Arch Linux

heyrict

Member

Registered: 2020-05-07

Posts: 6

[Solved] Specific key fails to respond after suspend

I recently got an Asus M3400QA laptop and found that, though other keys worked perfectly, one specific key (dot) gave no keystroke after suspend. Interestingly, evtest showed the scancode properly, though no keycode was given after suspend. System/device information are as follows:

❯  uname -srv
Linux 5.13.10-arch1-1 #1 SMP PREEMPT Thu, 12 Aug 2021 21:59:14 +0000

❯ evtest /dev/input/event2
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab83
Input device name: "AT Translated Set 2 keyboard"

Dmesg outputs:

❯ sudo dmesg | rg '(i8042|atkbd|PM: suspend)'
[    0.763825] i8042: PNP: PS/2 Controller [PNP030b:PS2K] at 0x60,0x64 irq 1
[    0.763829] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    0.764712] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.782879] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[    1.880722]  crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 i8042 xhci_pci crc32c_intel xhci_pci_renesas serio
[   30.234228] PM: suspend entry (s2idle)
[   33.977060] PM: suspend exit
[   34.162216] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input14
[   34.162965] atkbd_interrupt: 13 callbacks suppressed
[   34.162979] atkbd serio0: Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly.

Output of `dot` keystroke in evtest:

Before suspend:

Event: time 1629444950.516886, -------------- SYN_REPORT ------------
Event: time 1629444950.667312, type 4 (EV_MSC), code 4 (MSC_SCAN), value 34
Event: time 1629444950.667312, type 1 (EV_KEY), code 52 (KEY_DOT), value 1
Event: time 1629444950.667312, -------------- SYN_REPORT ------------
.Event: time 1629444950.751906, type 4 (EV_MSC), code 4 (MSC_SCAN), value 34
Event: time 1629444950.751906, type 1 (EV_KEY), code 52 (KEY_DOT), value 0
Event: time 1629444950.751906, -------------- SYN_REPORT ------------

After: (shown after releasing the key)

Event: time 1629444975.869721, -------------- SYN_REPORT ------------
Event: time 1629444976.079647, type 4 (EV_MSC), code 4 (MSC_SCAN), value 34
Event: time 1629444976.079647, -------------- SYN_REPORT ------------

Remapping scancode 34 to keycode did not work though.

Do you have any ideas which part was causing this specific behavior, the kernel, the `i8042` `atkbd` kernel modules or other layers?

Regards

Last edited by heyrict (2021-10-03 12:30:15)

heyrict

Member

Registered: 2020-05-07

Posts: 6

Re: [Solved] Specific key fails to respond after suspend

This issue is solved in latest kernel update (5.14.8)