Date: Fri, 28 Apr 2023 22:25:24 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805 --- Comment #26 from Mark Millard <email@example.com> --- (In reply to Mark Millard from comment #25) Interestingly, using the adaptor to USB-C for plugging in media after booting FreeBSD, I get different results on different systems (the only FreeBSD USB-C contexts that I've access to): ThreadRipper 1950X: media is detected. Windows Dev Kit 2023: same media is not detected. The ThreadRipper is a USB 3.1 context for the USB-C connector, not a USB 3.2 context. The WDK23 has its note about keyboards and mice via its USB-C connector which may indicate something relevant. The media here is a USB3.0 SSD. As for having the USB-C connection present during boot loader activity: that did not cause the loader any problems. The only way that I've ever found to have a synchronous exception during loader activity is from having plugged in FreeBSD boot media with too old of a UEFI loader --and for the UEFI to also have picked that media to get the UEFI loader from. Then that loader leads to the synchronous exception. The UEFI does not give a way to explicitly pick which USB device to boot from when more than one "bootable" USB media is present. May be the port scan is in a fixed order or some such. I've not tested for such. Overall: I'm unable to reproduce the problem that was reported. -- You are receiving this mail because: You are the assignee for the bug.