Distribution: gentoo with 2.6.9-r1 (but exactly the same problems appear with the 2.6.9 vanilla sources and the 2.6.10-rc1 sources). Hardware Environment: Fujitsu Siemens Lifebook s-4542 Software Environment: happens in the hell as well as under x (xorg-6.8) Problem Description: Since Kernel gentoo-dev-source-2.6.9-r1 (happens also with vanilla 2.6.9 and 2.6.10-rc1 but works perfectly with <2.6.9), my keyboard does not work anymore after resuming from suspend. Some keys echo double output of another key, some keys don't echo anything at all. All I can to is a hard reset. When pressing a key, I get the following output in /var/log/messages: Oct 25 06:37:02 pingu atkbd.c: Unknown key pressed (translated set 2, code 0x66 on isa0060/serio0). Oct 25 06:37:02 pingu atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known. Oct 25 06:37:02 pingu atkbd.c: Unknown key pressed (translated set 2, code 0x66 on isa0060/serio0). Oct 25 06:37:02 pingu atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known. Oct 25 06:37:02 pingu atkbd.c: Unknown key pressed (translated set 2, code 0x66 on isa0060/serio0). Oct 25 06:37:02 pingu atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known. Oct 25 06:37:02 pingu atkbd.c: Unknown key pressed (translated set 2, code 0x66 on isa0060/serio0). Oct 25 06:37:02 pingu atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known. Oct 25 06:37:02 pingu atkbd.c: Unknown key pressed (translated set 2, code 0x66 on isa0060/serio0). Oct 25 06:37:02 pingu atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known. cat /proc/interrupts says: CPU0 0: 461930 XT-PIC timer 1: 1175 XT-PIC i8042 2: 0 XT-PIC cascade 9: 7781 XT-PIC Intel 440MX, yenta, yenta, eth0 12: 11684 XT-PIC i8042 14: 8525 XT-PIC ide0 15: 0 XT-PIC uhci_hcd NMI: 0 LOC: 0 ERR: 0 MIS: 0 And just after the resume before pressing any key, /var/log/messages tells me: Oct 30 17:31:45 pingu PCI: Found IRQ 9 for device 0000:00:00.1 Oct 30 17:31:45 pingu PCI: Sharing IRQ 9 with 0000:00:13.1 Oct 30 17:31:45 pingu PCI: Setting latency timer of device 0000:00:00.1 to 64 Steps to reproduce: reboot, create some input either with the keyboard or the mouse, put to standy, resume. that's it!
Created attachment 3972 [details] current kernel config (sorry, wrong one)
Created attachment 3973 [details] current kernel config
similar error here ... with any kernel >= 2.6.9 (2.6.9-r6 gentoo and 2.6.10-r2 vanilla sources): atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0). atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known. the bug occures only with a ps2-keyboard no errors detected with an usb-keyboard 2.6.8 works perfectly
Just tried again with a minimal kernel config with gentoo-dev-sources-2.6.9-r9 and still have the same error. I'll attach the minimal .config file. Anyone can tell me how to nail it down? Unfortunately I don't have an USB keyboard to test what Richard wrote. Marco
Created attachment 4234 [details] minimal kernel .config minimal configuration with IDE and network and filesystem support.
Same is true for HP omnibook 6000, PIII/1000, sometimes under no load, often under heavy load; Ctrl/Shift/Meta/autorepeat-State is switched every now and then, characters are often dropped, mouse sometimes jumps. Very difficult to provide correct passwords ;-( Disabling acpi in kernel config solves this for 2.6.10-rc3
Correction to previous comment: after some time it started again to make problems, still better than with acpi, but not at all error free. So, sorry for the misinformation.
Same for Samsung X30 -> atkbd.c: Unknown key pressed (translated set 2, code 0x74 on isa0060/serio0). atkbd.c: Use 'setkeycodes 74 <keycode>' to make it known. atkbd.c: Unknown key released (translated set 2, code 0x74 on isa0060/serio0). atkbd.c: Use 'setkeycodes 74 <keycode>' to make it known. atkbd.c: Unknown key pressed (translated set 2, code 0x75 on isa0060/serio0). atkbd.c: Use 'setkeycodes 75 <keycode>' to make it known. atkbd.c: Unknown key released (translated set 2, code 0x75 on isa0060/serio0). atkbd.c: Use 'setkeycodes 75 <keycode>' to make it known.
still exists with gentoo-dev-sources-2.6.10-r4
I guess the patch haven't reached the official kernel ever (in these 1.5 months)? See this thread: < http://seclists.org/lists/linux-kernel/2005/Jan/1138.html > And the patch in the thread: < http://seclists.org/lists/linux-kernel/2005/Jan/1331.html > by Dmitry ===== drivers/input/serio/libps2.c 1.2 vs edited ===== --- 1.2/drivers/input/serio/libps2.c 2004-10-20 03:13:08 -05:00 +++ edited/drivers/input/serio/libps2.c 2005-01-06 01:20:11 -05:00 @@ -250,7 +250,7 @@ } /* Fall through */ default: - return 1; + return 0; } if (!ps2dev->nak && ps2dev->cmdcnt) -
That particular patch (well, better version of it) is in the kernel proper.
Seems this patch also solved the problem with apmd resume on my notebook. thanks a lot!
Seems I was too fast with my conclusion. The patch reduces the failures when resuming the laptop but it did not disappear yet. I still get those lines from time to time (always after standby/resume): Mar 30 10:01:55 pingu atkbd.c: Unknown key pressed (translated set 2, code 0x66 on isa0060/serio0). Mar 30 10:01:55 pingu atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known. Mar 30 10:01:55 pingu atkbd.c: Unknown key pressed (translated set 2, code 0x66 on isa0060/serio0). Mar 30 10:01:55 pingu atkbd.c: Use 'setkeycodes 66 <keycode>' to make it known.
But the keyboard works well? Those are just "warnings", aren't they?
Any update on this problem? Thanks.
Since no updates/complaints for long time - closing the bug.