From owner-freebsd-stable@FreeBSD.ORG Tue Jul 26 09:21:55 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CD74106564A; Tue, 26 Jul 2011 09:21:55 +0000 (UTC) (envelope-from amon@aelita.org) Received: from aelita.org (unknown [IPv6:2001:7a8:7003::3]) by mx1.freebsd.org (Postfix) with ESMTP id 1579B8FC13; Tue, 26 Jul 2011 09:21:54 +0000 (UTC) Received: from ra.aabs (localhost [127.0.0.1]) by aelita.org (8.14.4/8.14.4) with ESMTP id p6QBHqpO090950; Tue, 26 Jul 2011 13:17:52 +0200 (CEST) (envelope-from amon@ra.aabs) Received: (from amon@localhost) by ra.aabs (8.14.4/8.14.4/Submit) id p6QBHqYT090949; Tue, 26 Jul 2011 13:17:52 +0200 (CEST) (envelope-from amon) Date: Tue, 26 Jul 2011 13:17:52 +0200 From: Herve Boulouis To: Kostik Belousov Message-ID: <20110726111752.GG17204@ra.aabs> References: <20110725102107.GB17204@ra.aabs> <20110725085902.GM17489@deviant.kiev.zoral.com.ua> <20110726094913.GF17204@ra.aabs> <20110726090652.GE17489@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20110726090652.GE17489@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: rmacklem@freebsd.org, Herve Boulouis , freebsd-stable@freebsd.org Subject: Re: Sleeping thread owns a nonsleepable lock panic (& lor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 09:21:55 -0000 Le 26/07/2011 12:06, Kostik Belousov a écrit: > On Tue, Jul 26, 2011 at 11:49:13AM +0200, Herve Boulouis wrote: > > Le 25/07/2011 11:59, Kostik Belousov a ?crit: > > > > Ok the patched server crashed this morning strangely : all httpd processes were stuck in nfs or vmopar > > and were unkillable. Below is the full ps. > > Please see the > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > for information required to debug the deadlocks. the box was not stricly deadlocked since I was able to interact with it but I suppose you want me to break into debugger when the symptoms appears again and report all the commands listed in the handbook deadlock section ? Regards, -- Herve Boulouis