From owner-freebsd-arm@FreeBSD.ORG Fri Feb 7 22:30:02 2014 Return-Path: Delivered-To: freebsd-arm@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DDE84E9F for ; Fri, 7 Feb 2014 22:30:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AEC081085 for ; Fri, 7 Feb 2014 22:30:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s17MU2oa070049 for ; Fri, 7 Feb 2014 22:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s17MU2lL070048; Fri, 7 Feb 2014 22:30:02 GMT (envelope-from gnats) Date: Fri, 7 Feb 2014 22:30:02 GMT Message-Id: <201402072230.s17MU2lL070048@freefall.freebsd.org> To: freebsd-arm@FreeBSD.org Cc: From: Peter Jeremy Subject: Re: arm/181601: Sporadic failure of root mount on ARM/Raspberry X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Peter Jeremy List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 22:30:02 -0000 The following reply was made to PR arm/181601; it has been noted by GNATS. From: Peter Jeremy To: Ian Lepore 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 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: on smsc0 > > ukphy0: PHY 1 on miibus0 > > ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > ue0: 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--