Most recent kernel where this bug did not occur: Distribution: Hardware Environment: Acer Aspire 1501LMi (AMD Athlon64 3000+) 00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:0a.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) 00:0b.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa) 00:0b.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa) 00:0b.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 02) 00:0c.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet (rev 03) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] Software Environment: Problem Description: When typing on the notebook's keyboard, it happens from time to time (quite often, though) that when you press a key and release it (ordinary typing), that it behaves as if you wouldn't release it at all. You then have to press (and release, possibly) any key again, in order to stop the autorepeat of the failed keypress. It is quite annoying to type something when getting unexpected autorepeats once every while. I first thought, that it may only be some dust and dirt in the keyboard, but it doesn't seem behave like that in the Windows (so far ;) and then I (a good example of the consequences :) also noticed that when it happens, lots of following messages appear in the syslog: ------------------------- [10182.413396] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [10182.413401] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [10271.568304] atkbd.c: Unknown key pressed (translated set 2, code 0xc2 on isa0060/serio0). [10271.568310] atkbd.c: Use 'setkeycodes e042 <keycode>' to make it known. [10324.407131] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [10324.407136] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [10463.350818] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [10463.350824] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [10496.648735] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [10496.648741] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [10498.659067] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [10498.659072] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [11018.214526] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [11018.214531] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [11513.550225] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [11513.550231] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [11727.526931] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [11727.526936] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. [11761.571773] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). [11761.571778] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. -------------------- Currently I use kernel 2.6.17-rc5-git9, before I was using 2.6.16-git9 and it happend there as well. I may try some (another good example, but it is not allways just the space, that's just a coincidence) older kernels to see where it begins. Steps to reproduce: Just type on the keyboard on that notebook and kernel. :) I haven't witnessed it on any other hardware, so far.
Martin, have you made any progress investigating your keyboard? You can possibly look into setkeycodes command, it is supposed to help "unusual keyboards".
Indeed, there was a progress. I'm not sure at which point (kernel) exactly it began, but with current kernels the behavior disappeared and all seems to work correctly. Definitely at least 2.6.21+ seem to work. But as I say, I'm not sure at which point exactly it was fixed.
OK, great. I guess we close the bug. You can reopen it if the problem reappears. Thanks.