Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-13 Thread Martin Pieuchot
On 13/11/17(Mon) 12:33, Stuart Henderson wrote: > On 2017/11/13 13:17, Martin Pieuchot wrote: > > [...] > > So it seems that two of your CPU end up looking at/dealing with > > corrupted memory... > > Is that for sure? 2 does normally print a trace, 3 also drops into ddb. But none of them print:

Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-13 Thread Sebastien Marie
On Mon, Nov 13, 2017 at 12:33:35PM +, Stuart Henderson wrote: > > Same after an hour or two uptime, but this time I get some "netlock: > lock not held" from some cpu or other, and some functions in the bits of > the trace that get displayed: > > login: panic: kernel diagnostic assertion

Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-13 Thread Stuart Henderson
On 2017/11/13 13:17, Martin Pieuchot wrote: > 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

Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-13 Thread Martin Pieuchot
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,

Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-13 Thread Stuart Henderson
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

Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-12 Thread Martin Pieuchot
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 > >

Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-12 Thread Stuart Henderson
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

Re: assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-12 Thread Martin Pieuchot
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. > login: panic: kernel diagnostic assertion "_kernel_lock_held()" failed: file >

assertion "_kernel_lock_held()" failed, uipc_socket2.c: ipsec

2017-11-12 Thread Stuart Henderson
iked box, GENERIC.MP + WITNESS, -current as of Friday 10th: login: panic: kernel diagnostic assertion "_kernel_lock_held()" failed: file "/src/cvs-openbsd/sys/kern/uipc_socket2.c", line 310 splassert: soassertlocked: want 1 have 256 panic: spl assertion failure in soassertlocked Starting stack