Keyboard goes unresponsive for some reason

gorokuz · 2023-06-07 17:46:21

I can confirm that this problem still happens on my ThinkPad L14 AMD Gen 1 with firmware 1.29. It has happened extremely often since I started playing videogames in my laptop (multiple key presses at the same time?), but the last one I was just Ctrl+scrolling on a website to zoom out and the Ctrl became softwarestuck. Extremely annoying... If anyone has newer ideas on this issue, please let us know.

├─System Firmware:
│ │ Summary: UEFI ESRT device
│ │ Current version: 0.1.29
│ │ Minimum Version: 0.0.1
│ │ Vendor: Lenovo (DMI:LENOVO)
│ │ Update State: Success

espritlibre · 2023-06-08 15:16:45

i had the same issue 3 times so very rarely, in my case it was always the A key that didn't get released. the only key that works is the power button, which suspends the laptop and after resuming the keyboard functions properly again. i have a ThinkPad P14s Gen3 with the latest 0.1.34 fw. i have a journal saved from the last time this happened. if someone wanna look into i can share it.

seth · 2023-06-08 19:01:41

See whether this also happens w/ a different SW stack (windows, live distro eg. grml) - this might be a "why you should not drink sugary stuff next to your keyboard" situation (or the specific keyboard model might be prone to that) …

anthony93 · 2023-08-10 08:12:25

This just happened to me today (also Thinkpad P14s Gen 3) on 6.1.44-1-lts. I was just scrolling through my journal entries with the 'j' key and suddenly the page just wouldn't stop scrolling even though the 'j' key was released. I can still move my cursor with the touchpad, but the trackpoint stopped working. Activating my browser window with the mouse caused the letter 'j' to be spammed on the address bar, so we can assume that the key press event was being registered even though the key was released. I had to press the power button to reboot.

This occured a few times in the past when I was using the stable kernel (6.4.2-arch). Different keys were affected back then. One time it was the 'a' key, and another time the 'n' key (it was always the last key pressed at the point the problem occured that's affected). The problem disappeared on its own after a few kernel updates past 6.4.2arch. I never noticed it anymore until I recently switched back to the lts kernel.

These are the journal entries around the time the problem occured on 6.1.44-1-lts:

Aug 10 14:51:37 P14s systemd[1]: Unmounted EFI System Partition Automount.
Aug 10 15:03:53 P14s systemd[1]: Starting Cleanup of Temporary Directories...
Aug 10 15:03:53 P14s systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Aug 10 15:03:53 P14s systemd[1]: Finished Cleanup of Temporary Directories.
Aug 10 15:39:03 P14s systemd-logind[533]: Power key pressed short.
Aug 10 15:39:03 P14s systemd-logind[533]: Powering off...
Aug 10 15:39:03 P14s systemd-logind[533]: System is powering down.

As you can see, I pressed the power key at 15:39. The problem occurred just a minute before that.

ei · 2023-10-10 20:21:10

Issue still occurs on my T14 Gen 3 after upgrading to firmware version 1.28. Interestingly, it seems to have been *caused* by the firmware upgrade, since I had previously upgraded the firmware, magically noticed the glitch was gone, happened to upgrade it again recently, and suddenly noticed the issue is back.

There are a few possibilities here.

1) The firmware devs fixed the issue, then accidentally reintroduced it again.

2) The method I used to install the firmware matters. When I made a bootable disk, the glitch was fixed. When I used fwupd, the glitch was reintroduced.

3) Due to the random nature of this glitch, I just happened to get really lucky for several months, then suddenly get very unlucky over the course of a few weeks

Last edited by ei (2023-10-10 20:22:25)

tomblue01 · 2024-01-03 18:17:22

I have two brand new ThinkPad L14 Gen 3 AMD - bought for two of my kids for Christmas. Both running Win11 and both fully patched and BIOS updated (via Lenovo's update utility). Both keyboards go unresponsive randomly. Not fixed yet. Waiting for Lenovo to take some responsibility here and fix this.

iavr · 2024-12-11 05:18:13

When this first happened to me, I originally thought it was a VM thing, hence I opened https://bbs.archlinux.org/viewtopic.php?id=297375, but it happened to me for the first time outside of a VM yesterday.

What I can say about it is:

* It's very rare (and thus hard to troubleshoot). It's happened to me about 4-5 times in a full year of regular use.
* I've got a ThinkPad also; comparing notes to what everyone else is saying, this looks like it's exclusively a Lenovo problem.
* I'm using the latest firmware.
* Putting the computer to sleep and waking it back up makes the problem go away.

LookBackImThere · 2025-05-21 14:02:34

I have a Thinkpad L14 Gen 2 (this is different from the consumer line, as this is corporate model. For example, this doesn't have a touch screen like other L14 consumer models.), and I am facing the same issue. Although this happens rarely, it is annoying. I am using Sway btw, so this is not an Xorg issue, and since this is an years long issue faced by Thinkpads only, its not a problem by kernel version, or any OS software, but Lenovo side issue, probably BIOS

I have noticed this happens when I am typing quickly/multiple key press.
It's clear that Lenovo needs to fix this issue.

Last edited by LookBackImThere (2025-05-21 14:17:53)

Mikicrep · 2025-08-27 06:42:02

i got same issue, uefi version 1.71, happens everyday i use laptop, maybe caused by fast key presses and multiple key presses (mostly happens in osu!), i found temponary fix: ssh from phone and run script i made to replug all usb devices if anyone needs it tell me, running latest linux kernel (6.16 or 6.17? idk), i got thinkpad l14 gen 2

if anyone found solution lmk, i will continue trying to find a way to fix it cuz its soo annoying and often

seth · 2025-08-27 07:28:38

happens everyday i use laptop

Does it leave any traces in the system journal/dmesg?

replug all usb devices

Toggling /sys/bus/usb/devices/*/authorized or using usbreset from https://archlinux.org/packages/core/x86_64/usbutils/ ?
Re-attaching only the keyboard doesn't suffice?

Mikicrep · 2025-08-27 17:59:58

> Does it leave any traces in the system journal/dmesg?

idk how to use journalctl

> Toggling /sys/bus/usb/devices/*/authorized or using usbreset from https://archlinux.org/packages/core/x86_64/usbutils/ ?
Re-attaching only the keyboard doesn't suffice?

theese are cmds i use to reattach them

sudo udevadm trigger -s input
echo -n "disable" | sudo tee /sys/bus/serio/devices/serio0/drvctl
echo -n "reconnect" | sudo tee /sys/bus/serio/devices/serio0/drvctl

if i reattach only keyboard then touchpad wont fix itself cuz touchpad stops working too, it can only click, also trackpoint works fine

seth · 2025-08-27 18:04:03

https://wiki.archlinux.org/title/System … ing_output - you're looking for "-b" or "-f" and in doubt want to sudo it.
If you paste stuff for review, please stay away from "-x" and "-r" as far as humanly possible, thanks

Mikicrep · 2025-08-27 18:06:40

okay, i will try to get and send u that when i start daily driving that laptop (in like a week), thanks for trying to help

Mikicrep · 2025-09-02 08:34:20

Hi, here are logs from 1 hour range, issue happened like 5 minutes ago (not sure)
https://pastebin.com/gy20aUJB

In meanwhile I also ran commands to reattach it (sent above)

seth · 2025-09-02 15:19:08

Sep 02 10:19:06 mikicrep-thinkpad sudo[21565]: mikicrep : TTY=pts/0 ; PWD=/home/mikicrep ; USER=root ; COMMAND=/usr/bin/pacman --sync -- arandr
Sep 02 10:22:32 mikicrep-thinkpad sudo[22262]: mikicrep : TTY=pts/0 ; PWD=/home/mikicrep ; USER=root ; COMMAND=/usr/bin/pacman --sync -- clang
Sep 02 10:23:07 mikicrep-thinkpad sudo[26647]: mikicrep : TTY=pts/0 ; PWD=/home/mikicrep ; USER=root ; COMMAND=/usr/bin/pacman --upgrade --noconfirm -- /home/mikicrep/.cache/paru/clone/clang-format-all-git/clang-format-all-git-r8.4d6ee56-1-any.pkg.tar.zst
Sep 02 10:23:07 mikicrep-thinkpad sudo[26654]: mikicrep : TTY=pts/0 ; PWD=/home/mikicrep ; USER=root ; COMMAND=/usr/bin/pacman --database --asexplicit -- clang-format-all-git

Sep 02 10:24:36 mikicrep-thinkpad sshd-session[27569]: pam_unix(sshd:session): session opened for user mikicrep(uid=1000) by mikicrep(uid=0)
Sep 02 10:24:48 mikicrep-thinkpad sudo[27631]: mikicrep : TTY=pts/2 ; PWD=/home/mikicrep ; USER=root ; COMMAND=/usr/bin/udevadm trigger -s input
Sep 02 10:24:48 mikicrep-thinkpad sudo[27631]: pam_unix(sudo:session): session opened for user root(uid=0) by mikicrep(uid=1000)
Sep 02 10:24:48 mikicrep-thinkpad sudo[27631]: pam_unix(sudo:session): session closed for user root
Sep 02 10:24:48 mikicrep-thinkpad sudo[27638]: mikicrep : TTY=pts/2 ; PWD=/home/mikicrep ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/serio/devices/serio0/drvctl
Sep 02 10:24:48 mikicrep-thinkpad sudo[27638]: pam_unix(sudo:session): session opened for user root(uid=0) by mikicrep(uid=1000)
Sep 02 10:24:48 mikicrep-thinkpad sudo[27638]: pam_unix(sudo:session): session closed for user root
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event0 (Sleep Button)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event6 (YICHIP Wireless Device)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event2 (Power Button)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event1 (Lid Switch)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event8 (YICHIP Wireless Device System Control)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event10 (Intel HID events)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event9 (YICHIP Wireless Device Consumer Control)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event3 (AT Translated Set 2 keyboard)
Sep 02 10:24:48 mikicrep-thinkpad systemd-logind[862]: Watching system buttons on /dev/input/event4 (ThinkPad Extra Buttons)
Sep 02 10:24:48 mikicrep-thinkpad sudo[27669]: mikicrep : TTY=pts/2 ; PWD=/home/mikicrep ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/serio/devices/serio0/drvctl

Smells like https://bugs.archlinux.org/task/77789

sudo touch /etc/systemd/do-not-udevadm-trigger-on-update

Mikicrep · 2025-09-02 15:22:27

Yes it does reset keyboard layout, thats why i got another script to bring back keyboard, and also that pacman message is cuz i installed some package (not update anything)

Bug happens no matter did I use pacman or i did not

Update doesnt kill keyboard

Last edited by Mikicrep (2025-09-02 15:22:54)

seth · 2025-09-02 15:28:19

You wrote:

that pacman message is cuz i installed some package (not update anything)

But paru wrote:

Sep 02 10:22:32 COMMAND=/usr/bin/pacman --sync -- clang
Sep 02 10:23:07 COMMAND=/usr/bin/pacman --upgrade --noconfirm

This is why it's generally not a good idea to use pacman wrappers if you don't know how to use pacman, but in this case paru ran an upgrade when you were trying to install clang.
1 minute later you ssh'd into the system to fix the keyboard.

Those problems will only occur for some update (notably everytime systemd gets updated, check /var/log/pacman.log for what actually happened)

Add that file, see whether the problem occurs afterwards.

Mikicrep · 2025-09-02 17:43:43

Heres pacman.log?

https://pastebin.com/bf7RZvYi

seth · 2025-09-02 19:27:10

Not unless 30-systemd-update.hook doesn't run the wrong script.
But there's nothing else in the journal.

When this happens the keyboard is dead-dead?
You cannot cltr+alt+f3, you cannot even https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ?

Mikicrep · 2025-09-02 20:11:38

ye cant even go to tty, and also how do i do sysrq without actual button (its laptop, not pc keyboard)

seth · 2025-09-02 20:32:03

sysrq is the print key, there's not a very strong chance for it to work if the TTY switch doesn't work.

Since ist's usb, maybe it doesn't respond well to https://wiki.archlinux.org/title/Power_ … utosuspend ?

Mikicrep · 2025-09-03 07:15:50

I tried to find keyboard, but I couldnt, it doesnt show in lsusb

[9:10][mikicrep@mikicrep-thinkpad] | /home/mikicrep% lsusb --tree
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 004: Dev 003, If 0, Class=Vendor Specific Class, Driver=[none], 12M
    |__ Port 005: Dev 004, If 0, Class=Chip/SmartCard, Driver=[none], 12M
    |__ Port 007: Dev 005, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 007: Dev 005, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 009: Dev 008, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 009: Dev 008, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 010: Dev 007, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 010: Dev 007, If 1, Class=Wireless, Driver=btusb, 12M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M

It does show in xinput as some AT keyboard (id 14, idk is it laptop keyboard)

[9:11][mikicrep@mikicrep-thinkpad] | /home/mikicrep% xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=15	[slave  pointer  (2)]
⎜   ↳ TPPS/2 Elan TrackPoint                  	id=18	[slave  pointer  (2)]
⎜   ↳ YICHIP Wireless Device Mouse            	id=10	[slave  pointer  (2)]
⎜   ↳ YICHIP Wireless Device Consumer Control 	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Intel HID events                        	id=13	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=14	[slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                  	id=16	[slave  keyboard (3)]
    ↳ YICHIP Wireless Device                  	id=9	[slave  keyboard (3)]
    ↳ YICHIP Wireless Device Consumer Control 	id=12	[slave  keyboard (3)]
    ↳ YICHIP Wireless Device System Control   	id=17	[slave  keyboard (3)]

seth · 2025-09-03 09:06:38

Sorry, my brain bled another thread into this.
See whether "i8042.debug=1" gets you additional output.

There several mitigating options in

modinfo atkbd i8042

but w/o trigger pattern it will be hard to guess and test one

Mikicrep · 2025-09-03 19:58:12

I didnt yet boot with that boot flag, just to prove that pacman does not cause it here is another keyboard death that happened just now while i was playing roblox it happened randomly, maybe u can find smth useful idk

http://pastebin.com/nLgtnpaX

seth · 2025-09-03 20:19:56

The only thing logged for minutes before the ssh login is tailscaled, which isn't overly likely to cause your keyboard to stop working on a kernel level.

Arch Linux

#26 2023-06-07 17:46:21

Re: Keyboard goes unresponsive for some reason

#27 2023-06-08 15:16:45

Re: Keyboard goes unresponsive for some reason

#28 2023-06-08 19:01:41

Re: Keyboard goes unresponsive for some reason

#29 2023-08-10 08:12:25

Re: Keyboard goes unresponsive for some reason

#30 2023-10-10 20:21:10

Re: Keyboard goes unresponsive for some reason

#31 2024-01-03 18:17:22

Re: Keyboard goes unresponsive for some reason

#32 2024-12-11 05:18:13

Re: Keyboard goes unresponsive for some reason

#33 2025-05-21 14:02:34

Re: Keyboard goes unresponsive for some reason

#34 2025-08-27 06:42:02

Re: Keyboard goes unresponsive for some reason

#35 2025-08-27 07:28:38

Re: Keyboard goes unresponsive for some reason

#36 2025-08-27 17:59:58

Re: Keyboard goes unresponsive for some reason

#37 2025-08-27 18:04:03

Re: Keyboard goes unresponsive for some reason

#38 2025-08-27 18:06:40

Re: Keyboard goes unresponsive for some reason

#39 2025-09-02 08:34:20

Re: Keyboard goes unresponsive for some reason

#40 2025-09-02 15:19:08

Re: Keyboard goes unresponsive for some reason

#41 2025-09-02 15:22:27

Re: Keyboard goes unresponsive for some reason

#42 2025-09-02 15:28:19

Re: Keyboard goes unresponsive for some reason

#43 2025-09-02 17:43:43

Re: Keyboard goes unresponsive for some reason

#44 2025-09-02 19:27:10

Re: Keyboard goes unresponsive for some reason

#45 2025-09-02 20:11:38

Re: Keyboard goes unresponsive for some reason

#46 2025-09-02 20:32:03

Re: Keyboard goes unresponsive for some reason

#47 2025-09-03 07:15:50

Re: Keyboard goes unresponsive for some reason

#48 2025-09-03 09:06:38

Re: Keyboard goes unresponsive for some reason

#49 2025-09-03 19:58:12

Re: Keyboard goes unresponsive for some reason

#50 2025-09-03 20:19:56

Re: Keyboard goes unresponsive for some reason

Board footer