Fix Terminus USB hub that may breaks connected USB devices after S3
Bug #1806850 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 |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
USB devices connected to Terminus USB hub stop working after S3.
[Fix]
The Terminus hub seems to have a rather slow reset command, so we need to wait for extra time before doing any further action.
[Test]
After applying the fix, USB devices connected to the HUB no longer stop functioning after S3.
[Regression Potential]
Low. Although the fix affects all devices connect to the HUB, it has no functional change other than imposes longer delay time.
tags: | added: originate-from-1791001 somerville |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in linux (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Cosmic): | |
status: | New → In Progress |
Changed in linux-oem (Ubuntu Bionic): | |
status: | New → Fix Released |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Cosmic): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-cosmic removed: verification-needed-cosmic |
tags: | added: cscc |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in hwe-next: | |
status: | New → Fix Released |
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 1806850
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.