On 13/11/17(Mon) 10:03, Stuart Henderson wrote: > On 2017/11/13 08:44, Martin Pieuchot wrote: > > On 12/11/17(Sun) 22:10, Stuart Henderson wrote: > > > On 2017/11/12 22:48, Martin Pieuchot wrote: > > > > On 12/11/17(Sun) 21:30, Stuart Henderson wrote: > > > > > iked box, GENERIC.MP + WITNESS, -current as of Friday 10th: > > > > > > > > Weird, did you tweak "kern.splassert" on this box? Otherwise is looks > > > > like a major corruption. > > > > > > It would have kern.splassert=2. (I know this can cause problems > > > sometimes, though this would be the first time in 5+ years I've bumped > > > into it, most of my routers where I have serial console have this set). > > > > Well the panic below correspond to a value of 0 or > 3. > > Confirmed, it was definitely set to 2.
So it seems that two of your CPU end up looking at/dealing with corrupted memory... > > > I'm trying to get more information because it had either hanged or > > > panicked previously (it didn't have serial connected at the time and > > > the machine was needed so it had to be rebooted before I had chance > > > to dig into it). > > > > From which snapshot was the kernel that hanged or panic'd? > > > > It was running this: > > OpenBSD 6.2-current (GENERIC.MP) #199: Tue Nov 7 18:41:54 MST 2017 > > I've got it onto a remote control PDU now, now looking for some machine > with an old enough ssh client to be able to connect to the PDU :-| > > Which kernel would be most useful to run now? -current > I have now moved it to -current GENERIC.MP with the "fast path chunk > removed from amd64/amd64/fpu.c fpu_kernel_enter() which we still suspect > as maybe having some issues. That's perfect from my point of view.
