From owner-freebsd-arm@FreeBSD.ORG  Wed Aug 28 12:41:34 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@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 ESMTP id 186C5616;
 Wed, 28 Aug 2013 12:41:34 +0000 (UTC)
 (envelope-from lists.br@gmail.com)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com
 [IPv6:2a00:1450:400c:c03::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7B82C247F;
 Wed, 28 Aug 2013 12:41:33 +0000 (UTC)
Received: by mail-we0-f177.google.com with SMTP id q55so5101243wes.36
 for <multiple recipients>; Wed, 28 Aug 2013 05:41:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=iY5/fS002OFI3jR0J8VIZcYl4UsPIUyLrPTcjWdGpvk=;
 b=S6Tc7wbYCmeib+ebO37IOdmbwubuCrDUdSnYqsNQfniFIrJEGS5Y/rXSY224vqiVmN
 uIRrQGaMm3wrs3c0llVz3QpDIZVAXTpllzo04i4wnW7jRinCKczMBDqqhnLHyPfxUHpv
 jlcBzWTtt8qhFyaV5UCjlSUfZpkwGqds8FjK8t2WZOx/RAeflnIkP46Rn5tNSNpbyLia
 Ty9yyBqlltIdVGpyI9j6/xFOeIIEAKwz4cw1LD6eLtrL9Gxy9f3IS3v7sVtoiqw42kx9
 RtcmhjRIq6Vx3tIfN+X3Rlw5w+OpvEkSg12T0sP1a7CS9hWmzoFjGtGjBULQyvaADJH5
 oFbA==
MIME-Version: 1.0
X-Received: by 10.194.134.168 with SMTP id pl8mr1694577wjb.74.1377693691811;
 Wed, 28 Aug 2013 05:41:31 -0700 (PDT)
Received: by 10.216.75.140 with HTTP; Wed, 28 Aug 2013 05:41:31 -0700 (PDT)
In-Reply-To: <201308281230.r7SCU0k5093956@freefall.freebsd.org>
References: <201308281230.r7SCU0k5093956@freefall.freebsd.org>
Date: Wed, 28 Aug 2013 09:41:31 -0300
Message-ID: <CAB=2f8wbfQ1myBssBkUs-yh8k7Ji-j8MeUEOZGGG+t6CXkjv+Q@mail.gmail.com>
Subject: Re: arm/181601: Sporadic failure of root mount on ARM/Raspberry
From: Luiz Otavio O Souza <lists.br@gmail.com>
To: Ian Lepore <ian@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 12:41:34 -0000

On 28 August 2013 09:30, Ian Lepore <ian@freebsd.org> wrote:

[...]
 > mmcsd0: 8GB <SDHC NCard 1.0 SN 1075839384 MFG 05/2013 by 130 JT> at mmc0
50.0MHz/4bit/65535-block
 > WARNING: WITNESS option enabled, expect reduced performance.
 > WARNING: DIAGNOSTIC option enabled, expect reduced performance.
 > mmcsd0: Error indicated: 1 Timeout
 > mmcsd0: Error indicated: 1 Timeout
[...]

>
>  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).
>

Yes, i've seen this as well and for me, every time it fails it thinks my SD
is HS capable while it isn't. This make it fail later.

Setting hw.bcm2835.sdhci.hs=0 on loader.conf works fine as a workaround.

Luiz