← Back to team overview

kernel-packages team mailing list archive

[Bug 1518816] [NEW] xhci: Workaround to get Intel xHCI reset working more reliably

 

Public bug reported:

 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 a5964396190d0c40dd549c23848c282fffa5d1f2
Author: Rajmohan Mani <rajmohan.mani@xxxxxxxxx>
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.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1518816

Title:
   xhci: Workaround to get Intel xHCI reset working more reliably

Status in linux package in Ubuntu:
  New

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 a5964396190d0c40dd549c23848c282fffa5d1f2
  Author: Rajmohan Mani <rajmohan.mani@xxxxxxxxx>
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518816/+subscriptions


Follow ups