Date: Tue, 28 Dec 2004 12:38:44 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Benjamin Lutz <benlutz@datacomm.ch> Cc: freebsd-stable@freebsd.org Subject: Re: slow system freeze - data Message-ID: <20041228013844.GC7189@cirb503493.alcatel.com.au> In-Reply-To: <200412260814.53592.benlutz@datacomm.ch> References: <Pine.NEB.3.96L.1041223102130.89131C-100000@fledge.watson.org> <200412260814.53592.benlutz@datacomm.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041228013844.GC7189>