On Tue, Dec 01, 2020 at 09:33:25PM +0000, James Cook wrote: > > A few things to try: > > > > - Does it boot with bsd.sp instead of bsd.mp? > > It boots fine, just like bsd.mp. > > (I used https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd > downloaded just a few minutes ago.) > > > - What happens if you disable the following drivers in the bsd.mp kernel: > > > > pchgpio > > acpibtn > > acpiac > > acpibat > > acpihid > > acpipwrres > > acpicpu > > "disable acpiwrres" did nothing so I disabled acpipwrres instead (just > guessing). > > With all those disabled, bsd.mp still boots fine. > > > Cheers, > > > > Mark > > -- > James
A few more scraps of information: - I tried booting earlier releases. Unfortunately miniroot64.fs, miniroot65.fs and miniroot66.fs all run into a different problem: it hangs after output like the following booting hd0a:/bsd: ... entry point at 0x1001000 Booting from miniroot67.fs hangs soon after "root on rd0a..." as I originally reported. I could try even earlier releases if you think the "entry point at ..." bug might be gone. - I also tried the latest snapshot miniroot68.img, and still observe the problem. (The build date printed when it booted was "Wed Dec 16 02:04:55 MST 2020".) - I noticed that after the boot process gets stuck, if I unplug and plug in the USB device, I see messages on the console reporting this. So, the kernel is not completely frozen. - epony@ on IRC suggested I try booting from an SDcard or network in case it's related to USB, but it seems my BIOS doesn't support either boot option (at least, without a wired ethernet adaptor). Suggestions are welcome. In the meantime I am slowly trying to debug this myself, mostly as a learning exercise. I've successfully built my own bsd.rd (using the instructions on the release(8) man page) with the intention of adding some debug output to narrow down where it's getting stuck, but I don't know my way around the kernel code. -- James
