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: pgp1YsPnuP94P.pgp
Description: PGP signature

Reply via email to