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

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

Bug#943713: linux: T495 fails to suspend USB device, hangs kworker after failed suspend

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

Contents

  Bug#943713: linux: T495 fails to suspend USB device, hangs kworker after failed suspend Luit van Drongelen <luitvd@gmail.com> - 2019-10-28 15:10 +0100

#65527 — Bug#943713: linux: T495 fails to suspend USB device, hangs kworker after failed suspend

Source: linux
Severity: normal

Dear Maintainer,

My laptop _sometimes_ doesn't suspend, leaving it in a state where
graphics in gnome-shell (Wayland) are in an unusable state, even though
GDM and non-graphic terminals still work. With the laptop in this state,
shutting down or rebooting won't work either, which seems to be caused
by a stuck kworker.

I'm seeing kernel messages that appear to point at a USB hub, and the
hung kworker is in Workqueue: usb_hub_wq hub_event [usbcore]. As far as
I can tell, it seems related to bluetooth, as it mainly happens at work
where I use a Bluetooth mouse. 

Full output of the kernel for the hung kworker and for the failed
suspend can be found here: 
https://gist.github.com/Luit/ca685a406629d784d366b62254929575

I'm currently running a kernel from experimental because it happened
with the testing kernel and I hoped for it to be fixed there.

The system has a Ryzen 7 PRO 3700U CPU and Intel Wireless + Bluetooth.

Kind regards,
Luit


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (102, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [standalone]

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

csiph-web