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

In message <200411221657.36659.jhb_at_FreeBSD.org>, John Baldwin writes:
>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?

There is a patch for this in perforce phk_bufwork::sys/kern/kern_descrip.c
now.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.