Make Dell WD19 dock more reliable after suspend
Bug #1868217 reported by
Kai-Heng Feng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-osp1 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub
used internally may stop working after suspend.
[Fix]
Disable LPM on the Realtek USB Hub, and let xHCI controller make sure
the link state transition is completed.
[Test]
After applying the patches, the Dell WD19 works reliably after thousand
times for suspend/resume cycle.
[Regression Potential]
Low. This replaces the currently "msleep" way with more robust
mechanism. I also test other systems and nothing breaks.
CVE References
Changed in linux (Ubuntu Bionic): | |
status: | New → Won't Fix |
Changed in linux-oem-osp1 (Ubuntu Eoan): | |
status: | New → Won't Fix |
Changed in linux-oem-osp1 (Ubuntu Focal): | |
status: | New → Won't Fix |
tags: | added: oem-priority originate-from-1853942 somerville |
Changed in linux (Ubuntu Focal): | |
status: | Incomplete → Fix Committed |
Changed in linux (Ubuntu Eoan): | |
status: | Incomplete → Fix Committed |
tags: |
added: verification-done-eoan verification-done-focal removed: verification-needed-eoan verification-needed-focal |
Changed in linux-oem-osp1 (Ubuntu Bionic): | |
status: | New → Fix Committed |
Changed in hwe-next: | |
status: | New → Fix Released |
Changed in linux-oem-osp1 (Ubuntu): | |
status: | New → Invalid |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1868217
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.