Can't access ext3 partition on uSD

Stefan Monnier monnier at iro.umontreal.ca
Fri Feb 13 18:19:34 CET 2009


>> I guess so as well, but there's no trace of the problems.  If I do
>> a "find /sd -ls >/dev/null" to force it to read every inode, I get
>> a bunch of "Stale NFS file handles", a couple "Input/Output" errors, and
> There should be some much more chatty information in dmesg related to
> the input / output errors.

I wish there were, but really there isn't.  Maybe I can "turn on
debugging info" somehow?

> Another, dumb, thing to try is make sure there's a SIM on top of the uSD
> and maybe even wedge some paper on there to make sure the uSD is pressed
> down properly on the connector.

There's a SIM in there.
Adding a bit of paper doesn't seem to make anny difference.

FWIW, it seems that reading from that partition is deterministic, since
running md5sum on it twice, returns the same answer (it's a 2GB
partition, so it can't be cached).  See sessiong-log below, with
interspersed logread output which shows some glamo timeouts (the
battery warnings are due to my use of a Nokia battery).


        Stefan


# md5sum /dev/mmcblk0p1; md5sum /dev/mmcblk0p1
Feb 13 11:38:03 neo local0.debug udhcpc[2206]: Sending renew...
Feb 13 11:38:04 neo local0.info udhcpc[2206]: Lease of 192.168.1.81 obtained, lease time 86400
Feb 13 11:40:08 neo daemon.info ntpd[2205]: no servers reachable
Feb 13 11:41:02 neo user.info kernel: [181576.600000] pcf50633 0-0073: Charging restarted..
Feb 13 11:41:03 neo user.info kernel: [181576.640000] pcf50633 0-0073: INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
Feb 13 11:41:03 neo user.info kernel: [181576.710000] pcf50633 0-0073: INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 13 11:41:03 neo user.err kernel: [181576.710000] power_supply battery: driver failed to report `health' property
Feb 13 11:41:03 neo user.info kernel: [181576.745000] pcf50633 0-0073: INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 13 11:42:17 neo user.info kernel: [181651.915000] glamo-mci glamo-mci.0: command timeout, continuing
Feb 13 11:45:33 neo user.info kernel: [181846.750000] glamo-mci glamo-mci.0: command timeout, continuing
Feb 13 11:46:10 neo user.info kernel: [181884.560000] glamo-mci glamo-mci.0: command timeout, continuing
Feb 13 11:46:55 neo user.info kernel: [181929.475000] glamo-mci glamo-mci.0: command timeout, continuing
1832f642f13dd3bcebf738b7cc682eb9  /dev/mmcblk0p1
Feb 13 11:53:02 neo user.info kernel: [182295.905000] glamo-mci glamo-mci.0: command timeout, continuing
Feb 13 11:55:22 neo user.info kernel: [182436.685000] glamo-mci glamo-mci.0: command timeout, continuing
Feb 13 11:56:02 neo user.info kernel: [182476.680000] pcf50633 0-0073: Charging restarted..
Feb 13 11:56:02 neo user.info kernel: [182476.705000] pcf50633 0-0073: INT1=0x80 INT2=0x00 INT3=0x01 INT4=0x00 INT5=0x00
Feb 13 11:56:02 neo user.info kernel: [182476.795000] pcf50633 0-0073: INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 13 11:56:02 neo user.err kernel: [182476.795000] power_supply battery: driver failed to report `health' property
Feb 13 11:56:02 neo user.info kernel: [182476.855000] pcf50633 0-0073: INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 13 11:59:22 neo user.info kernel: [182676.180000] glamo-mci glamo-mci.0: command timeout, continuing
Feb 13 12:01:34 neo user.info kernel: [182808.110000] glamo-mci glamo-mci.0: command timeout, continuing
1832f642f13dd3bcebf738b7cc682eb9  /dev/mmcblk0p1
# 





More information about the openmoko-kernel mailing list