main's recent loader.efi broken in an example aarch64 update context

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
[I've cc'd some folks that recently committed onto main's stand/
or did the llvm14 toolchain merge. I've no clue what makes the
difference.]

Note: the MACCHIATObin Double Shot has a EDK2 based
UEFI/ACPI context for how it is set up to boot.

In trying to update a MACCHIATObin Double Shot to a main
vintage with llvm14 I got boot attempts that look like the
below at the tail of its visible activity (serial console):

QUOTE
Loading kernel...
/boot/kernel/kernel text=0x2a8 text=0x91b040 text=0x216434 data=0x1b8128 data=0x
0+0x2ae000 0x8+0x130980+0x8+0x157b86
Loading configured modules...
/boot/kernel/cryptodev.ko text=0x16c3 text=0x27a0 data=0x628+0x10 0x8+0xcd8+0x8+
0x96c
/boot/kernel/zfs.ko text=0xa81a0 text=0x209310 data=0x26a88+0xba46c 0x8+0x32a78+
0x8+0x2c37e
/etc/hostid size=0x25
/boot/entropy size=0x1000
No valid device tree blob found!
WARNING! Trying to fire up the kernel, but no device tree blob found!
EFI framebuffer information:
addr, size     0x0, 0x0
dimensions     0 x 0
stride         0
masks          0x00000000, 0x00000000, 0x00000000, 0x00000000


Synchronous Exception at 0x00000000B460F554
END QUOTE

Part of the update was updating the loader.efi copies:

# ls -Tldt /mnt/efi/*/*
-r-xr-xr-x  1 root  wheel  1204828 May 14 18:53:16 2022 /mnt/efi/boot/bootaa64.efi
-r-xr-xr-x  1 root  wheel  1204828 May 14 18:53:16 2022 /mnt/efi/freebsd/loader.efi



I had to revert to copies of a prior loader.efi vintage that
I had around to copy in order to boot the otherwise updated
USB3 drive. Nothing else had to change. Copied from:

CA72_Mbin_ZFS aarch64  1400057 1400057 # ls -Tldt /boot/efi/efi/*/*
-rwxr-xr-x  1 root  wheel  1287580 Apr 28 21:46:46 2022 /boot/efi/efi/boot/bootaa64.efi
-rwxr-xr-x  1 root  wheel  1287580 Apr 28 21:46:46 2022 /boot/efi/efi/freebsd/loader.efi




===
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.