arm/181601: Sporadic failure of root mount on ARM/Raspberry

Peter Jeremy peter at rulingia.com
Fri Feb 7 22:27:33 UTC 2014


On 2013-Aug-28 12:30:00 +0000, Ian Lepore <ian at freebsd.org> wrote:
> On Wed, 2013-08-28 at 05:35 +0000, Martin Laabs wrote:
> > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]...
> > mountroot: waiting for device /dev/mmcsd0s2a ...
> > smsc0: chip 0xec00, rev. 0002
> > miibus0: <MII bus> on smsc0
> > ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
> > ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > ue0: <USB Ethernet> on smsc0
> > ue0: Ethernet address: b8:27:eb:1d:b7:5a
> > Mounting from ufs:/dev/mmcsd0s2a failed with error 19.
> > 
> > Loader variables:
> >   vfs.root.mountfrom=ufs:/dev/mmcsd0s2a
> >   vfs.root.mountfrom.options=rw,noatime

> We have long had a problem with mysterious sdcard timeout errors on RPi
> that doesn't happen on other hardware with sdhci controllers.  Until
> now, it was thought that these timeouts always occurred shortly after
> the controller was initialized by the OS.  The timeouts would affect the
> early card-detection sequences; we worked around them by adding
> automatic retries to the mmc code that identifies and initializes cards.
> 
> This error appears to be a timeout that occurs after the card init
> sequences are done (the errors are reported by mmcsd0, not mmc0).

I am seeing this fairly consistently on every second boot - which is rather
annoying because I would like that RPi to reliably boot unattended.

Does anyone have any suggestions for a workaround?

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 326 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20140208/2c0a5ecc/attachment.sig>


More information about the freebsd-arm mailing list