Skip to contentSkip to conversation

Keyboard oddness.

DISCUSSION Rob Landley 4 participants 14 messages Sep 20, 2003 – Sep 26, 2003

lore
Share & tools
lore
#0 lore raw

I've mentioned my keyboard repeat problems before. I grepped through the logs and found a whole bunch of these type messages:

Aug 17 05:28:48 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Aug 19 09:06:51 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x8e, 
on isa0060/serio0) pressed.
Aug 22 04:33:36 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xcd, 
on isa0060/serio0) pressed.
Aug 22 10:29:45 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x9f, 
on isa0060/serio0) pressed.
Aug 22 10:43:45 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x9f, 
on isa0060/serio0) pressed.
Aug 24 00:29:57 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Aug 26 19:46:44 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xcd, 
on isa0060/serio0) pressed.
Aug 26 22:18:52 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1cb, 
on isa0060/serio0) pressed.
Aug 26 22:36:32 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Aug 28 05:18:28 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x97, 
on isa0060/serio0) pressed.
Aug 28 07:28:48 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Sep  1 19:18:52 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xcb, 
on isa0060/serio0) pressed.
Sep  1 19:50:52 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  2 00:52:01 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x94, 
on isa0060/serio0) pressed.
Sep  2 13:37:52 localhost kernel: atkbd.c: Unknown key (set 0, scancode 0xfc, 
on isa0060/serio1) pressed.
Sep  2 13:37:52 localhost kernel: atkbd.c: Unknown key (set 0, scancode 0xfc, 
on isa0060/serio1) pressed.
Sep  2 22:31:25 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xb9, 
on isa0060/serio0) pressed.
Sep  3 04:58:47 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Sep  3 14:26:41 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  3 22:03:33 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  3 22:06:53 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  3 22:27:33 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x9e, 
on isa0060/serio0) pressed.
Sep  4 16:00:48 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, 
on isa0060/serio0) pressed.
Sep  5 00:29:00 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  5 00:42:40 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xcd, 
on isa0060/serio0) pressed.
Sep  5 00:43:40 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x92, 
on isa0060/serio0) pressed.
Sep  5 00:52:00 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Sep  5 00:54:40 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Sep  5 01:49:00 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  5 02:24:40 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  5 03:06:00 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xcd, 
on isa0060/serio0) pressed.
Sep  5 14:36:01 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 
on isa0060/serio0) pressed.
Sep  5 14:37:42 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xae, 
on isa0060/serio0) pressed.
Sep  5 15:23:42 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x90, 
on isa0060/serio0) pressed.
Sep  5 15:38:22 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x97, 
on isa0060/serio0) pressed.
Sep  5 16:03:42 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1cb, 
on isa0060/serio0) pressed.
Sep  5 18:16:22 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd0, 

on isa0060/serio0) pressed.

(There's more, it just goes on and on...)

Any clues? (Thinkpad iSeries... 1200, I think.)

Rob

#1 lore raw
Quoted 7 lines · Rob Landley

I've mentioned my keyboard repeat problems before. I grepped through the logs and found a whole bunch of these type messages:

Aug 17 05:28:48 atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Aug 19 09:06:51 atkbd.c: Unknown key (set 2, scancode 0x8e, 

on isa0060/serio0) pressed.

...

These are key releases for keys i8042.c didnt know were down. If otherwise your keyboard functions well, this is harmless.

Quoted 4 lines
Sep  2 13:37:52 atkbd.c: Unknown key (set 0, scancode 0xfc, 
on isa0060/serio1) pressed.
Sep  2 13:37:52 atkbd.c: Unknown key (set 0, scancode 0xfc, 

on isa0060/serio1) pressed.

I suppose these are error codes from your mouse. If so, it is a bug that they ever went to atkbd.c.

Andries

#2 lore raw
Quoted 9 lines · Andries Brouwer
Quoted 7 lines · Rob Landley

I've mentioned my keyboard repeat problems before. I grepped through the logs and found a whole bunch of these type messages:

Aug 17 05:28:48 atkbd.c: Unknown key (set 2, scancode 0x1d0,
on isa0060/serio0) pressed.
Aug 19 09:06:51 atkbd.c: Unknown key (set 2, scancode 0x8e,

on isa0060/serio0) pressed.

Quoted 4 lines

...

These are key releases for keys i8042.c didnt know were down. If otherwise your keyboard functions well, this is harmless.

It doesn't. It's missing key release events left and right. About twice an hour a key well get "stuck". X is okay once you press a second key, but if a VT gets a key stuck, it doesn't come back.

Quoted 7 lines
Quoted 4 lines
Sep  2 13:37:52 atkbd.c: Unknown key (set 0, scancode 0xfc,
on isa0060/serio1) pressed.
Sep  2 13:37:52 atkbd.c: Unknown key (set 0, scancode 0xfc,

on isa0060/serio1) pressed.

I suppose these are error codes from your mouse. If so, it is a bug that they ever went to atkbd.c.

The mouse sometimes sticks as well, just like the keyboard. (Click and the button is held down for no reason.)

I suspect the bug is actually in the new input core...

Quoted 1 line

Andries

Rob

#3 lore raw
In reply to Rob Landley
Quoted 9 lines · Rob Landley

I've mentioned my keyboard repeat problems before. I grepped through the logs and found a whole bunch of these type messages:

Aug 17 05:28:48 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Aug 19 09:06:51 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x8e, 
on isa0060/serio0) pressed.
Aug 22 04:33:36 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xcd, 
Quoted 3 lines

(There's more, it just goes on and on...)

Any clues? (Thinkpad iSeries... 1200, I think.)

What kernel version? Can you test with latest?

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#4 lore raw
Quoted 11 lines · Vojtech Pavlik
Quoted 10 lines · Rob Landley

I've mentioned my keyboard repeat problems before. I grepped through the logs and found a whole bunch of these type messages:

Aug 17 05:28:48 localhost kernel: atkbd.c: Unknown key (set 2, scancode
0x1d0, on isa0060/serio0) pressed.
Aug 19 09:06:51 localhost kernel: atkbd.c: Unknown key (set 2, scancode
0x8e, on isa0060/serio0) pressed.
Aug 22 04:33:36 localhost kernel: atkbd.c: Unknown key (set 2, scancode

0xcd,

Quoted 5 lines
Quoted 3 lines

(There's more, it just goes on and on...)

Any clues? (Thinkpad iSeries... 1200, I think.)

What kernel version? Can you test with latest?

Currently 2.6.0-test5-mm2. It's done it since at least -test3.

Which would be "latest"? -bk8 or -mm3? :)

Rob

#5 lore raw
In reply to Vojtech Pavlik
Quoted 11 lines · Vojtech Pavlik
Quoted 10 lines · Rob Landley

I've mentioned my keyboard repeat problems before. I grepped through the logs and found a whole bunch of these type messages:

Aug 17 05:28:48 localhost kernel: atkbd.c: Unknown key (set 2, scancode
0x1d0, on isa0060/serio0) pressed.
Aug 19 09:06:51 localhost kernel: atkbd.c: Unknown key (set 2, scancode
0x8e, on isa0060/serio0) pressed.
Aug 22 04:33:36 localhost kernel: atkbd.c: Unknown key (set 2, scancode

0xcd,

Quoted 5 lines
Quoted 3 lines

(There's more, it just goes on and on...)

Any clues? (Thinkpad iSeries... 1200, I think.)

What kernel version? Can you test with latest?

So the key repeat problem is still happening with -test5-mm4. I just had the return key stick on me, and gave it a good three seconds to stop repeating
before I hit another key. It didn't. I noticed after it stuck that the
next time I hit it, it didn't register. (I unstuck it with the up-arrow key, I believe. But after that one failure to press, it seemed to be nicely reset...)

Here's a cut and paste from a tail of /var/log/messages:

Sep 22 12:50:38 localhost  -- landley[984]: LOGIN ON tty1 BY landley
Sep 22 13:24:05 localhost kernel: spurious 8259A interrupt: IRQ7.
Sep 22 14:12:26 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x94, 
on isa0060/serio0) pressed.
Sep 22 14:12:26 localhost kernel: i8042 history: 18 98 18 98 26 a6 39 b9 1f 9f 
15 1f 95 9f 12 94
Sep 22 14:22:05 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xa6, 
on isa0060/serio0) pressed.
Sep 22 14:22:05 localhost kernel: i8042 history: 94 15 95 39 14 b9 18 94 98 39 
b9 23 12 a3 92 a6
Sep 22 14:39:06 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1cb, 
on isa0060/serio0) pressed.
Sep 22 14:39:06 localhost kernel: i8042 history: cb e0 4b e0 cb e0 4b e0 cb e0 
4b e0 cb 4b e0 cb
Sep 22 14:58:05 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Sep 22 14:58:05 localhost kernel: i8042 history: 1c 90 9c e0 48 e0 c8 23 0f a3 
8f 1c 9c 50 e0 d0
Sep 22 14:59:46 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xb1, 
on isa0060/serio0) pressed.
Sep 22 14:59:46 localhost kernel: i8042 history: 2d ad 2d ad 17 97 19 99 1e 15 
9e 95 17 97 22 b1
Sep 22 15:02:11 localhost su(pam_unix)[1649]: session opened for user root by 

landley(uid=500)

Any clues? (This happens to me at least once an hour...)

Rob

#6 lore raw
Quoted 6 lines · Rob Landley

Here's a cut and paste from a tail of /var/log/messages:

Sep 22 14:12:26 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x94, 
on isa0060/serio0) pressed.
Sep 22 14:12:26 localhost kernel: i8042 history: 18 98 18 98 26 a6 39 b9 1f 9f 

15 1f 95 9f 12 94

ool sys e <t release>

Quoted 4 lines
Sep 22 14:22:05 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xa6, 
on isa0060/serio0) pressed.
Sep 22 14:22:05 localhost kernel: i8042 history: 94 15 95 39 14 b9 18 94 98 39 

b9 23 12 a3 92 a6

y to he <l release>

Quoted 6 lines

From "try to help"? The l press was lost.

Sep 22 14:39:06 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1cb, 
on isa0060/serio0) pressed.
Sep 22 14:39:06 localhost kernel: i8042 history: cb e0 4b e0 cb e0 4b e0 cb e0 

4b e0 cb 4b e0 cb

[Left] [Left] [Left] KP-4 <[Left] release>

This is a rather clear one. You press the grey [Left] key four times. It has make code e0 4b and break code e0 cb.
Three times we get e0 4b e0 cb but once we get 4b e0 cb. Surely, the e0 was lost here.

Quoted 4 lines
Sep 22 14:58:05 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0x1d0, 
on isa0060/serio0) pressed.
Sep 22 14:58:05 localhost kernel: i8042 history: 1c 90 9c e0 48 e0 c8 23 0f a3 

8f 1c 9c 50 e0 d0

[Enter] [Up] h [Tab] [Enter] KP-2 <[Down] release>

Rather similar. The e0 part of e0 50 was lost.

Quoted 4 lines
Sep 22 14:59:46 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xb1, 
on isa0060/serio0) pressed.
Sep 22 14:59:46 localhost kernel: i8042 history: 2d ad 2d ad 17 97 19 99 1e 15 

9e 95 17 97 22 b1

xxipayig <n release>

You were typing "paying" but the n press was not seen.

Quoted 1 line

Any clues? (This happens to me at least once an hour...)

Some people have been reporting missing key releases (maybe also you), but these are all missing key presses. It is easiest to blame the keyboard, even though I could imagine ways to blame the kernel.

What about 2.4? Do you have to go back once an hour and add a symbol that was not transmitted correctly? Does 2.4 work perfectly for you?

#7 lore raw
Quoted 10 lines · Andries Brouwer
Quoted 1 line · Rob Landley

Any clues? (This happens to me at least once an hour...)

Some people have been reporting missing key releases (maybe also you), but these are all missing key presses. It is easiest to blame the keyboard, even though I could imagine ways to blame the kernel.

What about 2.4? Do you have to go back once an hour and add a symbol that was not transmitted correctly? Does 2.4 work perfectly for you?

2.4 worked for me when I used it. I haven't booted 2.4 in weeks, but I don't remember losing any keypresses under 2.4. (I suppose I could fire up a 2.4 kernel and answer email with it for a couple hours, though...)

Rob

#8 lore raw
Quoted 5 lines · Rob Landley
Quoted 4 lines · Andries Brouwer
Quoted 1 line · Rob Landley

Any clues? (This happens to me at least once an hour...)

Quoted 7 lines
Quoted 5 lines

Some people have been reporting missing key releases (maybe also you), but these are all missing key presses. It is easiest to blame the keyboard, even though I could imagine ways to blame the kernel.

What about 2.4?

2.4 worked for me when I used it. I haven't booted 2.4 in weeks

I've been missing keypresses for at least six weeks; at first I too thought the keyboard was the culprit, but I've anecdotal grumblings in email from several 2.4 users who thought the same of their own machines. Not very likely to be a keyboard-infesting virus out there... Frequency seems to be of the order of 0.001 on average.

It might not be only keyboard interrupts that are being missed, but I have no hard data -- just a gut feeling that occasional ethernet packets are going astray too for no known good reason. Hasn't been enough of a problem to trigger serious investigation.

Signature · 3 lines
| G r e g  L o u i s         | gpg public key: 0x400B1AA86D9E3E64 |
|  http://www.bgl.nu/~glouis |   (on my website or any keyserver) |
|  http://wecanstopspam.org in signatures helps fight junk email. |
#9 lore raw
In reply to Andries Brouwer
Quoted 5 lines · Andries Brouwer
Quoted 1 line

Any clues? (This happens to me at least once an hour...)

Some people have been reporting missing key releases (maybe also you), but these are all missing key presses. It is easiest to blame the keyboard, even though I could imagine ways to blame the kernel.

If the press is the first event, how does it know that it's missing? Are you saying t got a key release that didn't match an active keypress? This seems like a similar problem. Are missing key releases flagged as errors and logged? (Maybe the next time that key is pressed, if the system thinks it's already down?)

I'm certainly seeing missing releases. Missing presses are just typos, I usually have enough gunk in the keyboard that it misses the occasional key anyway. (This laptop lives in my backpack, with books and papers and Wendy's coupons and pens and...) But "enter", "delete", or "cursor up" holding down for an extra second and change can be quite annoying.

Quoted 2 lines

What about 2.4? Do you have to go back once an hour and add a symbol that was not transmitted correctly? Does 2.4 work perfectly for you?

Okay, over the past few days I've booted into 2.4.21 three times and done my standard text-intensive programming, email, and word processing. I didn't notice any keys sticking. (It's intermittent enough problem that this isn't difinitive, but it's the best I can do.)

On the other hand, the key repeat rate is a lot slower under 2.4.21, and I suspect it's using the hardware repeat instead of the software repeat. The keyboard hardware definitely knows when a key gets released. :)

I.E. Under 2.4.21 I don't experience a problem. (Maybe there is a technical problem with the hardware, but it doesn't manifest in a way that I ever notice.) I'd be happy to live with the slower repeat rate if I could get 2.6 to use 2.4's keyboard access method.

Rob

#10 lore raw
In reply to Andries Brouwer
Quoted 6 lines · Andries Brouwer
Quoted 1 line

Any clues? (This happens to me at least once an hour...)

Some people have been reporting missing key releases (maybe also you), but these are all missing key presses. It is easiest to blame the keyboard, even though I could imagine ways to blame the kernel.

Quoted 8 lines

What about 2.4? Do you have to go back once an hour and add a symbol that was not transmitted correctly? Does 2.4 work perfectly for you?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Okay, a little fresh data:

I just had the keyboard key sticking problem occur, 2.6.0-test5-mm4.

Sep 25 20:06:25 localhost dhclient: DHCPREQUEST on eth0 to 128.83.185.55 port 
67
Sep 25 20:06:25 localhost dhclient: DHCPACK from 128.83.185.55
Sep 25 20:06:25 localhost dhclient: bound to 128.62.240.239 -- renewal in 1608 
seconds.
Sep 25 20:22:22 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd1, 
on isa0060/serio0) pressed.
Sep 25 20:22:22 localhost kernel: i8042 history: d1 e0 51 e0 d1 e0 51 e0 d1 e0 
51 e0 d1 e0 51 d1
Sep 25 20:22:42 localhost su(pam_unix)[2047]: session opened for user root by 

landley(uid=500)

The page down key is the one that stuck. I pressed another key (possibly either cursor up or page up) to unstick it, and then the next time I pressed page down it didn't register, but the time after that it did.

Checking the log, I saw the above message. This is the first time since the last reboot the problem has occurred, and the first such message since the last reboot. The message IS occurring when I have the key sticking problem, as shown by the timestamps.

You're talking about missed keypresses, but the end-user symptom I'm seeing is definitely a missed key release, and it's associated with the above log message.

Rob

#11 lore raw
Quoted 6 lines · Rob Landley

Okay, a little fresh data:

Sep 25 20:22:22 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd1, 
on isa0060/serio0) pressed.
Sep 25 20:22:22 localhost kernel: i8042 history: d1 e0 51 e0 d1 e0 51 e0 d1 e0 

51 e0 d1 e0 51 d1

e0 51 is PageDown press
e0 d1 is PageDown release

You see here (apart from the first byte, which probably is the second half of a PageDown release): PageDown press, release, press, release, press, release, press, broken release.

A byte e0 was lost, and the release was not seen as a PageDown release.

Quoted 6 lines

The page down key is the one that stuck. I pressed another key (possibly either cursor up or page up) to unstick it, and then the next time I pressed page down it didn't register, but the time after that it did.

You're talking about missed keypresses, but the end-user symptom I'm seeing is definitely a missed key release

Yes - here a release was garbled.

Many people have reported missing key releases, and, as a consequence of that, stuck keys. Your reports feel a bit different: the e0 is sometimes lost from a key press, sometimes from a key release.

#12 lore raw
Quoted 21 lines · Andries Brouwer
Quoted 6 lines · Rob Landley

Okay, a little fresh data:

Sep 25 20:22:22 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd1, 
on isa0060/serio0) pressed.
Sep 25 20:22:22 localhost kernel: i8042 history: d1 e0 51 e0 d1 e0 51 e0 d1 e0 

51 e0 d1 e0 51 d1

e0 51 is PageDown press
e0 d1 is PageDown release

You see here (apart from the first byte, which probably is the second half of a PageDown release): PageDown press, release, press, release, press, release, press, broken release.

A byte e0 was lost, and the release was not seen as a PageDown release.

Quoted 3 lines

The page down key is the one that stuck. I pressed another key (possibly either cursor up or page up) to unstick it, and then the next time I pressed page down it didn't register, but the time after that it did.

Quoted 8 lines
Quoted 2 lines

You're talking about missed keypresses, but the end-user symptom I'm seeing is definitely a missed key release

Yes - here a release was garbled.

Many people have reported missing key releases, and, as a consequence of that, stuck keys. Your reports feel a bit different: the e0 is sometimes lost from a key press, sometimes from a key release.

I'm wondering if it could be a bug in the i8042.c driver ...

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#13 lore raw
In reply to Andries Brouwer
Quoted 8 lines · Andries Brouwer
Quoted 2 lines

You're talking about missed keypresses, but the end-user symptom I'm seeing is definitely a missed key release

Yes - here a release was garbled.

Many people have reported missing key releases, and, as a consequence of that, stuck keys. Your reports feel a bit different: the e0 is sometimes lost from a key press, sometimes from a key release.

I don't know what to tell you. When I compiled 2.4 (no detectable problems), I wasn't using the input (and in fact had it disabled). Not necessarily a useful piece of information. The symptom that I notice is software autorepeat going bananas when the hardware at least knows the key has been released and would not be sending hardware autorepeat events...

Rob