On Tue, Jul 12, 2016 at 12:30:23AM +0200, stolendata.net wrote: > Alright, ddb prompt pops up on i386. Last output from kernel: > > real mem ... > avail mem ... > kernel: page fault trap, code=0 > Stopped at memcpy+0x13: repe movsl (%esi),%es:(%edi)
in ddb: trace ps take some pictures and send some links. > > If there's any chance you think you can guide me through pulling some > valuable info from here and on, I'm game. > > > On Tue, Jul 12, 2016 at 12:12 AM, Mike Larkin <[email protected]> wrote: > > > 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 <[email protected]> > > 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 > > > > > >
