On Mon, Sep 26, 2011 at 05:50:18PM +0800, Andiry Xu wrote: > On Fri, 2011-09-23 at 15:17 +0200, Oliver Neukum wrote: > > Am Freitag, 23. September 2011, 06:26:54 schrieb Andiry Xu: > > > On Thu, 2011-09-22 at 14:49 +0200, Oliver Neukum wrote: > > > > Hi, > > > > > > > > I see a device that fails during initialization after S3. It doesn't matter > > > > when S3 happens. After the controller has undergone an S3 cycle > > > > with or without the device, it becomes unable to cope with the device. > > > > > > > > I made logs with Andiry's debug patch cmd_ring.patch from the thread > > > > "problems with usb 3.0 on clevo p150hm" > > > > The problem is reproducible on xhci implementations from two vendors. > > > > It happens at least on 3.0.4, 3.1-rc5 and 3.1-rc7 > > > > > > > > The logs are > > > > xhcilog2.txt: taken with device plugged in > > > > xhcilog.txt: taken with the device plugged in after resumption from S3 > > > > > > > > The device is problematic even on UHCI: > > > > > > > > > > Oliver, > > > > > > Can you apply the patch attached to see if it helps? > > > > It helps somewhat. The device is still not usable, but at least the controller > > does not halt. The device does not respond to SET ADDRESS as it should. > > > > The patch re-initialize the host during resume. Does the issue occur > with cold boot and reboot with the device plugged-in? I suspect it's a > device issue. Sarah may give some suggestions. Oliver, can you try unplugging and replugging the device in after cold boot? Say, around 15 times or so? That should make the command ring wrap, and we can see if the xHCI driver is always writing off the end of the command ring, or if it only happens during those transfer errors. If you have CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING on, and you run `sudo dmesg -n 8`, you should be able to see the full xHCI debugging. You can stop after you've seen a toggle cycle bit line for the command ring. One thing I wonder is how the command ring *can* be full. If it's really full, then the host controller is not responding to commands (both types, in fact). I'll have to stare at the dmesg some more and come up with a possible patch to debug this further. Sarah Sharp -- 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
