I'm having a bit of a strange issue with one board out of 16, all are running the same boot loader (u-boot 1.3.1) and same kernel image (18.104.22.168.atmel.3). I'm booting the kernel off tftp and running the rootfs from nfs share.
However, the one particular board gets Critical Exceptions on a semi-regular basis. I've already swapped off the SDRAM thinking that it could be a ram related issue, with no success.
In my mind it points to a hardware issue since 15 other boards running the exact same setup are unaffected. What exactly does the critical exception mean? Is this the code has tried stepping outside of the acceptable memory space, perhaps with a stuck address bit or something like that?
Anyway here is a snip of the error message - one of many but this is a typical one: (this is during the boot sequence)
Mounting virtual filesystems: /proc mounted /sys mounted /dev mounted /dev/pts directory made /dev/pts mounted /dev/shm directory made Oops: Critical exception, sig: 9 [#1] FRAME_POINTER chip: 0x01f:0x1e82 rev 2 pc : [<00041502>] lr : [<00044778>] Not tainted sp : 7ff1eabc r12: 00000000 r11: 0007c23c r10: 00000000 r9 : 00000001 r8 : 0007a428 r7 : 0007c668 r6 : 0007556c r5 : 00079d28 r4 : 0007c23c r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000005 Flags: qvnzC Mode bits: hjmde....g CPU Mode: Application Process: S00mountvirtfs  (task: 93c11300 thread: 93d5a000) Killed /config mounted /tmp mounted /var/run mounted /var/log mounted
Some things seem to cause it to crap out easier than others, such as running some python scripts.
If anyone's ran into similar issues in the past I'd appreciate any tips. I'm running the mtest on the u-boot, and the next potential hardware step would be to replace the AVR32, not a small undertaking.