rpi4b main-n245392-8423f5d4c12 won't boot due to microsd timeout

[Mark Millard]

On 2021-Mar-11, at 21:49, Mark Millard <marklmi at yahoo.com> wrote:


> On 2021-Mar-11, at 17:59, tech-lists <tech-lists at zyxst.net> wrote:
> 
>> main-n245392-8423f5d4c12 built and installed fine. On reboot it seems
>> the microsd card times out. Console log is here:
>> https://cloud.zyxst.net/~john/FreeBSD/main-n245392-8423f5d4c12-no-debug-failboot.txt
>> 
>> Booting kernel.old works fine. This one is from
>> main-n244802-88db1cc9f19 (Feb 14th)
>> 
>> Nothing else has been changed configuration-wise, same msdos partition,
>> same config.txt. Only thing that has changed is /usr/src has been
>> updated, built and installed as of main-n245392-8423f5d4c12 (March
>> 11th).
>> 
>> Should I raise this in bugzilla?
> 
> Note: I use the official snapshot
> 
> FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210311-15565e0a217-257277.img.xz
> 
> and its:
> 
> # strings /mnt/boot/kernel/kernel | grep 15565e0a217
> @(#)FreeBSD 14.0-CURRENT #0 main-n245383-15565e0a217: Thu Mar 11 08:02:52 UTC 2021
> FreeBSD 14.0-CURRENT #0 main-n245383-15565e0a217: Thu Mar 11 08:02:52 UTC 2021
> 
> For some comparisons to what you report about your
> build.
> 
> 
> 
> Some oddities in your report that might need to be
> addressed first to make things more comparable
> are . . .
> 
> Your log file shows:
> 
> U-Boot 2020.07-rc3-00208-g88bd5b1793-dirty (Jun 06 2020 - 20:33:00 +0100)
> 
> But FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210311-15565e0a217-257277.img.xz
> has:
> 
> # strings /mnt/u-boot.bin | grep 2020
> 2020.10
> U-Boot 2020.10 (Mar 11 2021 - 04:30:22 +0000)
> 
> This makes comparison of results messier. You might
> want to copy the snapshot file over to your
> media.
> 
> 
> For reference the snapshot for 15565e0a217
> also has:
> 
> # strings /mnt/start4.elf | grep VC_BUILD_ID_
> VC_BUILD_ID_USER: dom
> VC_BUILD_ID_TIME: 12:10:40
> VC_BUILD_ID_VARIANT: start
> VC_BUILD_ID_TIME: Feb 25 2021
> VC_BUILD_ID_BRANCH: bcm2711_2
> VC_BUILD_ID_HOSTNAME: buildbot
> VC_BUILD_ID_PLATFORM: raspberrypi_linux
> VC_BUILD_ID_VERSION: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean)
> 
> The Feb 25 2021 start4.elf build is from the officially
> tagged 1.20210303 rpi* material from:
> 
> https://github.com/raspberrypi/firmware/tree/1.20210303/boot/
> ( which is what a modern sysutils/rpi-firmware has in
> part of /usr/local/share/rpi-firmware/ )
> 
> Note: many files other than start*.elf are involved but
> many do not have such nice, checkable version strings
> to look at.
> 
> What vintage/variant was your experiment was based on?
> 
> You might want to copy the snapshot's material over to
> your media if your media does not match.
> 
> 
> Your log file shows:
> 
>    FreeBSD/arm64 EFI loader, Revision 1.1
>    (Thu Sep 17 07:58:43 UTC 2020 root at releng1.nyi.freebsd.org)
> 
> But FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210311-15565e0a217-257277.img.xz
> has:
> 
> # strings /mnt/EFI/BOOT/bootaa64.efi | egrep '(FreeBSD/|root@)'
> FreeBSD/arm64 EFI loader, Revision 1.1
> (Thu Mar 11 07:29:18 UTC 2021 root at releng1.nyi.freebsd.org)
> 
> I do not have sizes or content to compare to see if there
> are actual differences. FYI:
> 
> # ls -Tld /mnt/EFI/BOOT/bootaa64.efi 
> -rwxr-xr-x  1 root  wheel  1258796 Mar 10 23:29:52 2021 /mnt/EFI/BOOT/bootaa64.efi
> 
> You might want to copy the snapshot's material over to
> your media if your media does not match.

The suggestion might not be the best for EFI/BOOT/bootaa64.efi :

Copying your build's /boot/loader.efi to EFI/BOOT/bootaa64.efi
would likely be better so it is testing the version from your
build instead.

> With the deliberate matching of materials, re-running the
> experiment and basing any report on the result with a
> description of the context would avoid worries about the
> mismatches contributing to the behaviorial issues. (I've
> no clue if they actually matter or not.)




===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)