Hi,
On Sun, Feb 23, 2020 at 10:30:24AM +0100, Thomas Klausner wrote:
> With a 9.99.47/amd64 kernel from February 16, I just had panic (handcopied):
>
> panic: kernel diagnostic assertion "curcpu()->ci_biglock_count == 0" failed:
> file .../kern_exit.c line 214: k
Can someone please offer a another set of eyes on this commit?
https://github.com/NetBSD/src/commit/065ad9b5c35f8798d18fe75356b2c22ee42a4896
Removing KERNEL_UNLOCK_ALLs feels wild. But I don't understand the code
well enough to know whether it's right.
Hi Thomas.
On Sun, Feb 23, 2020 at 10:30:24AM +0100, Thomas Klausner wrote:
> With a 9.99.47/amd64 kernel from February 16, I just had panic (handcopied):
>
> panic: kernel diagnostic assertion "curcpu()->ci_biglock_count == 0" failed:
> file .../kern_exit.c lin
Hi!
With a 9.99.47/amd64 kernel from February 16, I just had panic (handcopied):
panic: kernel diagnostic assertion "curcpu()->ci_biglock_count == 0" failed:
file .../kern_exit.c line 214: kernel_lock leaked
cpu12: Begin traceback
vpanic
kern_assert
exit1
sys_exit
syscall
-- sysc
