On 26.02.2018 16:05, Oliver Neukum wrote:
Am Dienstag, den 13.02.2018, 13:56 -0800 schrieb The Real Bev:
I went back to the distribution kernel for 64-bit 14.2 slackware --
4.14.18. During boot, dmesg displays the following errors:
[ 15.850711] xhci_hcd 0000:09:00.0: not ready 4195ms after FLR; waiting
[ 20.458401] xhci_hcd 0000:09:00.0: not ready 8291ms after FLR; waiting
[ 29.161245] xhci_hcd 0000:09:00.0: not ready 16483ms after FLR; waiting
[ 46.058397] xhci_hcd 0000:09:00.0: not ready 32867ms after FLR; waiting
[ 82.922254] xhci_hcd 0000:09:00.0: not ready 65635ms after FLR; giving up
[ 83.261301] xhci_hcd 0000:09:00.0: Refused to change power state,
currently in D3
[ 83.352431] xhci_hcd 0000:09:00.0: xHCI Host Controller
[ 83.387291] xhci_hcd 0000:09:00.0: new USB bus registered, assigned
bus number 11
[ 83.699853] xhci_hcd 0000:09:00.0: Host halt failed, -19
[ 83.731151] xhci_hcd 0000:09:00.0: can't setup: -19
[ 83.764138] xhci_hcd 0000:09:00.0: USB bus 11 deregistered
[ 83.821909] xhci_hcd 0000:09:00.0: init 0000:09:00.0 fail, -19
This is the same problem I've had for 4.9.79, 4.15.2 and now 4.14.18.
There is clearly a problem. I give up. I'm just going to live with it.
Hi Mathias,
it looks like a relatively old issue with D3 on some instances of XHCI.
Yep, The "Host halt failed, -19" (ENODEV) is seen when xhci driver tries to
halt the host during setup, polling a mmio register but reading only 0xffffffff.
Which I guess is expected if controller is still on D3.
No idea why this controller fails to change from D3 to D0.
Any PCI changes betewen 4.8 and 4.9?
-Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
