This bug is awaiting verification that the linux-oem-6.11/6.11.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done- noble-linux-oem-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-failed- noble-linux-oem-6.11'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2085410 Title: Fix USB device suspend failure while HCD in S4 wakeup Status in linux package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux source package in Oracular: New Status in linux-oem-6.11 source package in Oracular: New Status in linux source package in Plucky: New Status in linux-oem-6.11 source package in Plucky: New Bug description: [SRU Justification] [Impact] More and more USB device suspend failure are caused by the un-expected HCD_FLAG_WAKEUP_PENDING on the USB host controller. It mostly happens on the USB devices connected to the high-speed root hub. It randomly happens when put the system into suspend [Fix] Fixed by the upstream fix https://lore.kernel.org/linux-usb/20241012094633.126736-1-duancheng...@kylinos.cn/. Set wakeup to false if suspend type is either PM_EVENT_FREEZE or PM_EVENT_QUIESCE [Test Case] 1. Power on machine and connect a USB device to the high-speed root hub. (Find your device in lsusb in the secondary root hub) 2. run checkbox-cli run com.canonical.certification::suspend-cycles-stress-test 3. observe the suspend/resume fail with the kernel message [Where problems could occur] Add more restriction on how the wakeup should be performed. Should be low risk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
