Re: RPi3 usb boot hang on stable/13

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On 2022-Jul-2, at 09:58, bob prohaska <[email protected]> wrote:

> Lately an RPi3 running stable/13 has started hanging on boot from USB
> The disk is on a powered hub.
> 
> When gracefully rebooted it ends with:
> 
> .....
> MESS:00:00:03.166523:0: Device tree loaded to 0x4000 (size 0x63cd)
> MESS:00:00:03.172180:0: uart: Set PL011 baud rate to 103448.300000 Hz
> MESS:00:00:03.178716:0: uart: Baud rate change done...
> MESS:00:00:03.182145:0: uart: Baud rate change done...
> MESS:00:00:03.187830:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
> MMC:   mmc@7e300000: 1
> Loading Environment from FAT... OK
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> Bus usb@7e980000: scanning bus usb@7e980000 for devices... 6 USB Device(s) found
>       scanning usb for storage devices... 1 Storage Device(s) found
> Hit any key to stop autoboot:  0 
> 
> Device 0: 

That is U-Boot output. Looks like the output stopped before
the load of even the FreeBSD loader: FreeBSD is not involved
yet so it is not a FreeBSD problem.

> At that point the console is unresponsive. 

Nasty.

> The machine has a history of not always finding the USB disk, but this
> appears to be new behavior. As with the disk discovery problem, the
> error can be worked around by simple repetition. Once booted it's 
> stable but network response remains erratic.
> 
> There's some indication that power-cycling the hard disk helps.
> 
> At the moment uname -a reports
> 
> FreeBSD pelorus.zefox.org 13.1-STABLE FreeBSD 13.1-STABLE #5 stable/13-n251597-7c500f98b8d: Fri Jul  1 21:52:12 PDT 2022     [email protected]:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64

But FreeBSD is not involved yet at the failure point.

What vintage of U-Boot?

# strings u-boot.bin | grep "U-Boot 20"


===
Mark Millard
marklmi at yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.