[Bug 270805] loader.efi: crashes with USB device attached

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 22 Apr 2023 01:14:21 UTC

Mark Millard <marklmi26-fbsd@yahoo.com> changed:

           What    |Removed                     |Added
                 CC|                            |marklmi26-fbsd@yahoo.com

--- Comment #3 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
Confirmed with main FreeBSD USBC boot media attached. This is
media I use to boot 3 types of Cortex-A72 systems, 2 by UEFI/ACPI
(HoneyComb, MACCHIATObin Double Shot), and 1 by U-Boot (RPi4Bs).
Also: 2 Cortex-A53 U-Boot based systems, a RPi3B and RPi2B
v1.2 . Also: ZFS root media. The media has main [so: 14] and
has the commits for D37765 and D38031 . I had put in place
hw.pac.enable=0 aS well.

Result on the Windows Dev Kit 2023 was a quick:

Synchronous Exception 0x0000000092F922FC

The sequence for the first Dev Kit Power On was:

1st: Power on with UEFI button and set the UEFI to use no secure boot keys.
     Set USB as the first context to try to boot from/via.

2nd: Try to boot with the FreeBSD media attached to USBC.
     Result: the exception.

(So Windows 11 Pro had never been started yet and the internal
media was undisturbed.)

Everything I've tried to boot that USBC media has gotten the same
result. I've not found any UEFI settings that make a difference.

Later I'll try some blank USBC media and possibly other variations
to see if something more specific about the media content leads to
the specific failure report vs. possibly other failures.

I'll note that I've no plan to remove the Windows Pro 11 from the
internal media. I want to be able to swap external media and boot, 
such as switching between ZFS and UFS based systems. I'll also
probably try FreeBSD in Hyper-V at some point.

You are receiving this mail because:
You are on the CC list for the bug.