On Sat, 5 May 2012, Martin Mokrejs wrote: > Hi Alan, > I am testing how the ASMedia2105 works with USB2 controllers (while being USB3.0 > capable and doing well with Texas Instruments host while not with NEC uPD720200 > 3.0.25 nor 3.0.2.8 firmwares at least). I see four different scenarios when testing > with the eSATA/USB port in my laptop, Dell Vostro3550. Should be the below chip. I don't understand. Why did you send this email? > It failed for me once but I do not have the corresponding usbmon capture. ... > [10462.609293] hub 1-1:1.0: port 1, status 0101, change 0000, 12 Mb/s > [10462.689285] usb 1-1.1: new full-speed USB device number 4 using ehci_hcd > [10462.768925] usb 1-1.1: device descriptor read/64, error -32 > [10462.958779] usb 1-1.1: device descriptor read/64, error -32 > [10463.148504] usb 1-1.1: new full-speed USB device number 5 using ehci_hcd > [10463.228382] usb 1-1.1: device descriptor read/64, error -32 > [10463.418105] usb 1-1.1: device descriptor read/64, error -32 > [10463.607817] usb 1-1.1: new full-speed USB device number 6 using ehci_hcd > [10464.026931] usb 1-1.1: device not accepting address 6, error -32 > [10464.107070] usb 1-1.1: new full-speed USB device number 7 using ehci_hcd > [10464.526181] usb 1-1.1: device not accepting address 7, error -32 > [10464.526459] hub 1-1:1.0: unable to enumerate USB device on port 1 ... > While trying to reproduce the issue I ended up with 4 different dmesg snippets and > corresponding usbmon traces (attached). > Maybe it is still of some help? Help for what? Do you want to know why the 2105 doesn't work very well? My impression is that it turns on the electrical connection to the computer before it is fully set up and ready to operate. As a result, the first one or two times it can't respond properly when the computer tries to initialize it. Alan Stern -- 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
