My Zaurus startet to behave strangely (CPU load average > 2.00, fonts in GPE wrong, suspend not working). I couldn't identify to problem, so I rebooted a couple of times, which didn't solve the problem. I found two interesting bits in 'dmesg': [full dmesg output attached]
Sharp SL series flash device: 800000 at 0
Using static partision definition
Creating 1 MTD partitions on "sharpsl-flash":
0x00120000-0x007f0000 : "Boot PROM Filesystem"
NAND device: Manufacturer ID: 0xec, Chip ID: 0x79 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 32 at 0x00080000
Bad eraseblock 3095 at 0x0305c000
Bad eraseblock 3099 at 0x0306c000
Creating 3 MTD partitions on "sharpsl-nand":
0x00000000-0x00700000 : "System Area"
[...]
0x00700000-0x03c00000 : "Root Filesystem"
0x03c00000-0x08000000 : "Home Filesystem"
[...]
I2C: i2c-0: PXA I2C adapter
i2c: error: exhausted retries
i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
i2c: ICR: 000007e0 ISR: 00000002
i2c: log: [00000446:000007e0]
I don't know whether these message are new.
I tried to find out whether the NAND chip is working by running "md5sum /dev/mtdblock*". This works on mtdblock0 and mtblock3 while I'm seeing "IO errors" for mtdblock1 and mtdblock2.
So, it seems my NAND has a few badblocks, I learned (from google) that's OK. But are these NEW badblocks which were good untill now? I know the NAND memory wears out, but does this mean I'm near the end of its lifecycle (2.5years of "normal" usage)?
I assume the builtin NAND chips don't have any "logic" (for wear leveraging, mapping out badblocks), so this has to be done on the software side (jffs2, mtd?). But how would I do this? Will the OZ installer do the job? Is there a "format" utility?
Did people here have problems with bad NAND chips before? I assume, the devices used by OZ developers get reflashed quite often?
Your help is very much appreciated.
