From owner-freebsd-arm@freebsd.org  Sun Aug  7 14:54:46 2016
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 543ACBB0030
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Sun,  7 Aug 2016 14:54:46 +0000 (UTC)
 (envelope-from paul@gromit.dlib.vt.edu)
Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gromit.dlib.vt.edu",
 Issuer "Chumby Certificate Authority" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2D1BE1B88;
 Sun,  7 Aug 2016 14:54:46 +0000 (UTC)
 (envelope-from paul@gromit.dlib.vt.edu)
Received: from mather.chumby.lan (c-71-63-91-41.hsd1.va.comcast.net
 [71.63.91.41])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 445EC252;
 Sun,  7 Aug 2016 10:46:37 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Raspberry Pi B stuck during boot?
From: Paul Mather <paul@gromit.dlib.vt.edu>
In-Reply-To: <ceb1d17b-cf01-9d7e-a11b-2d5fb0e26538@freebsd.org>
Date: Sun, 7 Aug 2016 10:46:36 -0400
Cc: ticso@cicely.de,
 freebsd-arm <freebsd-arm@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <772B7B99-9C6E-4AA6-86F7-4FECF85B8A15@gromit.dlib.vt.edu>
References: <CADL2u4jjVuxVkcG06z_7pJWX72YGWGm9P08Rsuwo-Q6u_rbTMQ@mail.gmail.com>
 <CADL2u4iS=PCXMRr7TxkS8KZJj7wKDKvqCMg71s_iOg3tFTETdw@mail.gmail.com>
 <CADL2u4jiGMoC0C-rPU7vqyurpUtozy2u0d2XcMq+PuBGULZ3Rw@mail.gmail.com>
 <CADL2u4jqfpH1dsyFfpgR8LR8f6sMZRZVAQOaZNH_OqAXiKMbqA@mail.gmail.com>
 <CADL2u4h5iP=eVQSYUpMGRj-Awtu4yKT_w7jdv1ZYmb-sXwSUNQ@mail.gmail.com>
 <CADL2u4iX5yrbwAGmFVc1p8gAT-xQrxPETDazBXgzGJK9PpipdQ@mail.gmail.com>
 <CADL2u4gsQX9sYcqTLK0xqW1tnP1R_+0X4L+g0+-Lcy1juCMRFA@mail.gmail.com>
 <CADL2u4gzxANGUEfCw5Dn5otX7H53J-eA2UjQbTWo+qR_OAy_zQ@mail.gmail.com>
 <CADL2u4j0mx5W=rkdTpnZb1KFsc4y3N0_fq80OZK=eNrw8eFg=w@mail.gmail.com>
 <CADL2u4hANGUQSLe-JWfB4FQoRMPx5jm0u6oU1K1pg+K=Xy-SEw@mail.gmail.com>
 <20160806142322.GB31491@cicely7.cicely.de>
 <ceb1d17b-cf01-9d7e-a11b-2d5fb0e26538@freebsd.org>
To: =?windows-1252?Q?Ren=E9_Ladan?= <rene@freebsd.org>
X-Mailer: Apple Mail (2.3124)
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Aug 2016 14:54:46 -0000


> On Aug 7, 2016, at 6:09 AM, Ren=E9 Ladan <rene@freebsd.org> wrote:
>=20
> On 06-08-16 16:23, Bernd Walter wrote:
>> On Sat, Aug 06, 2016 at 03:06:20PM +0200, Ren=E9 Ladan wrote:
>>> Hi,
>>>=20
>>> With recent versions of 11 (alpha3 and beta3) my raspberry b gets =
stuck
>>> near the end of the boot. I checked the SD card and updated it to =
11-beta3
>>> using these commands (if I remember correctly, but nothing unusual):
>>>=20
>>> % make buildworld TARGET=3Darm TARGET_ARCH=3Darmv6
>>> % make buildkernel KERNCONF=3DRPI-B TARGET=3Darm TARGET_ARCH=3Darmv6
>>> # make installworld TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt
>>> # make installkernel TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt
>>> KERNCONF=3DRPI-B
>>> # make delete-old TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt
>>> # make delete-old-libs TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt=

>>> # mergemaster -A armv6 -D /mnt -p
>>> # mergemaster -A armv6 -D /mnt -U -i
>>>=20
>>> See https://rene-ladan.nl/IMG_20160804_193031.jpg for a phone =
picture of
>>> the TV screen where it gets stuck.
>>>=20
>>> Any ideas if what could be wrong?
>> It might be hanging in single user mode prompt on serial console.
>>=20
> So if I would disable serial console in /etc/ttys it should be fine?


The phone picture of the screen showed a "WARNING: / was not properly =
dismounted" line in the boot messages.  It could be that the system has =
dropped into single-user mode because of this (i.e., fsck -p failed and =
thus so did multi-user boot).


> It still hangs with only the "console" and "ttyv0" entries "on" in
> /etc/ttys, the rest is "off", but it used to work fine.


I suggest you fsck your SD card file systems so they are clean before =
troubleshooting further.

Cheers,

Paul.