Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: diagnostic assertion curcpu()->ci_biglock_count == 0 failed


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: kernel_lock leaked
> cpu12: Begin traceback
> vpanic
> kern_assert
> exit1
> sys_exit
> syscall

The source of this problem is not going to be identified any time soon, so I
put back an unconditional release for kernel_lock there, so the panic should
no longer occur.  In theory LOCKDEBUG should catch this but it changes the
timing so much it may not happen.


Home | Main Index | Thread Index | Old Index