X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something
Hi,
I realized that my computer (this one, Debian Lenny, w. k.
2.6.26-2-686-bigmem) was frozen. I tried escaping from the screensaver,
but nothing worked, except launching another tty, and restarting gdm.
Here is the interesting output I obtained by looking at /var/log/syslog
and dmesg:
==
[24892.623421] atkbd.c: Unknown key pressed (translated set 2, code 0xbb
on isa0060/serio0).
[24892.623421] atkbd.c: Use 'setkeycodes e03b <keycode>' to make it known.
[24892.691424] atkbd.c: Unknown key released (translated set 2, code
0xbb on isa0060/serio0).
[24892.691424] atkbd.c: Use 'setkeycodes e03b <keycode>' to make it known.
==
and
==
May 18 17:59:00 merciadriluca-station kernel: [24892.623421] atkbd.c:
Unknown key pressed (translated set 2, code 0xbb on isa0060/serio0).
May 18 17:59:00 merciadriluca-station kernel: [24892.623421] atkbd.c:
Use 'setkeycodes e03b <keycode>' to make it known.
May 18 17:59:00 merciadriluca-station kernel: [24892.691424] atkbd.c:
Unknown key released (translated set 2, code 0xbb on isa0060/serio0).
May 18 17:59:00 merciadriluca-station kernel: [24892.691424] atkbd.c:
Use 'setkeycodes e03b <keycode>' to make it known.
==
Could it be that? What should it mean?
Thanks.
--
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
I use PGP. If there is an incompatibility problem with your mail
client, please contact me.
05-18-2010, 05:20 PM
Camaleón
X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something
On Tue, 18 May 2010 18:08:24 +0200, Merciadri Luca wrote:
> I realized that my computer (this one, Debian Lenny, w. k.
> 2.6.26-2-686-bigmem) was frozen. I tried escaping from the screensaver,
> but nothing worked, except launching another tty, and restarting gdm.
> Here is the interesting output I obtained by looking at /var/log/syslog
> and dmesg:
>
> ==
> [24892.623421] atkbd.c: Unknown key pressed (translated set 2, code 0xbb
> on isa0060/serio0).
(...)
That seems to be unrelated with a X freeze. Looks like a keyboard key
mapping error but nothing serious.
Just review your "/var/log/Xorg.0.log". If X crashed there must something
there :-?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.05.18.17.20.50@gmail.com">http://lists.debian.org/pan.2010.05.18.17.20.50@gmail.com
05-18-2010, 06:08 PM
Merciadri Luca
X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Camaleón <noelamac@gmail.com> writes:
> On Tue, 18 May 2010 18:08:24 +0200, Merciadri Luca wrote:
>
>> I realized that my computer (this one, Debian Lenny, w. k.
>> 2.6.26-2-686-bigmem) was frozen. I tried escaping from the screensaver,
>> but nothing worked, except launching another tty, and restarting gdm.
>> Here is the interesting output I obtained by looking at /var/log/syslog
>> and dmesg:
>>
>> ==
>> [24892.623421] atkbd.c: Unknown key pressed (translated set 2, code 0xbb
>> on isa0060/serio0).
>
> (...)
>
> That seems to be unrelated with a X freeze. Looks like a keyboard key
> mapping error but nothing serious.
>
> Just review your "/var/log/Xorg.0.log". If X crashed there must something
> there :-?
Nothing really interesting there. Just:
==
AUDIT: Tue May 18 18:01:04 2010: 3716 X: client 33 rejected from local host (uid 0)
Auth name: MIT-MAGIC-COOKIE-1 ID: -1
==
but 18:01:24 seems to be when I asked to restart gdm.
Note that I do not think that X crashed entirely. I just mean that the
screen was looking like frozen, but screensaver was still
moving... slowly, or sometimes really slowly.
- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
- --
All flowers are not in one garden.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 877hn1ytfh.fsf@merciadriluca-station.MERCIADRILUCA">http://lists.debian.org/877hn1ytfh.fsf@merciadriluca-station.MERCIADRILUCA
05-18-2010, 08:02 PM
Camaleón
X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something
On Tue, 18 May 2010 20:08:02 +0200, Merciadri Luca wrote:
> Camaleón writes:
>> Just review your "/var/log/Xorg.0.log". If X crashed there must
>> something there :-?
> Nothing really interesting there. Just:
>
> ==
> AUDIT: Tue May 18 18:01:04 2010: 3716 X: client 33 rejected from local
> host (uid 0)
> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
> ==
> but 18:01:24 seems to be when I asked to restart gdm.
Nothing more in the rest of the "/var/log/Xorg.x.log" files?
> Note that I do not think that X crashed entirely. I just mean that the
> screen was looking like frozen, but screensaver was still moving...
> slowly, or sometimes really slowly.
Next time it happens, go to a tty and type "top" to list the processes in
use. Sort the table by CPU cycles and/or memory use. The slowness could
be caused by a "rampant" program consuming a lot of resources.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.05.18.20.02.09@gmail.com">http://lists.debian.org/pan.2010.05.18.20.02.09@gmail.com
05-18-2010, 08:55 PM
Merciadri Luca
X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Camaleón <noelamac@gmail.com> writes:
> On Tue, 18 May 2010 20:08:02 +0200, Merciadri Luca wrote:
>
>> Camaleón writes:
>
>>> Just review your "/var/log/Xorg.0.log". If X crashed there must
>>> something there :-?
>> Nothing really interesting there. Just:
>>
>> ==
>> AUDIT: Tue May 18 18:01:04 2010: 3716 X: client 33 rejected from local
>> host (uid 0)
>> Auth name: MIT-MAGIC-COOKIE-1 ID: -1
>> ==
>> but 18:01:24 seems to be when I asked to restart gdm.
>
> Nothing more in the rest of the "/var/log/Xorg.x.log" files?
No. Weird.
>
>> Note that I do not think that X crashed entirely. I just mean that the
>> screen was looking like frozen, but screensaver was still moving...
>> slowly, or sometimes really slowly.
>
> Next time it happens, go to a tty and type "top" to list the processes in
> use. Sort the table by CPU cycles and/or memory use. The slowness could
> be caused by a "rampant" program consuming a lot of resources.
Okay. Thanks!
- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
- --
Love is like war, Easy to start, Hard to end, Impossible to forget.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87fx1p7wwj.fsf@merciadriluca-station.MERCIADRILUCA">http://lists.debian.org/87fx1p7wwj.fsf@merciadriluca-station.MERCIADRILUCA