From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 01:38:52 2004 Return-Path: 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 0B31B16A4CE for ; Tue, 28 Dec 2004 01:38:52 +0000 (GMT) Received: from mail28.syd.optusnet.com.au (mail28.syd.optusnet.com.au [211.29.133.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 436F543D54 for ; Tue, 28 Dec 2004 01:38:51 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iBS1cjAZ026988 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 28 Dec 2004 12:38:46 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iBS1cjxP015976; Tue, 28 Dec 2004 12:38:45 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iBS1ciXW015975; Tue, 28 Dec 2004 12:38:45 +1100 (EST) (envelope-from pjeremy) Date: Tue, 28 Dec 2004 12:38:44 +1100 From: Peter Jeremy To: Benjamin Lutz Message-ID: <20041228013844.GC7189@cirb503493.alcatel.com.au> References: <200412260814.53592.benlutz@datacomm.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412260814.53592.benlutz@datacomm.ch> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: slow system freeze - data X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 28 Dec 2004 01:38:52 -0000 On Sun, 2004-Dec-26 08:14:49 +0100, Benjamin Lutz wrote: >The freeze just happened again. I managed to get into the debugger and get >some info. The info you dumped shows that there's a filesystem deadlock on ad4s1f. This is consistent with the behaviour you reported - the system is running "normally" but as soon as a process trys to access that filesystem, it freezes. Eventually, everything all processes are frozen. Unfortunately, it's not clear (to me) where to go next. Printing the locked vnodes might help but that's not easy to do without gdb. >The first app that froze as far as I could tell was xmms. Actually, the locks suggest that the problem started with pid 678 - kdeinit. This is unlikely to be -- Peter Jeremy