From owner-freebsd-current@FreeBSD.ORG  Mon Nov 22 23:08:54 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 88CC116A4CE; Mon, 22 Nov 2004 23:08:54 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C93BA43D46; Mon, 22 Nov 2004 23:08:53 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAMN8qLT031188;
	Tue, 23 Nov 2004 00:08:52 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: John Baldwin <jhb@FreeBSD.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 22 Nov 2004 16:57:36 EST."
             <200411221657.36659.jhb@FreeBSD.org> 
Date: Tue, 23 Nov 2004 00:08:52 +0100
Message-ID: <31187.1101164932@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: current@FreeBSD.org
Subject: Re: panic: sleeping thread owns a non-sleepable lock 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2004 23:08:54 -0000

In message <200411221657.36659.jhb@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 @
>> 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?

This one is a known trouble-spot but I don't know how to solve it.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@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.