Date: Mon, 27 Dec 2004 18:34:24 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: slow system freeze - data Message-ID: <20041228023424.GA73310@xor.obsecurity.org> In-Reply-To: <20041228013844.GC7189@cirb503493.alcatel.com.au> References: <Pine.NEB.3.96L.1041223102130.89131C-100000@fledge.watson.org> <200412260814.53592.benlutz@datacomm.ch> <20041228013844.GC7189@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 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 Does xmms try to run with rtprio or idprio? Those are still broken, and can lead to deadlocks, afaik. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0MYvWry0BWjoQKURApuAAJoD9LfsY/4TuBlHNgcydJC9/qUQqwCfXvYL D5A62lxIFwHW6Z/sIlcU8ZQ= =EZeE -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041228023424.GA73310>