|Summary:||Enabling USB (auto)suspend (power control) for xHCI controllers incurs random device failures since kernel 4.15|
|Component:||USB||Assignee:||Greg Kroah-Hartman (greg)|
Description mwohah 2018-05-10 18:27:47 UTC
Since the upgrade to Linux 4.15 (and also in 4.16), I'm experiencing an issue where all my USB devices just die seemingly without any cause. Both my laptop's internal (attached) keyboard as well as my external keyboard die. Replugging the external keyboard unfortunately does not solve the problem. My touchpad, on the other hand, continues to work, though it may internally be connected via PS/2. After this happens, I have only been able to solve it by rebooting. In the logs, the following error can be found. xhci_hcd 0000:3d:00.0: xHCI host controller not responding, assume dead Previously, similar issues occurred to users that could be fixed by adding intel_iommu=false to the kernel parameters. This however seems to be a different problem, as it newly occurs in this specific kernel version and is not solved by the aforementioned solution. This was also posted at the Archlinux forums , where we managed to pin down the issue to being related to xHCI and autosuspend (power management). I'm using powertop's --auto-tune and disabling the "good" setting for all xHCI controllers again makes the issue disappear. Linux 4.14 and lower also do not expose this issue. Please also find attached the complete journalctl output of one boot from start to finish that exposed the issue, which may be helpful during debugging. Thanks!  https://bbs.archlinux.org/viewtopic.php?pid=1784603
Comment 2 Greg Kroah-Hartman 2018-05-10 18:44:50 UTC
On Thu, May 10, 2018 at 06:27:47PM +0000, email@example.com wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=199681 > > Bug ID: 199681 > Summary: Enabling USB (auto)suspend (power control) for xHCI > controllers incurs random device failures since kernel > 4.15 All USB bugs should be sent to the firstname.lastname@example.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release.