Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #80026 > unrolled thread

Bug#1043558: keyboard doesn't respond after waking up

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1043558: keyboard doesn't respond after waking up Alma Madeleine <AlMa1@ro.ru> - 2023-08-13 00:10 +0200
    Processed: keyboard doesn't respond after waking up "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-13 00:10 +0200
    Bug#1043558: (no subject) Alma Madeleine <AlMa1@ro.ru> - 2023-08-13 00:30 +0200
    Bug#1043558: (no subject) Nathan Houghton <nathan@brainwerk.org> - 2023-11-17 10:10 +0100
    Bug#1043558: marked as done (keyboard doesn't respond after  waking up) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-02-20 15:40 +0100

#80026 — Bug#1043558: keyboard doesn't respond after waking up

Package: linux-image-6.1.0-11-amd64
Version: 6.1.38-4
Control: affects -1 src:linux linux gnome

After a stationary PC suspended itself due to inactivity and then woke 
up from suspend (on mouse or key press – I can't recollect), the 
keyboard was not responsive.  It had power: the LED 🄵 was lit. 
Pressing the keys (I tried several keys, including 🄵Umsch and NumLock) 
had no visible effect whatsoever.  After physically unplugging and 
plugging in the keyboard cable again to the same place, the keyboard 
starting working.

The keyboard has “Microsoft® Natural® Ergonomic Keyboard 4000 v1.0” and 
“Model: 1048” written on its bottom, has a German layout, and is 
connected to the PC via a cable ending with a USB-A plug.

As opposed to the keyboard, the mouse, which was plugged into the 
neighbor USB-A port, was working normally.

The error happens only seldom (every couple of weeks or even months) 
after suspend due to inactivity followed by getting awake; much more 
often, the keyboard works normally.  A simple test consisting of putting 
the PC to sleep manually followed by awakening it did not cause the 
error to reoccur.

Gratefully,
Alma

[toc] | [next] | [standalone]

#80027 — Processed: keyboard doesn't respond after waking up

Processing control commands:

> affects -1 src:linux linux gnome
Bug #1043558 [linux-image-6.1.0-11-amd64] keyboard doesn't respond after waking up
Added indication that 1043558 affects src:linux, linux, and gnome

-- 
1043558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043558
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#80028 — Bug#1043558: (no subject)

Correction:

> … and plugging in the keyboard again.

→

… and disconnecting the keyboard.

[toc] | [prev] | [next] | [standalone]

#80893 — Bug#1043558: (no subject)

I might be seeing the same issue -- at least the high level
behavior Alma describes matches what I am seeing on my desktop
system. I am not using the same keyboard (I am using a Leopold
FC200RT). Sometimes the issue also affects my USB mouse.

I also checked my systemd logs, comparing the good vs bad case,
and I noticed one difference. In the bad case, I see the
following prints during resume from suspend (grepped my systemd
journal for "usb" and "xhci"):

---8<---
Nov 15 22:53:26 carbon kernel: xhci_hcd 0000:06:00.0: xHC error in resume, USBSTS 0x401, Reinit
Nov 15 22:53:26 carbon kernel: usb usb5: root hub lost power or was reset
Nov 15 22:53:26 carbon kernel: usb usb6: root hub lost power or was reset
Nov 15 22:53:26 carbon kernel: xhci_hcd 0000:05:00.0: xHC error in resume, USBSTS 0x401, Reinit
Nov 15 22:53:26 carbon kernel: usb usb3: root hub lost power or was reset
Nov 15 22:53:26 carbon kernel: usb usb4: root hub lost power or was reset
Nov 15 22:53:26 carbon kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Nov 15 22:53:27 carbon kernel: input: Microsoft Xbox Series S|X Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input25
Nov 15 22:53:30 carbon ModemManager[752]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3': not supported by any plugin
Nov 15 22:53:39 carbon kernel: usb 1-5: USB disconnect, device number 5
Nov 15 22:53:43 carbon kernel: usb 1-5: new low-speed USB device number 9 using xhci_hcd
Nov 15 22:53:43 carbon kernel: usb 1-5: New USB device found, idVendor=04b4, idProduct=0101, bcdDevice= 0.01
Nov 15 22:53:43 carbon kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 15 22:53:43 carbon kernel: usb 1-5: Product: USB Keyboard
Nov 15 22:53:43 carbon kernel: usb 1-5: Manufacturer: Cypress
Nov 15 22:53:43 carbon kernel: input: Cypress USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/0003:04B4:0101.0006/input/input26
Nov 15 22:53:43 carbon kernel: hid-generic 0003:04B4:0101.0006: input,hidraw2: USB HID v1.11 Keyboard [Cypress USB Keyboard] on usb-0000:00:14.0-5/input0
Nov 15 22:53:43 carbon kernel: input: Cypress USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:04B4:0101.0007/input/input27
Nov 15 22:53:44 carbon mtp-probe[14339]: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5"
Nov 15 22:53:44 carbon kernel: input: Cypress USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:04B4:0101.0007/input/input28
Nov 15 22:53:44 carbon kernel: hid-generic 0003:04B4:0101.0007: input,hidraw3: USB HID v1.11 Keyboard [Cypress USB Keyboard] on usb-0000:00:14.0-5/input1
Nov 15 22:53:44 carbon /usr/libexec/gdm-x-session[1565]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/0003:04B4:0101.0006/input/input26/event4"
Nov 15 22:53:44 carbon /usr/libexec/gdm-x-session[1565]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:04B4:0101.0007/input/input27/event5"
Nov 15 22:53:44 carbon /usr/libexec/gdm-x-session[1565]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:04B4:0101.0007/input/input27/event5"
Nov 15 22:53:44 carbon /usr/libexec/gdm-x-session[1565]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:04B4:0101.0007/input/input28/event6"
Nov 15 22:53:44 carbon mtp-probe[14365]: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5"
---8<---

Versus the working case logs (manual suspend, resume a few
minutes later, same grep for "usb" and "xhci"):

---8<---
Nov 16 23:23:15 carbon kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Nov 16 23:23:15 carbon kernel: input: Microsoft Xbox Series S|X Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input22
Nov 16 23:23:18 carbon ModemManager[753]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3': not supported by any plugin
---8<---

The "xHC error in resume" and "root hub lost power or was reset"
messages are not present in the working case.

Similar messages also seem to be present in the logs shared by
Alma.

--

uname -a:

Linux carbon 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux

--

I'm running debian bookworm, with all the latest updates applied
(as of 11/17/2023).

Manually suspending (systemctl suspend) and then hitting a button
on my keyboard to wake the system back up after a short time (1-2
minutes) generally resumes without any issue (and the keyboard
continues to work also). I suspended and woke my machine 5 times
back to back, and all 5 times the keyboard worked fine after
resume.

The keyboard failing to work after exiting suspend seems to occur
most often for me when I boot my PC up, leave it idle for several
hours, and then come back to try and wake it up after it has been
suspended for a long time. This past week I have seen this
failure 2 to 3 times under similar circumstances. This is a
relatively new install, so I cannot comment on whether this issue
was seen in older kernels or previous debian releases.

[toc] | [prev] | [next] | [standalone]

#85937 — Bug#1043558: marked as done (keyboard doesn't respond after waking up)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 20 Feb 2025 15:33:17 +0100 (CET)
with message-id <20250220143317.7B199BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1043558,
regarding keyboard doesn't respond after waking up
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1043558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043558
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web