xhci: Workaround to get Intel xHCI reset working more reliably
Bug #1518816 reported by
XiongZhang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
| Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
| Vivid |
Won't Fix
|
Undecided
|
Unassigned | ||
| Wily |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
SRU Justification:
On all of Intel's shipping xHCI platforms, including both servers and clients, the controller can cause the shutdown process to hang.
This is because existing Intel xHCI controllers require a delay of 1 mS,after setting the CMD_RESET bit in command register, before accessing any HC registers. This allows the HC to complete the reset operation and be ready for HC register access.
Fix:
Patch in 4.4-rc2
commit a5964396190d0c4
Author: Rajmohan Mani <email address hidden>
Date: Wed Nov 18 10:48:20 2015 +0200
xhci: Workaround to get Intel xHCI reset working more reliably
Regression Potential: Just add a 1ms delay for xhci_reset, so regressions are very unlikely.
Revision history for this message
| Brad Figg (brad-figg) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Triaged |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Trusty): | |
| status: | New → Fix Committed |
| Changed in linux (Ubuntu Vivid): | |
| status: | New → Fix Committed |
| Changed in linux (Ubuntu Wily): | |
| status: | New → Fix Committed |
| Changed in linux (Ubuntu Trusty): | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Andy Whitcroft (apw) wrote Closing unsupported series nomination. | #2 |
| Changed in linux (Ubuntu Vivid): | |
| status: | Fix Committed → Won't Fix |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1518816
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.