Date: Tue, 28 Dec 2004 03:27:00 +0100 From: Benjamin Lutz <benlutz@datacomm.ch> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: slow system freeze - data Message-ID: <200412280327.03752.benlutz@datacomm.ch> 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 --] Hello Peter, > The info you dumped shows that there's a filesystem deadlock on > ad4s1f. In case you haven't guessed, that'd be my /usr. > 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. You mean that's the point where I need serial console access? I hope to have that running after the holidays. > >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 Well, xmms is just the first app where it became apparent :) PID 678 is really kded (at least it is at the moment - It is very likely it was then too, since these low PIDs seem to generally be assigned the same way with each boot). kded appears to be some CORBA-related tool used by KDE. Btw, is my assumption that this is a kernel problem, not a problem with any of my applications, correct? Anyway, many thanks for your help and insight so far, it is appreciated. Greetings Benjamin [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD4DBQBB0MR3gShs4qbRdeQRAtiYAJ418FNV/TcMhH3WHpTOXMSU2jKNXQCXc/us hWLM/9CS3hMfXbKzN5XJcg== =HlTk -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412280327.03752.benlutz>