On Thu, 15 Mar 2012, Reartes Guillermo wrote: > Basically, when i instert a media on a dvd writer (TEAC DV-W28SS-R) > attached to a SATA-USB Bridge (Sunplus) plugged to a HUB (TERMINUS) > attached to > an USB controller there are USB Resets. > > Typical reset: > > Mar 15 12:44:25 slack kernel: [ 587.206783] usb 1-2.3: USB > disconnect, device number 4 > Mar 15 12:44:26 slack kernel: [ 588.140418] usb 1-2.3: new high-speed > USB device number 5 using ehci_hcd > Mar 15 12:44:26 slack kernel: [ 588.219672] usb 1-2.3: New USB device > found, idVendor=1bcf, idProduct=0c31 > Mar 15 12:44:26 slack kernel: [ 588.219675] usb 1-2.3: New USB device > strings: Mfr=1, Product=2, SerialNumber=3 > Mar 15 12:44:26 slack kernel: [ 588.219677] usb 1-2.3: Product: USB > to Serial-ATA bridge > Mar 15 12:44:26 slack kernel: [ 588.219679] usb 1-2.3: Manufacturer: > Sunplus Innovation Technology > Mar 15 12:44:26 slack kernel: [ 588.219681] usb 1-2.3: SerialNumber: > DF0F28FF0F0001832517 > Mar 15 12:44:26 slack kernel: [ 588.221377] scsi6 : usb-storage 1-2.3:1.0 > Mar 15 12:44:27 slack kernel: [ 589.242436] scsi 6:0:0:0: CD-ROM > TEAC DV-W28SS-R 1.0C PQ: 0 ANSI: 0 > Mar 15 12:44:31 slack kernel: [ 593.815170] sr 6:0:0:0: Attached scsi > generic sg1 type 5 > Mar 15 12:44:40 slack kernel: [ 602.054781] usb 1-2.3: USB > disconnect, device number 5 > Mar 15 12:44:40 slack kernel: [ 602.732420] usb 1-2.3: new high-speed > USB device number 6 using ehci_hcd > Mar 15 12:44:40 slack kernel: [ 602.811672] usb 1-2.3: New USB device > found, idVendor=1bcf, idProduct=0c31 ... Those aren't resets; they are disconnects. > I performed test on two systems, 3 usb controllers, and different os > (it is already uploaded to te bug-report), the results varies > with os version and controller. I was unable to reproduce the usb > reset attaching the SATA-Bridge directly to the USB host > controller. It sounds like your hub isn't working right. Or maybe your USB cables. 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
