[U-Boot] Random problem on MPC8640D based board

Hi,
We are using MPC8640 in our board. During booting we are getting TRAP 200 randomly. Some times it is booting without any issue some times it trapped into the exception 200 and automatically restarts itself. The PowerPC archietecture defines TRAP 200 will be due to some TLB miss and related things. Can you please suggest me how to identify the source of the issue and solve the problem.
TRAP 200 ########
U-Boot 2009.06 (Apr 27 2010 - 14:33:25) Data Patterns DPVPX0659 SPU COTS Module
CPU: 8641, Version: 2.1, (0x80900021) Core: E600 Core 0, Version: 2.2, (0x80040202) Clock Configuration: CPU:800 MHz, MPX:400 MHz DDR:200 MHz (400 MT/s data rate), LBC:25 MHz L1: D-cache 32 KB enabled I-cache 32 KB enabled L2: 1024 KB enabled Board Revision : 1V00 FPGA Revision : 1V00 I2C: ready POST: Enabled DRAM: DDR-2 Enabled DDR: 512 MB SDRAM Test skipped Now running in RAM - U-Boot at: 1ffaa000 POST memory PASSED FLASH: 512 MB *** Warning - bad CRC, using default environment
PCI-EXPRESS 1: Agent 0xdff08020=0x00000000 R0 bus_start: 0 phys_start: 0 size: 20000000 Not scanning PCI bus 00. PI=1 PCI-EXPRESS 1 on bus 00 - 00 SRIO: Machine check in kernel mode. Caused by (from msr): regs 1ff87e08 MSS error. MSSSR0: 00001000 NIP: 1FFE0BE0 XER: 20000000 LR: 1FFE0BB8 REGS: 1ff87e08 TRAP: 0200 DAR: 00000000 MSR: 00101030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
GPR00: 000000FF 1FF87EF8 1FF87F78 00000000 00000020 00000000 00000000 FFFFFFFF GPR08: 1FF87DE4 DC000034 1FF87C8F 1FF87DE4 00000000 FFFFFFFD 1FFF7100 200AA000 GPR16: F7FFFBFF FFAFF7FF FFFFFFFF FFFFFFDF FFFFFFFF 00000001 FFFFFBFF FFFFF7FF GPR24: FFEFEFFF FFFFFFFF FDEFFFFF 1FF87F58 1FF87FC4 20000000 1FFF89F4 00000001 Call backtrace: 1FFC22E4 1FFE27FC 1FFB5834 1FFAC560 machine check Resetting Board...
Thank you Thirumalai

Dear "Thirumalai",
In message 8F0ECFAA4F2C46928A69DE95FAF2A07B@itd210 you wrote:
We are using MPC8640 in our board. During booting we are getting TRAP 200 randomly. Some times it is booting without any issue some times it trapped into the exception 200 and automatically restarts itself. The PowerPC archietecture defines TRAP 200 will be due to some TLB miss and related things. Can you please suggest me how to identify the source of the issue and solve the problem.
Did you try booting Linux on that board? Let me guess: if you tried, it crashed, right?
I recommend to check the RAM initialization sequence. I bet you see memory corruption effects.
Best regards,
Wolfgang Denk

----- Original Message ----- From: "Wolfgang Denk" wd@denx.de To: "Thirumalai" thirumalai.p@datapatterns.co.in Cc: u-boot@lists.denx.de Sent: Wednesday, May 05, 2010 12:02 PM Subject: Re: [U-Boot] Random problem on MPC8640D based board
Dear "Thirumalai",
In message 8F0ECFAA4F2C46928A69DE95FAF2A07B@itd210 you wrote:
We are using MPC8640 in our board. During booting we are getting TRAP 200 randomly. Some times it is booting without any issue some times it trapped into the exception 200 and automatically restarts itself. The PowerPC archietecture defines TRAP 200 will be due to some TLB miss and related things. Can you please suggest me how to identify the source of the issue and solve the problem.
Sorry. Trap 200 is Machine check exception. Also sometimes we are getting TRAP 300 which is DSI exception.
Did you try booting Linux on that board? Let me guess: if you tried, it crashed, right?
No. It is not crashing. Linux is booting on this board successfully. Its a random issue.
I recommend to check the RAM initialization sequence. I bet you see memory corruption effects.
What you meant for memory corruption effects?
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de What can it profit a man to gain the whole world and to come to his property with a gastric ulcer, a blown prostate, and bifocals? -- John Steinbeck, _Cannery Row_ _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Dear "Thirumalai",
In message 0C0A8ED2EDFB487097801B3175C0F2CD@itd210 you wrote:
Sorry. Trap 200 is Machine check exception. Also sometimes we are getting TRAP 300 which is DSI exception.
It doesn't really matter which exception you are seeing. Fact is the system is not running stable. Culprit # 1 in such situations is the RAM not working stable.
Did you try booting Linux on that board? Let me guess: if you tried, it crashed, right?
No. It is not crashing. Linux is booting on this board successfully. Its a random issue.
How do you run Linux? Did you try running with root file system mounted over NFS, and adding some real load, like compiling some sources?
I recommend to check the RAM initialization sequence. I bet you see memory corruption effects.
What you meant for memory corruption effects?
I mean that your RAm is not working reliably. See the FAQ: http://www.denx.de/wiki/view/DULG/UBootCrashAfterRelocation
Best regards,
Wolfgang Denk

Dear Denx,
----- Original Message ----- From: "Wolfgang Denk" wd@denx.de To: "Thirumalai" thirumalai.p@datapatterns.co.in Cc: u-boot@lists.denx.de Sent: Wednesday, May 05, 2010 12:38 PM Subject: Re: [U-Boot] Random problem on MPC8640D based board
Dear "Thirumalai",
In message 0C0A8ED2EDFB487097801B3175C0F2CD@itd210 you wrote:
Sorry. Trap 200 is Machine check exception. Also sometimes we are getting TRAP 300 which is DSI exception.
It doesn't really matter which exception you are seeing. Fact is the system is not running stable. Culprit # 1 in such situations is the RAM not working stable.
Did you try booting Linux on that board? Let me guess: if you tried, it crashed, right?
No. It is not crashing. Linux is booting on this board successfully. Its a random issue.
How do you run Linux? Did you try running with root file system mounted over NFS, and adding some real load, like compiling some sources?
We are running with rootfile system mounted over NFS. we have used lmbench and ltp for load.
I recommend to check the RAM initialization sequence. I bet you see memory corruption effects.
What you meant for memory corruption effects?
I mean that your RAm is not working reliably. See the FAQ: http://www.denx.de/wiki/view/DULG/UBootCrashAfterRelocation
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Mr. Cole's Axiom: The sum of the intelligence on the planet is a constant; the population is growing.
participants (2)
-
Thirumalai
-
Wolfgang Denk