bradb
06-18-2006, 04:12 AM
Ok, this is odd - I've been playing around with a port of mmc-unionfs, and have had a few odd problems. I've been assuming it was something I did, until I recently reloaded the 2006 beta, and I noticed this in the dmesg output:
JFFS2 notice: (338) check_node_data: wrong data CRC in data node at [some address]...
I'd noticed this before, after I used the unionfs.ko kernel module. But today, I've re-flashed the 2006 beta and before I've been able to load that package, I'm getting the error. So, it's not my port.
I've also had problems today with installing packages - after I install one package, the next install hangs... I reboot and start the install again and all seems fine.
Any ideas if this is a real hardware problem or not? It seems to be intermittent (of course).
Brad.
JFFS2 notice: (338) check_node_data: wrong data CRC in data node at [some address]...
I'd noticed this before, after I used the unionfs.ko kernel module. But today, I've re-flashed the 2006 beta and before I've been able to load that package, I'm getting the error. So, it's not my port.
I've also had problems today with installing packages - after I install one package, the next install hangs... I reboot and start the install again and all seems fine.
Any ideas if this is a real hardware problem or not? It seems to be intermittent (of course).
Brad.