On Wed, Oct 24, 2012 at 11:12:18AM -0400, Alan Stern wrote: > On Wed, 24 Oct 2012, Greg KH wrote: > > > On Wed, Oct 24, 2012 at 10:12:47AM -0400, Alan Stern wrote: > > > On Wed, 24 Oct 2012, Matthias Schniedermeyer wrote: > > > > > > > Hi > > > > > > > > > > > > I have a 3TB WD HDD in an USB3 enclosure that fails to show up if i > > > > connect the USB3-cable first and then switch on the enclosure. > > > > (Example-Log see below) > > > > > > > > If i either: > > > > - Wait a little before connecting the USB3-cable > > > > - Disconnect/Reconnect the USB3-cable > > > > - rmmod xhci; modprobe xhci > > > > The HDD shows up and works normally. > > > > > > > > Question is, is there something that i can do that doesn't involve > > > > 'rmmod'ing the xhci-driver or doing something physical? > > > > Is there a way to force a "rescan"? > > > > For e.g. is there something that i can do to a sysfs-file to force a > > > > "rescan" of the USB-port? > > > > Or can i prolong the timeout, which appears to be 5 seconds. > > > > > > The 5-second limit is part of the USB-2 specification (sections 9.2.6.1 > > > and 9.2.6.4). > > > > And it can be increased with the delay_use module parameter to the > > usb_storage driver. > > No, it can't. That module parameter affects a different delay, in > usb-storage. Matthias's problem is the delay in > usb_set_configuration(). Ah, my mistake, you are right, nevermind... -- 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
