Re: panic: sleeping thread owns a non-sleepable lock

From: Peter Holm <peter_at_holm.cc>
Date: Tue, 23 Nov 2004 02:13:07 +0100
On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote:
> On Monday 22 November 2004 09:38 am, Peter Holm wrote:
> > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got:
> > Sleeping on "fdesc" with the following non-sleepable locks held:
> > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked _at_
> > kern/kern_descrip.c:2425 and then
> > panic: sleeping thread (pid 92279) owns a non-sleepable lock
> >
> > http://www.holm.cc/stress/log/cons89.html
> 
> Yes, the panic is a result of the earlier warning.  Poul-Henning touched this 
> code last, so it is probably something for him to look at.  I'm unsure how 
> msleep() is getting called, however.  The turnstile panic is not important, 
> can you find the thread that went to sleep (should be pid 92279) and get 
> stack trace for that?
> 

The ddb trace is in the log, just before call doadump. Let me know if you
need any gdb output.
-- 
Peter Holm
Received on Tue Nov 23 2004 - 00:13:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:23 UTC