From owner-freebsd-arm@FreeBSD.ORG  Tue Jan  1 03:22:29 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id EAB846A6
 for <freebsd-arm@freebsd.org>; Tue,  1 Jan 2013 03:22:29 +0000 (UTC)
 (envelope-from shurd@sasktel.net)
Received: from mail129c7.megamailservers.com (mail129c7.megamailservers.com
 [69.49.98.229]) by mx1.freebsd.org (Postfix) with ESMTP id 80D5C8FC0A
 for <freebsd-arm@freebsd.org>; Tue,  1 Jan 2013 03:22:28 +0000 (UTC)
X-Authenticated-User: hurds.sasktel.net
Received: from stephen.hurd.local (ip70-187-145-241.oc.oc.cox.net
 [70.187.145.241]) (authenticated bits=0)
 by mail129c7.megamailservers.com (8.13.6/8.13.1) with ESMTP id r012NAPG030487
 for <freebsd-arm@freebsd.org>; Mon, 31 Dec 2012 21:23:12 -0500
Message-ID: <50E2488F.6010506@sasktel.net>
Date: Mon, 31 Dec 2012 18:23:11 -0800
From: Stephen Hurd <shurd@sasktel.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:16.0) Gecko/20121022 Firefox/16.0 SeaMonkey/2.13.1
MIME-Version: 1.0
To: freebsd-arm <freebsd-arm@freebsd.org>
Subject: Re: Rpi boot process stuck on mountroot
References: <CALCpEUGXc_Dp=BG5dTLBkMR3P30kgNnzpWzHuW2Xx-Qs0XjZvw@mail.gmail.com>
 <1357002062.54953.135.camel@revolution.hippie.lan>
 <06BF94A3-6F02-4E4B-8572-D202E5C8CB4B@kientzle.com>
 <57772D20A1814967B7FFDC476215780B@ad.peach.ne.jp>
In-Reply-To: <57772D20A1814967B7FFDC476215780B@ad.peach.ne.jp>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-CSC: 0
X-CHA: v=1.1 cv=irLj17ZF5ABOTBuyAu2t31N+Nq5xiP0nh7CWcFrUZ/0= c=1 sm=1
 a=sd1-78TbSwQA:10 a=Fi2vhVeW2BcA:10 a=YxfxW3ofkq8A:10 a=8nJEP1OIZ-IA:10
 a=qWhSLQ/2FgUpSQgLv9E1tw==:17 a=6I5d2MoRAAAA:8 a=eCIUKNaFY_JaK2AMAg0A:9
 a=wPNLvfGTeEIA:10 a=kpCrhyn8lwkA:10 a=qWhSLQ/2FgUpSQgLv9E1tw==:117
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A020206.50E24891.006D, ss=1, re=0.000, recu=0.000,
 reip=0.000, cl=1, cld=1, fgs=0
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: Tue, 01 Jan 2013 03:22:30 -0000

Daisuke Aoyama wrote:
> There is two factor.
> One of is dev/mmc never check an error condition of the result.
> Other is RPI does not work 50MHz with some SD cards.
> I have posted the workaround patch today.
>
> http://lists.freebsd.org/pipermail/freebsd-arm/2013-January/004507.html

Another thing to consider is the power.  When voltage levels between TP1
and TP2 are below around 4.6V, I see a lot more of this failure.