From: Oleg Drokin <green@linuxhacker.ru>
To: Fernando.Paredes@sun.com, linux-kernel@vger.kernel.org
Subject: Re: Toshiba keyboard lockups
Date: Thu, 10 Jun 2004 22:15:12 +0300 [thread overview]
Message-ID: <200406101915.i5AJFCBu197611@car.linuxhacker.ru> (raw)
In-Reply-To: <40C7880C.4000401@sun.com>
Hello!
Fernando Paredes <Fernando.Paredes@sun.com> wrote:
FP> Applied these patches. Nothing while tail'ing /var/log/messages. Nothing
FP> in the root console that I can see either.
FP> Patched the source to 2.6.6. Still get the same lockups, totally random.
FP> Any more ideas?
Not sure if I have exact problem like you do, but at least I have something
similar. Once in a while keyboard suddenly stopps working, touchpad still work
though (I have Toshiba Satellite Pro (centrino based) laptop here).
I figured out that if I leave the keyboard for some time (up to 2 minutes),
it starts to work again, at least this was the case with XFree 4.4,
during those no-keyboard times, mouse cursor was moving with small jumps
(when keyboard works it moves smoothly).
I upgraded to FC2 (and hence to xorg X server) today, and lockup happened
once already, the "wait for some time" strategy did not work, so I
remembered initially I thought this was something bad pressed on keyboard
(btw, usually lockups happens when I press several keys at the same time by
accident (but not always when I do this)), so I was pressing various
modifier keys and Fn-Fx stuff. (Fn is one key, Fx is set of functional keys).
So today after some waiting I jut pressed alt+ctrl+shifts in some
conbinations and it unfroze almost immediately to my surprise.
Also I can add that sometimes when I press more than one alphanumeric key,
I get this sort of message from kernel:
"atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed."
Also sometimes (not always) after the freeze/unfreeze I get various messages
from atkbd.c, here are some examples:
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
(numbers may differ from time to time)
atkbd.c: Unknown key pressed (translated set 0, code 0x1d on isa0060/serio0).
atkbd.c: Use 'setkeycodes 1d <keycode>' to make it known.
(numbers may differ from time to time voth in keycode and in translated set)
atkbd.c: Unknown key pressed (translated set 0, code 0x22 on isa0060/serio0).
(again numbers may vary)
atkbd.c: Failed to enable keyboard on isa0060/serio0
(this is some ancient message from October 25th, 2004, seen it only once,
just prior to reeboot, according to logs, do not remember details).
And also I often see multiple
"input: AT Translated Set 2 keyboard on isa0060/serio0" messages.
And new ones are appearing after the freeze/unfreeze. (not every time, though).
May be that will help someone.
Bye,
Oleg
next prev parent reply other threads:[~2004-06-10 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 23:33 Fernando Paredes
2004-05-12 9:49 ` R. J. Wysocki
2004-06-09 21:58 ` Fernando Paredes
2004-06-10 19:15 ` Oleg Drokin [this message]
2004-06-10 20:46 ` Jason Munro
2004-06-10 22:05 ` Fernando Paredes
2004-07-06 8:48 ` Ralf Hildebrandt
2004-07-12 9:20 ` Ralf Hildebrandt
2004-06-15 7:51 ` Sean Legassick
2004-06-17 22:37 ` Gabriel Lavoie
2004-06-19 18:36 ` Vojtech Pavlik
2004-06-19 19:48 ` R. J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406101915.i5AJFCBu197611@car.linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=Fernando.Paredes@sun.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®