Ticket #2057 (new defect)
1bit errors in files
|Reported by:||Richard.Kralovic||Owned by:||openmoko-devel|
|Severity:||normal||Keywords:||file corruption, 1bit errors|
|Blocking:||Estimated Completion (week):|
After some time of usage, I notice 1 bit errors in some binaries/libraries (affected application crashes, restarting the application does not, help, of course). Files are correct after rebooting Neo again; even without reflash.
I experienced this bug with different distributions (FSO, ASU...) and different kernels (downloaded Om2008.9-gta02-20080916.uImage.bin, custom built uImage-2.6.24+git0+a1e97c611253511ffc2d8c45e3e6d6894fa03fa3-r1.01-om-gta02.bin, etc.).
There is no relevant information in dmesg output. I also added warning messages to the software ECC correcting code (drivers/mtd/nand/nand_ecc.c) to the custom build kernel, but none of them appeared in dmesg.
The bug is hard to reproduce on demand, but usually occurs after several hours/days of usage.
Observed file corruption was always a single bit flip from 0 to 1, at offset 0x????0c2 or 0x????8c2 of the affected file, e.g. as follows:
< 00008c0: 0200 0200 0000 0000 0300 0300 0100 0000 ................
00008c0: 0200 2200 0000 0000 0300 0300 0100 0000 ..".............