System cannot detect USB device in BAT mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Critical
|
Phidias | ||
linux (Ubuntu) |
Invalid
|
Critical
|
Phidias | ||
Vivid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
On some Skylake-U platforms, if boots with battery only and has no USB device connect, after boot the USB port can't be used, even though the xHCI Host Controller doesn't report any error in dmesg. The USB device looks like doesn't turn on, LED on USB mouse or keyboard doesn't light up.
[Fix]
There's a fix in mainline v4.2-rc3, though it states the fix is for Braswell, but the uuid use in the commit can also be found on Skylake-U platforms.
Commit log is as follows:
commit c3c5819a3509524
Author: Mathias Nyman <email address hidden>
Date: Tue Jul 21 17:20:25 2015 +0300
xhci: call BIOS workaround to enable runtime suspend on Intel Braswell
Intel xhci hw that require XHCI_PME_STUCK quirk have as default disabled
xhci from going to D3 state in runtime suspend. Driver needs to verify
it can deal with the hw by calling an ACPI _DSM method to get D3 enabled.
Signed-off-by: Mathias Nyman <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
[Test]
1. Install the patched kernel
2. Boot with battery
3. Insert a USB device (disk, keyboard, mouse), should work normally
Related branches
Changed in hwe-next: | |
importance: | Undecided → Critical |
assignee: | nobody → Phidias (phidias-chiang) |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → Critical |
tags: | added: kernel-acpi |
Changed in linux (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in linux (Ubuntu Vivid): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Triaged → Invalid |
tags: |
added: verification-done-vivid removed: verification-needed-vivid |
Changed in hwe-next: | |
status: | Triaged → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1489292
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.