From owner-freebsd-arm@freebsd.org Mon Mar 7 11:19:53 2016 Return-Path: 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 F03A6AC22F7 for ; Mon, 7 Mar 2016 11:19:53 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC6B1B69 for ; Mon, 7 Mar 2016 11:19:53 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 470501FE023; Mon, 7 Mar 2016 12:19:48 +0100 (CET) Subject: Re: Odd hang during boot on RPI2 for 2 days now To: Jukka Ukkonen , freebsd-arm References: <56D99C2E.4020301@gmail.com> <56DD5DF8.9090700@gmail.com> From: Hans Petter Selasky Message-ID: <56DD6476.80603@selasky.org> Date: Mon, 7 Mar 2016 12:22:30 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56DD5DF8.9090700@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 11:19:54 -0000 On 03/07/16 11:54, Jukka Ukkonen wrote: > > Continuing where I previously left with this problem... > When I set boot_verbose=1 in loader.conf I got a little > more information before the poor RPI2 simply froze. > Now the last shown line was... > > random: harvesting attach, 8 bytes (4 bits) from ukbd0 > > If I disconnect the USB keyboard and then reconnect it, > the kernel prints the normal detach and attach messages, > once again returns back to printing the "random: ..." > line shown above, and freezes again. > Then I think the init process is waiting for something. Would you manage to press CTRL+T in the console and see what is printed? --HPS