| 2020-01-15 20:51:04 |
dann frazier |
bug |
|
|
added bug |
| 2020-01-15 20:51:13 |
dann frazier |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-01-15 20:51:13 |
dann frazier |
bug task added |
|
linux (Ubuntu Eoan) |
|
| 2020-01-15 20:51:13 |
dann frazier |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-01-15 20:51:13 |
dann frazier |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2020-01-15 20:51:13 |
dann frazier |
nominated for series |
|
Ubuntu Focal |
|
| 2020-01-15 20:51:13 |
dann frazier |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2020-01-15 20:51:13 |
dann frazier |
nominated for series |
|
Ubuntu Disco |
|
| 2020-01-15 20:51:13 |
dann frazier |
bug task added |
|
linux (Ubuntu Disco) |
|
| 2020-01-15 20:54:55 |
dann frazier |
linux (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2020-01-15 20:54:57 |
dann frazier |
linux (Ubuntu Disco): status |
New |
Confirmed |
|
| 2020-01-15 20:54:59 |
dann frazier |
linux (Ubuntu Eoan): status |
New |
Confirmed |
|
| 2020-01-15 20:55:01 |
dann frazier |
linux (Ubuntu Focal): status |
New |
Confirmed |
|
| 2020-06-30 14:08:12 |
Chad Sealock |
bug |
|
|
added subscriber Chad Sealock |
| 2020-07-02 19:58:39 |
Steve Langasek |
linux (Ubuntu Disco): status |
Confirmed |
Won't Fix |
|
| 2020-07-24 01:19:10 |
Matthew Ruffell |
bug task deleted |
linux (Ubuntu Focal) |
|
|
| 2020-07-24 01:19:18 |
Matthew Ruffell |
linux (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2020-07-24 01:19:55 |
Matthew Ruffell |
linux (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2020-07-24 01:19:58 |
Matthew Ruffell |
linux (Ubuntu Eoan): status |
Confirmed |
In Progress |
|
| 2020-07-24 01:41:09 |
Matthew Ruffell |
description |
This bug tracks the reapplication of "usb: handle warm-reset port requests on hub resume".
We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a regression it introduced (bug 1856608). However, that patch did fix an issue for a user, and reverting it requires us to diverge from mainline. Once we understand and resolve the regression, we should reapply it. |
[Impact]
We wish to reapply "usb: handle warm-reset port requests on hub resume".
We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a perceived regression it introduced (bug 1856608).
Only one customer saw this regression, and only in very specific systems. We have now determined that the root cause of the regression was that the systems used defective USB cables, which had Tx and Rx lines mixed up.
Signals were being sent down the wrong wires, placing the USB devices into a SS_INVALID link state, and this patch simply revealed the problems going on in the USB3 subsystem. USB3 devices never worked with these cables, but for some reason USB2 worked, which led to the long drawn out debugging timeframe.
We have confirmation from device hardware teams that USB cables on affected systems have their Tx and Rx wires mixed up, and this has also been confirmed by the USB cable manufacturer that these cables are a bad batch.
New USB cables fix the problem, and "usb: handle warm-reset port requests on hub resume" is safe to reapply.
[Fix]
We reapply upstream commit:
commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e
Author: Jan-Marek Glogowski <glogow@fbihome.de>
Date: Fri Feb 1 13:52:31 2019 +0100
Subject: usb: handle warm-reset port requests on hub resume
To the Bionic and Eoan kernels.
This commit fixes a real problem for users of a particular external hard disk, so it has value for Ubuntu users, and we do not want to diverge from upstream stable patches.
[Testcase]
For users with defective non-complaint USB cables:
dmesg | grep "Cannot enable"
For users with a particular USB-C external hard disk:
The disk will work as expected when it is plugged in.
[Regression Potential]
If any users in the community happen to use USB cables with Tx and Rx lines mixed up, they may see messages like:
"usb usb2-port2: Cannot enable. Maybe the USB cable is bad?"
These users need to swap out their USB cables for a non-defective one.
The commit landed in 5.1, and was backported to all stable kernels. As of 5.8-rc6, the commit is still in place, and has no fixup commits. I believe that re-introducing this commit will not cause any regressions for users with USB compliant hardware. |
|
| 2020-07-24 01:42:19 |
Matthew Ruffell |
description |
[Impact]
We wish to reapply "usb: handle warm-reset port requests on hub resume".
We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a perceived regression it introduced (bug 1856608).
Only one customer saw this regression, and only in very specific systems. We have now determined that the root cause of the regression was that the systems used defective USB cables, which had Tx and Rx lines mixed up.
Signals were being sent down the wrong wires, placing the USB devices into a SS_INVALID link state, and this patch simply revealed the problems going on in the USB3 subsystem. USB3 devices never worked with these cables, but for some reason USB2 worked, which led to the long drawn out debugging timeframe.
We have confirmation from device hardware teams that USB cables on affected systems have their Tx and Rx wires mixed up, and this has also been confirmed by the USB cable manufacturer that these cables are a bad batch.
New USB cables fix the problem, and "usb: handle warm-reset port requests on hub resume" is safe to reapply.
[Fix]
We reapply upstream commit:
commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e
Author: Jan-Marek Glogowski <glogow@fbihome.de>
Date: Fri Feb 1 13:52:31 2019 +0100
Subject: usb: handle warm-reset port requests on hub resume
To the Bionic and Eoan kernels.
This commit fixes a real problem for users of a particular external hard disk, so it has value for Ubuntu users, and we do not want to diverge from upstream stable patches.
[Testcase]
For users with defective non-complaint USB cables:
dmesg | grep "Cannot enable"
For users with a particular USB-C external hard disk:
The disk will work as expected when it is plugged in.
[Regression Potential]
If any users in the community happen to use USB cables with Tx and Rx lines mixed up, they may see messages like:
"usb usb2-port2: Cannot enable. Maybe the USB cable is bad?"
These users need to swap out their USB cables for a non-defective one.
The commit landed in 5.1, and was backported to all stable kernels. As of 5.8-rc6, the commit is still in place, and has no fixup commits. I believe that re-introducing this commit will not cause any regressions for users with USB compliant hardware. |
BugLink: https://bugs.launchpad.net/bugs/1859873
[Impact]
We wish to reapply "usb: handle warm-reset port requests on hub resume".
We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a perceived regression it introduced (bug 1856608).
Only one customer saw this regression, and only in very specific systems. We have now determined that the root cause of the regression was that the systems used defective USB cables, which had Tx and Rx lines mixed up.
Signals were being sent down the wrong wires, placing the USB devices into a SS_INVALID link state, and this patch simply revealed the problems going on in the USB3 subsystem. USB3 devices never worked with these cables, but for some reason USB2 worked, which led to the long drawn out debugging timeframe.
We have confirmation from device hardware teams that USB cables on affected systems have their Tx and Rx wires mixed up, and this has also been confirmed by the USB cable manufacturer that these cables are a bad batch.
New USB cables fix the problem, and "usb: handle warm-reset port requests on hub resume" is safe to reapply.
[Fix]
We reapply upstream commit:
commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e
Author: Jan-Marek Glogowski <glogow@fbihome.de>
Date: Fri Feb 1 13:52:31 2019 +0100
Subject: usb: handle warm-reset port requests on hub resume
To the Bionic and Eoan kernels.
This commit fixes a real problem for users of a particular external hard disk, so it has value for Ubuntu users, and we do not want to diverge from upstream stable patches.
[Testcase]
For users with defective non-complaint USB cables:
dmesg | grep "Cannot enable"
For users with a particular USB-C external hard disk:
The disk will work as expected when it is plugged in.
[Regression Potential]
If any users in the community happen to use USB cables with Tx and Rx lines mixed up, they may see messages like:
"usb usb2-port2: Cannot enable. Maybe the USB cable is bad?"
These users need to swap out their USB cables for a non-defective one.
The commit landed in 5.1, and was backported to all stable kernels. As of 5.8-rc6, the commit is still in place, and has no fixup commits. I believe that re-introducing this commit will not cause any regressions for users with USB compliant hardware. |
|
| 2020-07-24 01:42:48 |
Matthew Ruffell |
tags |
|
sts |
|
| 2020-07-24 04:37:46 |
Matthew Ruffell |
linux (Ubuntu Bionic): assignee |
|
Matthew Ruffell (mruffell) |
|
| 2020-07-24 04:37:49 |
Matthew Ruffell |
linux (Ubuntu Eoan): assignee |
|
Matthew Ruffell (mruffell) |
|
| 2020-07-27 21:10:21 |
Matthew Ruffell |
linux (Ubuntu Eoan): status |
In Progress |
Won't Fix |
|
| 2020-07-27 21:10:29 |
Matthew Ruffell |
linux (Ubuntu Eoan): assignee |
Matthew Ruffell (mruffell) |
|
|
| 2020-08-07 21:56:54 |
Khaled El Mously |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-08-10 18:52:37 |
Ubuntu Kernel Bot |
tags |
sts |
sts verification-needed-bionic |
|
| 2020-08-11 23:40:30 |
Matthew Ruffell |
tags |
sts verification-needed-bionic |
sts verification-done-bionic |
|
| 2020-09-01 10:15:06 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2021-01-01 22:56:42 |
Kevin Kim |
bug |
|
|
added subscriber Kevin Kim |
