Date: Sat, 22 Apr 2023 23:17:21 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805 --- Comment #20 from Mark Millard <firstname.lastname@example.org> --- (In reply to Robert Clausecker from comment #0) Ultimately, using main [so: 14], I've not been able to reproduce any "after displaying the beastie menu" crashes based on USB storage having been connected during the boot. USB3.2 and USB3.0 devices. I cover 3 of the 4 combinations relative to port types for my test context: USB3.2 in USB-C port (no "umass0" or no "umass1" or . . .) USB3.2 in USB-A port (works) USB3.0 in USB-A port (works) Unfortunately, I do not have a way to form a USB3.0/USB-C combination. The USB3.2 in USB-C port case has differing consequences for boot media (no root mount or the like) vs. having the same result as not plugging the drive into a port at all: not detected. (In my context, the FreeBSD boot media is always a "umass*".) I no longer maintain an environment for building stable/* or releng/* variants. So it may be a main vs. releng distinction compared to your results. I've not checked. I'll also note that I do not have access to a variety of media of the types listed. It could be some other distinction is involved that happens to correlate with USB3.2 in my context and that some other USB3.2 storage media would work. I've no way to know from what I've available to test. (Of course, a bunch of my comments ended up being the process of figuring my own operator error: All those reporting a Synchronous Exception.) -- You are receiving this mail because: You are the assignee for the bug.