* Shilimkar, Santosh <santosh.shilimkar@xxxxxx> [120605 23:41]: > > I don't know the AMXX architecture that well but looking at the > crash-log, am not sure GPMC should play in role here. > What I think is, it is mostly memory corruption and can be caused by > many reasons as Tony outlined. Bad GPMC timings can cause corruption on the smsc fifo, which can cause random oopses especially with nfsroot. I was seeing that on my zoom3 with nfsroot with bad muxing for GPMC until we applied bce492c0 (ARM: OMAP2+: UART: Fix incorrect population of default uart pads). That's easy to test by leaving out GPMC. > To ensure that, your memory is in good state, can you run memtester > for long duration and see that you > are not getting any memory failures. Try to give the maximum memory > size as a an input to memtester. Yes and that should be left running for a few weeks on a group of devices to verify things work once you think you have all the issues fixed. Regards, Tony > You can download one from [1] > > Regards > Santosh > [1] http://pyropus.ca/software/memtester/ -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
