Date: Sat, 22 Apr 2023 02:27:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 270805] loader.efi: crashes with USB device attached Message-ID: <bug-270805-227-vPA0ZuSiVV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270805-227@https.bugs.freebsd.org/bugzilla/> References: <bug-270805-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270805 --- Comment #5 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #4) I booted teh media in question on another machine and did: # mv /boot/efi/EFI /boot/efi/EFI-disabled Then I tried booting the Dev Kit machine with the media connected: No Synchronous Exception Eventually it booted to the internal Windows 11 Pro So it appears that the FreeBSD boot loader is involved in the problem. Side note: I've now also tried a USB3-A style port instead of USB3-C. Both types of ports get the issue. (Given some Microsft wording I was not sure that ports USB3-A were involved in potential booting. They are.) FYI: # ls -Tld /boot/efi/EFI/*/* -r-xr-xr-x 1 root wheel 865292 Mar 15 21:30:46 2023 /boot/efi/EFI/BOOT/bootaa64.efi -rwxr-xr-x 1 root wheel 865292 Mar 15 21:30:46 2023 /boot/efi/EFI/FREEBSD/loader.efi They still match what is on my normal environment that still predates the openzfs import disaster. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270805-227-vPA0ZuSiVV>