On Wed, Oct 24, 2012 at 12:52:18PM -0400, covici@xxxxxxxxxxxxxx wrote: > Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx> wrote: > > > On Wed, Oct 24, 2012 at 11:13:51AM -0400, covici@xxxxxxxxxxxxxx wrote: > > > I cannot post dmesg output befcause it starts spewing messages before > > > any disk is mounted -- I have to shut down and reboot without the drive > > > plugged in. But see a previous message where I posted some more > > > information in this thread. But to answer your questions, the enclosure > > > has its own power and it does work with usb2 -- although I have not > > > booted with it plugged in in that state, so I will have to check. > > > > So it does not get better if you unplugg the device later on? You could either > > try netconsole (Documentation/networking/netconsole.txt assuming you have > > already network) if this works or maybe even simpler, boot your own kernel and > > after you booted modprobe the xhci driver (and hope that it still behaves that > > way). > > I will have to try that, but when this has happened in the past with > kernels like 3.4.0, unplugging and replugging the drive did not fix > anything. I will have to see if the xhci module is in there at the > time. I'm wondering if perhaps your device isn't responding to the Set Address control transfer, and the xHCI driver is getting stuck with the command on the command ring. Can you try the latest kernel from Linus' tree? There's some command cancellation patches that went into 3.7 (that are marked for stable) that should fix that particular issue. 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
