Dave Voutila <[email protected]> wrote: > Is mispeaking? This is what I experienced: > > panic: acquiring blockable sleep lock with spinlock or critical section > held (kernel_lock) &kernel_lock > > Full backtraces of two occurrences: https://imgur.com/a/vKIe3k7
It looks like this began with sys_generic.c 1.130 (hey mpi) previously selwakeup() was not grabbing the kernel lock and could be called for LOG_CONS on a pty below kernel printf, as it was mostly just doing wakeup related actions.
