Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Feb 2014 22:30:02 GMT
From:      Peter Jeremy <peter@rulingia.com>
To:        freebsd-arm@FreeBSD.org
Subject:   Re: arm/181601: Sporadic failure of root mount on ARM/Raspberry
Message-ID:  <201402072230.s17MU2lL070048@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR arm/181601; it has been noted by GNATS.

From: Peter Jeremy <peter@rulingia.com>
To: Ian Lepore <ian@freebsd.org>
Cc: freebsd-arm@freebsd.org, freebsd-gnats-submit@freebsd.org
Subject: Re: arm/181601: Sporadic failure of root mount on ARM/Raspberry
Date: Sat, 8 Feb 2014 09:27:15 +1100

 --x+6KMIRAuhnl3hBn
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On 2013-Aug-28 12:30:00 +0000, Ian Lepore <ian@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.
 > >=20
 > > Loader variables:
 > >   vfs.root.mountfrom=3Dufs:/dev/mmcsd0s2a
 > >   vfs.root.mountfrom.options=3Drw,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.
 >=20
 > 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?
 
 --=20
 Peter Jeremy
 
 --x+6KMIRAuhnl3hBn
 Content-Type: application/pgp-signature
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.22 (FreeBSD)
 
 iKYEARECAGYFAlL1XcNfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl
 bnBncC5maWZ0aGhvcnNlbWFuLm5ldDBCRjc3QTcyNTg5NEVCRTY0RjREN0VFRUZF
 OEE0N0JGRjAwRkI4ODcACgkQ/opHv/APuIfsgACgrjubepqhBbphlk5FMaE/Zs8u
 dpAAoMEGJmwHGBTzDqREdu8NDVGAr1an
 =8SxC
 -----END PGP SIGNATURE-----
 
 --x+6KMIRAuhnl3hBn--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402072230.s17MU2lL070048>