Date: Wed, 28 Feb 2018 14:46:24 -0500 From: Hyun Hwang <hyun@caffeinated.codes> To: freebsd-arm@freebsd.org Subject: Re: Stock image of armv7 RPI2 (r330034) hangs on loader after first boot, with red LED on. Message-ID: <1519847184.3588780.1286870920.4B6980E3@webmail.messagingengine.com> In-Reply-To: <1519842223.2614418.1286772128.15A6E6C5@webmail.messagingengine.com> References: <1519842223.2614418.1286772128.15A6E6C5@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, February 28, 2018, 1:23 PM (UTC-0500), Hyun Hwang <hyun@caffeinated.codes> wrote: > Hi, > > I re-imaged my RPi 2 with [the stock image] > (https://download.FreeBSD.org/ftp/snapshots/arm/armv7/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-arm-armv7-RPI2-20180226-r330034.img.xz), > but it hangs on second boot on the loader. > > First boot shows no problem at all. Loader finds the kernel, loads the > dtb, and hands over to the kernel. Then kernel clears the screen and > starts normal boot procedure. > The problem occurs on the second boot. I first shut the pi down using > `shutdown -h now`, unplugged it, and then immediately re-plugged to the > power. > > This is what the screen reads: > ``` > Hit [Enter] to boot immediately, or any key for command prompt. > Booting [/boot/kernel/kernel]... > /boot/dtb/bcm2836-rpi-2-b.dtb size=0x34cd > Loaded DTB from file 'bcm2836-rpi-2-b.dtb'. > Kernel entry at 0x1200100... > Kernel args: (null) > ``` > At this point, it does nothing. > > I have found that the very problem occurred [a month ago to bob] > (https://lists.freebsd.org/pipermail/freebsd-arm/2018-January/017310.html), > but unlike their situation (self-built), this occurs on stock image. > > Can anyone look into this problem? In the meantime, I will try few other > previous images that is still in download.FreeBSD.org. > > Thank you. > -- > Hyun Hwang I just checked stock image at r329009, and it boots fines even after the first boot. So some commit after r329009 is causing behavior, but frankly, I have no idea where to start looking, since this weird hang does not print any detailed message out even if I set `verbose_loading="YES"` and `boot_verbose="YES"` in `/boot/loader.conf.local`. It just sits there and do nothing after that `Kernel args: (null)` line. Any lead is appreciated. -- Hyun Hwang
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1519847184.3588780.1286870920.4B6980E3>