-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Nov 9, 2007, at 13:34, Frank Wille wrote:

> Michael Lorenz wrote:
>
>>> [..awacs causing deadlock..]
>> Ouch, that does look like an interrupt deadlock.
>>
>>> This is a PowerMac G4 (Sawtooth) 400 MHz with 1.25 GB RAM. The load
>>> was not
>>> too high (mainly caused by Firefox). I was just starting a new live
>>> stream on
>>> xmms when it happened.
>>
>> Ok, my G4 isn't too different from that ( AGP, 2x 500MHz G4, 896MB )
>> - - - let's see if I can reproduce it. I've been listening to music a
>> lot, maybe network activity at the same time triggers it.
>
> Did you make it?
No deadlock here.

> I was able to repeat it a few times now. Just run xmms with an MP3  
> radio
> live-stream in background. Then compile a few packages, or download  
> some
> files with firefox.
I did build a lot of stuff over nfs with audio playing.

> BTW, seems that the lockup is not  instantly. The last two times I  
> observed
> that it takes 1 or 2 seconds where the mouse-pointer becomes very  
> slow and
> starts jumping, before everything freezes.
Hmm, I sometimes see that with some process bombing the kernel with  
system calls. But that's no deadlock, it just responds very, very  
slowly.

> But the music keeps playing, which means that the network still works
> (although I cannot login).
Can you reproduce this with something else than playing an audio  
stream? It looks more like a process running amok than awacs acting  
up right now.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBRzT0RspnzkX8Yg2nAQK0nwf+Nj7gTpdDc7duOvo/5mjPLoTzYTR43dNn
je1nOa4tk2/+e7NPhPNSN3c2I9RKaQXlUm3PuUUymscH2e7vs888qc5K7OcOcQRA
FmkVkpU7gac81qlsDxI4nR7v9RRDWoGAHWH9n3b370EYHzdOv3coxePMXhTM20WD
CHRNspYhRJm4WYMZHsbz0KQq8dGfix061WDALyIQLhoNW8BBa8fsfEieQXgKlvr1
yzpZWO2VW1cIkNQxSZPh5D/XtPsKJxmsMtR4C3LwaPSJfyAhaJaLeE0Zw1lATef3
SaDQjO4Cq/5QY3e+JkTrBoS/MdkruKOSXUAxsR8pIFUPElCFR5ZKzg==
=hjQS
-----END PGP SIGNATURE-----