From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 02:35:56 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 995FE16A4CE for ; Tue, 28 Dec 2004 02:35:56 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64ECC43D5A for ; Tue, 28 Dec 2004 02:35:56 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2BC6A512C4; Mon, 27 Dec 2004 18:34:24 -0800 (PST) Date: Mon, 27 Dec 2004 18:34:24 -0800 From: Kris Kennaway To: Peter Jeremy Message-ID: <20041228023424.GA73310@xor.obsecurity.org> References: <200412260814.53592.benlutz@datacomm.ch> <20041228013844.GC7189@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <20041228013844.GC7189@cirb503493.alcatel.com.au> User-Agent: Mutt/1.4.2.1i cc: Benjamin Lutz 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 02:35:56 -0000 --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 28, 2004 at 12:38:44PM +1100, Peter Jeremy wrote: > 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 g= et=20 > >some info. >=20 > 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. >=20 > 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. >=20 > >The first app that froze as far as I could tell was xmms. >=20 > Actually, the locks suggest that the problem started with pid 678 - kdein= it. > This is unlikely to be=20 Does xmms try to run with rtprio or idprio? Those are still broken, and can lead to deadlocks, afaik. Kris --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0MYvWry0BWjoQKURApuAAJoD9LfsY/4TuBlHNgcydJC9/qUQqwCfXvYL D5A62lxIFwHW6Z/sIlcU8ZQ= =EZeE -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C--