>>The dmesg is needed. This looks like the disk/usb stick is not being >>found by the OS. > > I was afraid of that. > > Dealing with the first apparent problem, that most of the dmesg scrolls > off the screen, looks to be easy; a quick look at the source reveals > that ddb has an apparently undocumented 'dmesg' command. > > Actually capturing the dmesg looks to be harder; given that this is a > store demo system to which I have very limited access I'm not sure I've > got any better way than hand-writing it all. I've got a couple of ideas > for easier ways to try, but it will take a few days. Are there any > parts of the dmesg that are known to be unnecessary for this purpose, so > I can avoid the work of copying them if I have to fall back to writing > everything down and retyping it? > > Now that I've had time to think about this a bit, I'd guess that the > problem is some new USB controller that OpenBSD doesn't yet understand. > If so, am I correct that all that's really needed is the vendor ID and > device ID of the controller? I'll check for this first, now that I know > how to view the whole dmesg after the panic. > > FWIW this stick boots just fine on lots of other systems, both before > and after this problem system.
AFAIK, if its a USB 3 controller, it is unsupported in OpenBSD.
