http://bugzilla.kernel.org/show_bug.cgi?id=9147
------- Comment #137 from da...@start.no 2009-01-19 19:05 ------- The bug is in fact from as far back as 2003: http://lkml.org/lkml/2003/9/15/210 The user begins by complaining about the familiar errors: Sep 14 20:42:27 cpp kernel: atkbd.c: Unknown key (set 2, scancode 0xb6, on isa0060/serio0) pressed. Sep 14 20:42:27 cpp kernel: i8042 history: 19 a2 99 0f 8f 0f 8f 1c 9c 04 84 36 09 b6 89 b6 Sep 14 22:13:00 cpp kernel: atkbd.c: Unknown key (set 2, scancode 0xa5, on isa0060/serio0) pressed. Sep 14 22:13:00 cpp kernel: i8042 history: a7 20 9e 21 9f 24 25 26 27 a0 a4 a5 a6 a7 a1 a5 Sep 14 22:13:00 cpp kernel: atkbd.c: Unknown key (set 2, scancode 0xa6, on isa0060/serio0) pressed. Sep 14 22:13:00 cpp kernel: i8042 history: 20 9e 21 9f 24 25 26 27 a0 a4 a5 a6 a7 a1 a5 a6 Sep 14 22:13:00 cpp kernel: atkbd.c: Unknown key (set 2, scancode 0xa7, on isa0060/serio0) pressed. Sep 14 22:13:00 cpp kernel: i8042 history: 9e 21 9f 24 25 26 27 a0 a4 a5 a6 a7 a1 a5 a6 a7 An Andries Brouwer then replies: Enter your search termsSubmit search formWeblkml.org Date Mon, 15 Sep 2003 23:28:00 +0200 >From Andries Brouwer <> Subject Re: 2.6.0-test1, -test4 control key "stuck" On Mon, Sep 15, 2003 at 08:55:46PM +0000, xsdg wrote: > What would happen if the kernel received two keypress events, and then one > key- > release event for a single key? I'd imagine that it'd disregard the duplicate > keypress The answers differ for 2.4 and 2.6. For 2.4 each keypress is a keypress, and key releases are rather unimportant as long as the key is not a modifier key. For 2.6 we have synthetic repeat, so a second keypress from the keyboard is ignored, the key repeats with kernel-defined frequency, and the repeat is ended by the key release. > any idea what might cause the key sticking problem? If a key release is not seen, 2.4 doesnt mind, but 2.6 keeps repeating. > Also, I'm not sure how the final issue I described Do not recall all items of all letters I answer - sorry. Andries In other words, the bug may be caused by a combination of faulty hardware and some very naive code in the keyboard driver that was added in kernel 2.6. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
