Re: awacs driver

Michael Lorenz wrote:

>> 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.

No, nothing does happen here, even after minutes.


>> 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.

Usually there is audio involved, but yesterday I experienced
my first
deadlock without audio: I had disconnected the USB keyboard
and mouse, then
reconnected them. Only the mouse was recognized and the
keyboard seemed to
write to the boot console in background. Parts of the upper
X11-screen were
overwritten by it. I killed the gnome-session and restarted
the X server.
Then worked again for some time until the deadlock
occurs...

But this is probably unrelated.


-- 
    _  Frank Wille (frankphoenix.owl.de)
 _ //  http://sun.hasenbra
ten.de/~frank/
 X/   Phx  #AmigaGer

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

Hello,

On Nov 10, 2007, at 09:51, Frank Wille wrote:

> Michael Lorenz wrote:
>
>>> 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.
>
> No, nothing does happen here, even after minutes.

Ok.

>>> 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.
>
> Usually there is audio involved, but yesterday I
experienced my first
> deadlock without audio: I had disconnected the USB
keyboard and  
> mouse, then
> reconnected them. Only the mouse was recognized and the
keyboard  
> seemed to
> write to the boot console in background. Parts of the
upper X11- 
> screen were
> overwritten by it. I killed the gnome-session and
restarted the X  
> server.
> Then worked again for some time until the deadlock
occurs...

This is strange. When X is running nothing should write to
the  
console unless the machine panics.
Which Xserver are you using? And do you by any chance run it
from a  
different virtual console than 0?

> But this is probably unrelated.

Maybe, maybe not.

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

iQEVAwUBRzXe1MpnzkX8Yg2nAQKiDgf/ZWwnDwewKx/JpnHPkKuMMgxS0XiA
FHJ7
U+ymunxRgneiCvV2O+DGKdv8muZvi/MNvjxf6RgizqbOdfKFYmX6jfTFgyem
Sk9g
VPgsnobjX01EQPIrvE5IgmWV6UM/bhjQGwY7nB4NvkTAvw9szUVlXlwJylc6
k8ey
XwHmOhraUj91QwF+KyTMYLzgKtPz6RT1B/zSk6AlCqlS5PbPhnL25wMBw0Rh
DAPt
i9syQ7abvSlNOdbBOKFJByie0u4rgFt59rsUtWMHjPbF9HobXbj8ZneWicdM
bnlo
LcNaNheLhg4YeXawLp5g+p2MIMO1TuEohWIe9Yc76qvcVt1zmEtTzA==
=OAbQ
-----END PGP SIGNATURE-----