dmesg prints xhci error messages after resuming from s3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Invalid
|
Low
|
Adam Lee | ||
linux (Ubuntu) |
Invalid
|
Low
|
Adam Lee | ||
Trusty |
Invalid
|
Low
|
Adam Lee |
Bug Description
kernel: 3.13.0-24-generic
xhci controller:
00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Lenovo Device [17aa:501c]
Flags: bus master, medium devsel, latency 0, IRQ 56
Memory at f1700000 (64-bit, non-prefetchable) [size=64K]
Kernel driver in use: xhci_hcd
[ 1410.931247] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021e3ad6c0
[ 1410.931248] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021e3ad700
[ 1410.931249] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021e3ad740
[ 1410.931250] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021ded1980
[ 1410.931251] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88021ded19c0
error messages popped up after resuming from s3, annoying.
description: | updated |
summary: |
- xhci error messages after resuming from s3 + dmesg prints xhci error messages after resuming from s3 |
tags: | added: blocks-hwcert-enablement |
description: | updated |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Trusty): | |
importance: | Medium → Low |
Changed in linux (Ubuntu): | |
importance: | Medium → Low |
Changed in hwe-next: | |
importance: | Undecided → Low |
status: | New → In Progress |
assignee: | nobody → Adam Lee (adam8157) |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1308871
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.