From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 22:00:02 2004 Return-Path: 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 94EAD16A4CF for ; Mon, 22 Nov 2004 22:00:02 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4381743D1F for ; Mon, 22 Nov 2004 22:00:02 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20559 invoked from network); 22 Nov 2004 22:00:02 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Nov 2004 22:00:01 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAMLxdYj030036; Mon, 22 Nov 2004 16:59:58 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Peter Holm Date: Mon, 22 Nov 2004 16:57:36 -0500 User-Agent: KMail/1.6.2 References: <20041122143804.GA36649@peter.osted.lan> In-Reply-To: <20041122143804.GA36649@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200411221657.36659.jhb@FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: phk@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 22:00:02 -0000 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? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org