On 2018-04-17, Rodney Polkinghorne <this...@gmail.com> wrote: > Dear list > > My old Dell laptop ran stably under 6.1. After I upgraded to 6.2, > the kernel started to crash with "page fault trap, code=0" every > time I started the X server. Every other time, this left the file > system in a state that fsck could not repair. I don't have a spare > laptop for debugging, and it took me a while to install OpenBSD on > a USB key where I was happy to reproduce the crash. (OK, I was > lazy, and I hoped that someone else would encounter this fault who > was in a better position to diagnose it.) > > This could be a hardware fault. However, it occurs consistently, > when booting from both the hard disk and a USB key. Version 6.1 > has always worked. > > The fault still happens in 6.3 and in recent snapshots. I would > like to follow the instructions in crash(8) about capturing the > output of the ps and trace commands, rebooting, and emailing a > dmesg. > > The problem is that the machine won't reboot from ddb. When I run > "boot reboot", it either hangs or panics, and I have to power cycle > and lose the message buffer. > > What's the best way forward? I could take some screen shots with > a camera and post them on the web. Alternatively, I'm in Melbourne, > and I'd be happy to lend the laptop to a local developer. > > Rodney > >
Try "call cpu_reset". Or take photos and please transcribe the most important bits - at least the panic / crash string and function names from 'trace' - it's a lot quicker to figure out who needs to see it if those are available in plaintext in the email.
