This bug is awaiting verification that the linux-azure- nvidia-6.14/6.14.0-1006.6 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-azure- nvidia-6.14' to 'verification-done-noble-linux-azure-nvidia-6.14'. If the problem still exists, change the tag 'verification-needed-noble- linux-azure-nvidia-6.14' to 'verification-failed-noble-linux-azure- nvidia-6.14'.
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-azure-nvidia-6.14-v2 verification-needed-noble-linux-azure-nvidia-6.14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.14 in Ubuntu. https://bugs.launchpad.net/bugs/2115478 Title: [SRU] Add waiting latency for USB port resume Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux source package in Noble: Won't Fix Status in linux-oem-6.14 source package in Noble: Fix Released Status in linux source package in Plucky: Fix Released Status in linux-oem-6.14 source package in Plucky: Invalid Status in linux source package in Questing: Fix Released Status in linux-oem-6.14 source package in Questing: Invalid Bug description: [ Impact ] On certain USB3 device topologies, the hub will enter runtime resume before the down stream device to wake up. When a device is connect to such hub, the hub will enter runtime resume before the device generates any activities, making it not able to get detected. [ Fix ] ========================= OEM-6.14 ======================================= Cherry-pick the following commit: 1. [PATCH v2] usb: hub: fix detection of high tier USB3 devices behind suspended hubs[1] ========================= Plucky ============================ Cherry-pick the following commit: 1. usb: hub: fix detection of high tier USB3 devices behind suspended hubs[1] and backport the subsequent two commits, which fix an issue caused by the commit above: 2. usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm 3. usb: hub: Fix flushing of delayed work used for post resume purposes [ Test ] 1. Connect SD25TB5/WD25TB5 dock to SUT. 2. Connect USB3.0/3.1 sotarge to dock's USB port. 3. The USB storage should be recognized. [ Where problems could occurs ] This may increase resume latency for deeper USB device hierarchy. [ Additional Information ] [1] https://lore.kernel.org/linux- usb/[email protected]/ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2115478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
