slow system freeze - data

[Benjamin Lutz]

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20041228/924cdcf3/attachment.bin