On Tue, Jul 12, 2016 at 12:09:03AM +0200, stolendata.net wrote: > GENERIC.MP AMD64/5.9-release booted from full install on USB disk behaves > the exact same way as the ramdisk kernel, stops booting at the same point. > Do you want me to try a full i386 install as well? >
Please, since at least i386 panics. You might get into ddb and can do a backtrace. -ml > On Mon, Jul 11, 2016 at 11:41 PM, Mike Larkin <mlar...@azathoth.net> wrote: > > > On Mon, Jul 11, 2016 at 11:36:22PM +0200, stolendata.net wrote: > > > > > > > > If it's of any value to help narrow the problem down, this particular CPU > > > model is probably not the culprit. I've been running OpenBSD on one on > > > another board since 4.9. > > > > > > > Even though you don't have a full install, can you try booting a regular > > non-ramdisk kernel instead? The ramdisk kernel has a bunch of stuff > > stripped > > out (including ddb), and trying a regular kernel may give us more data > > points. > > Of course, it won't boot since you don't have a full install, but if it > > gets > > that far, that's information as well. > > > > This can be done in a variety of ways, including using another machine and > > installing to a USB stick. > > > > -ml > > > > > > > > On Mon, Jul 11, 2016 at 11:05 PM, Mike Larkin <mlar...@azathoth.net> > > wrote: > > > > > > > On Mon, Jul 11, 2016 at 10:37:23PM +0200, stolendata.net wrote: > > > > > > > > > With 5.9/AMD64-release the kernel manages to get just a few steps > > > > further, > > > > > crashing after a few lines of the "BIOS0" enumeration. If a picture > > of > > > > this > > > > > would help let me know and I'll fire the machine up again. I've tried > > > > > > > > This would be nice, if you could. It would indicate if i386 and amd64 > > are > > > > failing at the same place. > > > > > > > > -ml > > > > > > > > > >
