Hi, I've also ran into this. Reported here [1] (a new email with some more stack traces should be landing soon).
BR, Pedro Caetano [1] https://marc.info/?l=openbsd-bugs&m=148581520804370&w=2 On Mon, Jan 30, 2017 at 11:12 PM, Hrvoje Popovski <hrv...@srce.hr> wrote: > On 25.1.2017. 7:32, Martin Pieuchot wrote: > > I just enabled the NET_LOCK() again and I'm looking for test reports. > > Please go build a kernel from sources or wait for the next snapshot, > > run it and report back. > > > > If you're looking for some small coding tasks related to the NET_LOCK() > > just do: > > > > # sysctl kern.splassert=2 > > # sysctl kern.pool_debug=2 > > > > Then watch for the traces on your console. > > > > source is fetched half an hour ago and i think that this one is new > > > splassert: yield: want 0 have 1 > Starting stack trace... > yield() at yield+0xac > pool_get() at pool_get+0x1ca > pf_osfp_add() at pf_osfp_add+0x145 > pfioctl() at pfioctl+0x13f8 > VOP_IOCTL() at VOP_IOCTL+0x44 > vn_ioctl() at vn_ioctl+0x77 > sys_ioctl() at sys_ioctl+0x1b1 > syscall() at syscall+0x27b > --- syscall (number 54) --- > end of kernel > end trace frame: 0x2, count: 249 > 0xd71fb72f43a: > End of stack trace. > >
