Date: Sat, 22 Apr 2023 08:28:10 +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-bfHatZGpeq@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 #7 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #6) I found the distinction that controls failure vs. success in booting via the USB3 ports: USB3-C ugen0.5: <GenesysLogic USB3.2 Hub> at usbus0 ports: ZFS and UFS boots fail. USB3-A ugen0.1: <Generic XHCI root HUB> at usbus0 ports: ZFS and UFS boots work. Looks like the FreeBSD kernel does not handle USB3.2 (but the UEFI/ACPI does for the FreeBSD loader). This may make the Windows Dev Kit 2023 a useful context for development work on handling more modern USB3.*'s. I'll note that https://learn.microsoft.com/en-us/windows/arm/dev-kit/ reports: QUOTE When connecting an external keyboard or mouse, use the USB-A ports, not USB-C. Using USB-C to connect a keyboard or mouse will only work intermittently. END QUOTE (It is unclear if that is a Windows specific issue, UEFI issue, both, or more.) For reference for the UFS USB3-C boot failures, the messages are: Mounting from ufs:/dev/gpt/CA72USBufs failed with error 22; retrying for 10 more seconds Mounting from ufs:/dev/gpt/CA72USBufs failed with error 22; invalid fstype. --=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-bfHatZGpeq>