From owner-freebsd-current@FreeBSD.ORG Tue Feb 8 18:32:14 2005 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 511F516A4CE for ; Tue, 8 Feb 2005 18:32:14 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC36743D48 for ; Tue, 8 Feb 2005 18:32:13 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 19722 invoked from network); 8 Feb 2005 18:32:13 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 8 Feb 2005 18:32:13 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j18IW3GG095656; Tue, 8 Feb 2005 13:32:07 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 8 Feb 2005 13:17:40 -0500 User-Agent: KMail/1.6.2 References: <20050206134113.GA77071@peter.osted.lan> In-Reply-To: <20050206134113.GA77071@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502081317.40267.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: Deadlock with option FULL_PREEMPTION 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: Tue, 08 Feb 2005 18:32:14 -0000 On Sunday 06 February 2005 08:41 am, Peter Holm wrote: > With GENERIC HEAD from Feb 5 09:19 UTC + FULL_PREEMPTION + > mpsafe_vfs = 1 I ran into what appears to be the same deadlock > twice. This is the first one: > http://www.holm.cc/stress/log/cons114.html What is the deadlock exactly? It looks like lots of threads banging on fork() and that they are all waiting on an exclusive lock of allproc_lock while holding a shared lock of proctree_lock (except for the 1 thread currently doing a fork that is on a run queue because it was preempted by IRQ 0 which kicked off softclock). Can you get 'ps' output? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org