-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
| interspersed logread output which shows some glamo timeouts (the | Feb 13 11:42:17 neo user.info kernel: [181651.915000] glamo-mci glamo-mci.0: command timeout, continuing Well these are likely the cause of the other problems in the higher layers. These were the old "Insanity Timeouts" weakened to nonfatal errors since it seemed that the command had in fact completed. Sprite_tm suggested it. https://docs.openmoko.org/trac/ticket/2078 He also says he can match md5sum on the device, but then I don't know how that's consistent with the evidently corrupted filesystem. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmYE5AACgkQOjLpvpq7dMrLBwCghcxkav1UY26G7roClqBlQs2+ mVAAoIO7e+006Igyx6WcB1nIdOsMJ1Um =e7Zm -----END PGP SIGNATURE-----
