From owner-freebsd-current@FreeBSD.ORG Wed Oct 13 18:02:11 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 4645916A4E6 for ; Wed, 13 Oct 2004 18:02:11 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0818A43D64 for ; Wed, 13 Oct 2004 18:02:11 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13856 invoked from network); 13 Oct 2004 18:02:10 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 13 Oct 2004 18:02:10 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i9DI1wSZ001485; Wed, 13 Oct 2004 14:02:06 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Wed, 13 Oct 2004 13:47:23 -0400 User-Agent: KMail/1.6.2 References: <20041013075048.GA88808@peter.osted.lan> In-Reply-To: <20041013075048.GA88808@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410131347.23035.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org Subject: Re: panic: process 32827(tcpblast):2 holds Giant but isn't blocked on a 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: Wed, 13 Oct 2004 18:02:11 -0000 On Wednesday 13 October 2004 03:50 am, Peter Holm wrote: > This is with GENERIC HEAD from Oct 12 12:56 UTC. More info @ > http://www.holm.cc/stress/log/cons84.html The thread is in the state TDS_CAN_RUN so it's runnable but not on a run queue or running. The only way that I know that this can happen is if priority propagation happens after the system has already panic'd in which case you are about to deadlock anyhow since you are blocking on a lock owned by a thread that will never get to run again. You can try adjusting propagate_priority() to treat TD_CAN_RUN(td) the same as TD_IS_RUNNING(td) and maybe you will get your original panic message. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org