I have been searching the web, but I have not seen any mention of this kind of problem.
I am using a custom 405ex board based on Kilauea, with NAND boot. (256MB NAND and 256MB DDR DRAM.) The DRAM passes all tests, and the board boots into Linux fine. When adding code to the initrd, we found that any image > 16MB seemed to cause this problem after being loaded. I also tested on Kilauea, and it happens but only with a uboot 1.3.3 image running from NAND, the default NOR image does not fail. (1.3.2 rc2 ?)
To reproduce, I download an initrd (uRamdisk) using tftp in uboot and then use 'iminfo' and it causes a machine check. The strings from the image_get_xxx() functions appear to be bogus and printf crashes. (image_get_os, image_get_arch...) I am debugging it now, but I was hoping someone else had seen this already.
===== FROM UBOOT CONSOLE =====
=> tftp 200000 uRamdisk ... download completes ... => iminfo ## Checking Image at 00200000 ... Legacy image found Image Name: Linux-2.6.25.5 Created: 2008-08-20 22:17:07 UTC Image Type: Machine Check Exception. Caused by (from msr): regs 0ff0f310 Data machine check. NIP: 00000000 XER: 0000005F LR: 0FFCA940 REGS: 0ff0f310 TRAP: 0200 DEAR: 00000000 MSR: 00000000 EE: 0 PR: 0 FP: 0 ME: 0 IR/DR: 00
GPR00: 00000000 0FF0F400 0FF0FF44 60C21FAD 00000000 0FF0F450 01048A68 FFFFFFFF GPR08: 0FFA1BD8 60C21FAD 0FFD8838 00000002 00002FAF 00000000 0FFEAB00 0FFD83F4 GPR16: 0FFD8418 0FFD8424 0FF0F994 0FF0F894 0FF0F7DD 00000000 0FF0F750 0FFE1468 GPR24: 0FF0F418 0FF0F45C 00000000 60C21FAD FFFFFFFF 0FF0F5D7 0FFEC204 0FF0F450 Call backtrace: 0FF0F45C 0FFCAB9C 0FFBE4C8 9AE6C2BD machine check
==========
Any information would help. Thank you, Jeff
Jeff Hemstreet jeffhemstreet@yahoo.com