On Tue, Mar 13, 2012 at 02:18, Xu, Andiry <Andiry.Xu@xxxxxxx> wrote: >> > > xhci_hcd 0000:0d:00.0: Poll event ring: 4308439040 >> > > xhci_hcd 0000:0d:00.0: op reg status = 0xffffffff >> > > xhci_hcd 0000:0d:00.0: HW died, polling stopped. >> > >> > This means your host controller is dead after suspend: op reg status >> > reads 0xffffffff indicates the xHC is not working at all, it's in >> > a status like "plug out". >> >> It doesn't necessarily mean that the host got removed. When the PCI >> host controller goes into D3, the registers will read as 0xffffffff. So >> I suspect the host was just suspended when the polling loop ran. We >> need a better way for the polling loop to know the host controller died >> instead of checking the registers. > > I agree with you, but for this case, the suspend is actually failed: > Stop xHC in xhci_suspend() timeout and the function returns -110. > The save state register is not set. I think the PCI host controller > does not go into D3 in this case, right? Is there a way how I could verify this hypothesis? Any other ideas? Regards, Thilo P.S.: Just updated to 3.3 - I'll keep you updated whether the freezes are still an issue... -- 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
