[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#943713: marked as done (linux: T495 fails to suspend USB device, hangs kworker after failed suspend)

Your message dated Thu, 20 Feb 2025 12:34:46 +0100 (CET)
with message-id <20250220113446.1A190BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #943713,
regarding linux: T495 fails to suspend USB device, hangs kworker after failed suspend
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.)


-- 
943713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943713
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: