On Tue, Sep 06, 2011 at 07:33:25PM -0400, Alan Stern wrote: > On Tue, 6 Sep 2011, Don Zickus wrote: > > > Hi Sarah, > > > > I setup a system that has a VIA usb3 hub connected to an Intel Panther > > Point usb3 root hub. On top of that I stuck a usb3 Western Digital > > harddrive behind the VIA usb3 hub. It looks like below > > > > usb3 PP (root hub) -> usb3 VIA (hub) -> usb3 WD disk > > > > I noticed on boot up I get a bunch of 'Device not responding to set > > address.' Looking further it seems to be on the virtual usb2 side of the > > usb3 hub (3-3), whereas everything is fine on the usb3 side of the usb3 > > hub (4-3). > > > > I am sure there is some probing that has to happen to detect if the device > > is connected on the usb2 or usb3 bus. But I didn't expect it to be noisy > > if things failed. Any pointers on where to look to figure this out? > > > > Thanks, > > Don > > > > lsusb output > > (bus 004 device 002 is supposed to be the VIA hub) > > > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > > Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > > Bus 001 Device 003: ID 0624:0291 Avocent Corp. > > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 004 Device 002: ID 2109:0810 > > Bus 004 Device 003: ID 1058:0730 Western Digital Technologies, Inc. > > Shouldn't there be an entry listing bus 003 device 002 for the VIA > hub's USB-2 component? Dunno. It wasn't listed. I assumed that was the part that was failing. Cheers, Don -- 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
