On Wed, 1 May 2013, Martin Mokrejs wrote:
That's not how drivers work in Linux. They don't unbind all by
themselves; they wait until the bus-level code tells them to unbind.
xhci-hcd is not alone in this respect; all the drivers behave this way.
I don't believe that. From my tests only
On Wed, 1 May 2013, Martin Mokrejs wrote:
Sarah Sharp wrote:
The HW died, polling stopped message is harmless. It happens when the
xHCI host goes into a PCI low power state (D3). When the PCI host goes
into D3cold, the registers will read as all Fs, and the polling loop
will mistakenly
Alan Stern wrote:
On Wed, 1 May 2013, Martin Mokrejs wrote:
Sarah Sharp wrote:
The HW died, polling stopped message is harmless. It happens when the
xHCI host goes into a PCI low power state (D3). When the PCI host goes
into D3cold, the registers will read as all Fs, and the polling loop
:00.0: op reg status = 0x0
+[ 123.191570] xhci_hcd :0b:00.0: ir_set 0 pending = 0x2
+[ 123.191574] xhci_hcd :11:00.0: HW died, polling stopped.
+[ 123.191580] xhci_hcd :0b:00.0: HC error bitmask = 0x0
At this step xhci_hcd should unbind the dead device so that it's sysfs entries
reg status = 0x0
+[ 123.191570] xhci_hcd :0b:00.0: ir_set 0 pending = 0x2
+[ 123.191574] xhci_hcd :11:00.0: HW died, polling stopped.
+[ 123.191580] xhci_hcd :0b:00.0: HC error bitmask = 0x0
At this step xhci_hcd should unbind the dead device so that it's sysfs
entries could
] xhci_hcd :11:00.0: op reg status = 0x
+[ 123.191563] xhci_hcd :0b:00.0: op reg status = 0x0
+[ 123.191570] xhci_hcd :0b:00.0: ir_set 0 pending = 0x2
+[ 123.191574] xhci_hcd :11:00.0: HW died, polling stopped.
+[ 123.191580] xhci_hcd :0b:00.0: HC error bitmask = 0x0
