From owner-freebsd-stable@FreeBSD.ORG Mon Apr 24 13:26:30 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62E5516A402 for ; Mon, 24 Apr 2006 13:26:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E257843D46 for ; Mon, 24 Apr 2006 13:26:29 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id BC3A446BA8; Mon, 24 Apr 2006 09:26:28 -0400 (EDT) Date: Mon, 24 Apr 2006 14:26:28 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Henri Hennebert In-Reply-To: <20060420093147.7j9stegaiocc0ok4@webmail.restart.be> Message-ID: <20060424142455.G44099@fledge.watson.org> References: <20060420093147.7j9stegaiocc0ok4@webmail.restart.be> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org Subject: Re: 6.1RC system nearly freezing 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: Mon, 24 Apr 2006 13:26:30 -0000 On Thu, 20 Apr 2006, Henri Hennebert wrote: > I upgrade a web, squid, mail server (under SMP with 2 pentium III) to 6.1-RC > (Apr 9 2006) and encounter 2 `freezing'. > > The system is still responding to http requests but I can't login on the > console or through ssh -- no shell prompt. No more mail delivery. > > I break to KDB and found more then 1000 sendmail processes waiting for > devfs... > > call boot(0) can't complete the shutdown process. > > I join the KDB informations. Let me know if more informations are needed. Are you running with WITNESS and INVARIANTS enabled? If not, could you do so and see if the problem is reproduceable, and if so, whether or not WITNESS (and friends) generate any warnings? It looks like something has leaked a lock, resulting in deadlock. The question is, however, which lock, and where. WITNESS may be able to provide some insight into this; if you could run "show alllocks" with WITNESS in place, that would be helpful also. Robert N M Watson