From owner-freebsd-arm@FreeBSD.ORG  Mon Mar 17 01:33:15 2014
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5C833EAE
 for <freebsd-arm@freebsd.org>; Mon, 17 Mar 2014 01:33:15 +0000 (UTC)
Received: from felyko.com (felyko.com [IPv6:2607:f2f8:a528::3:1337:ca7])
 by mx1.freebsd.org (Postfix) with ESMTP id 473C6C20
 for <freebsd-arm@freebsd.org>; Mon, 17 Mar 2014 01:33:15 +0000 (UTC)
Received: from [10.0.1.3] (c-24-6-115-18.hsd1.ca.comcast.net [24.6.115.18])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by felyko.com (Postfix) with ESMTPSA id 21FD039841;
 Sun, 16 Mar 2014 18:33:12 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Booting FreeBSD from eMMC on BeagleBone Black
From: Rui Paulo <rpaulo@FreeBSD.org>
In-Reply-To: <CAD44qMXrKbZqXT_Z1UL2LXuVON4Gb49m-GygW_6Y14Zz-egTFw@mail.gmail.com>
Date: Sun, 16 Mar 2014 18:33:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1283934-0065-4979-92AA-99D1056BFBD5@FreeBSD.org>
References: <CAD44qMXrKbZqXT_Z1UL2LXuVON4Gb49m-GygW_6Y14Zz-egTFw@mail.gmail.com>
To: Patrick Kelsey <kelsey@ieee.org>
X-Mailer: Apple Mail (2.1874)
Cc: freebsd-arm <freebsd-arm@freebsd.org>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <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: Mon, 17 Mar 2014 01:33:15 -0000

On 16 Mar 2014, at 14:59, Patrick Kelsey <kelsey@ieee.org> wrote:

> - Improved disk probing support that will now by default find and use =
the
> first suitable partition among the available storage devices.

I think this introduced a bug where, if you have a non-responsive boot =
device, ubldr will stop and won't try network booting:

## Starting application at 0x01000054 ...
Consoles: U-Boot console =20
Compatible API signature found @1d800a8
Number of U-Boot devices: 2

FreeBSD/armv6 U-Boot loader, Revision 1.2
(rpaulo@zedfs.local, Fri Mar 14 22:35:47 PDT 2014)
DRAM:	 256MB
Unknown device type ''   <------------ this is new
Found U-Boot device: disk
Probing all storage devices...
Checking unit=3D0 slice=3D0 partition=3D-1...disk0: read failed, error=3D1=


Checking unit=3D1 slice=3D0 partition=3D-1...
Checking unit=3D2 slice=3D0 partition=3D-1...
Checking unit=3D3 slice=3D0 partition=3D-1...
Checking unit=3D4 slice=3D0 partition=3D-1...
Checking unit=3D5 slice=3D0 partition=3D-1...

can't load 'kernel'

Type '?' for a list of commands, 'help' for more detailed help.
loader>=20

It stops here and doesn't try net0 booting.

--
Rui Paulo