> I'll whip up some patches that allow you to disable USB 3.0 Link PM for > the VIA hub and we'll see if that helps. Or you could downgrade to the > 3.4 kernel and see if that helps, since USB 3.0 Link PM went into 3.5. Thanks Sarah. I tried in 3.4.11 to .. about the same thing .. http://d3xt3r01.tk/~dexter/usbmon.trace.txt contains a new trace. 1 drive plugged in the usb hub, connected to the asrock. dexter@d3xt3r01 ~ $ cp -v /media/sdd1/en ~ ‘/media/sdd1/en’ -> ‘/home/dexter/en’ cp: reading ‘/media/sdd1/eno’: Input/output error cp: failed to extend ‘/home/dexter/en’: Input/output error 2012-09-24T21:08:35.407758+03:00 d3xt3r01 kernel: [ 227.308783] EXT4-fs (sdb1): recovery complete 2012-09-24T21:08:35.408911+03:00 d3xt3r01 kernel: [ 227.309606] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) 2012-09-24T21:08:57.192369+03:00 d3xt3r01 kernel: [ 249.092067] usb 2-2.2: reset SuperSpeed USB device number 5 using xhci_hcd 2012-09-24T21:08:57.203739+03:00 d3xt3r01 kernel: [ 249.104503] usb 2-2.2: Parent hub missing LPM exit latency info. Power management will be impacted. 2012-09-24T21:08:57.204902+03:00 d3xt3r01 kernel: [ 249.105266] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88010b35b980 2012-09-24T21:08:57.204913+03:00 d3xt3r01 kernel: [ 249.105277] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88010b35b9c0 2012-09-24T21:09:32.386789+03:00 d3xt3r01 kernel: [ 284.287436] hub 2-2:1.0: Cannot enable port 2. Maybe the USB cable is bad? 2012-09-24T21:09:32.913454+03:00 d3xt3r01 kernel: [ 284.813228] sd 9:0:0:0: Device offlined - not ready after error recovery 2012-09-24T21:09:32.913478+03:00 d3xt3r01 kernel: [ 284.813248] sd 9:0:0:0: [sdb] Unhandled error code 2012-09-24T21:09:32.913487+03:00 d3xt3r01 kernel: [ 284.813254] sd 9:0:0:0: [sdb] 2012-09-24T21:09:32.913492+03:00 d3xt3r01 kernel: [ 284.813259] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK 2012-09-24T21:09:32.913496+03:00 d3xt3r01 kernel: [ 284.813266] sd 9:0:0:0: [sdb] CDB: 2012-09-24T21:09:32.913501+03:00 d3xt3r01 kernel: [ 284.813270] Read(10): 28 00 00 07 a9 80 00 00 f0 00 2012-09-24T21:09:32.913505+03:00 d3xt3r01 kernel: [ 284.813289] end_request: I/O error, dev sdb, sector 502144 2012-09-24T21:09:32.913509+03:00 d3xt3r01 kernel: [ 284.813337] sd 9:0:0:0: rejecting I/O to offline device 2012-09-24T21:09:32.913514+03:00 d3xt3r01 kernel: [ 284.813347] sd 9:0:0:0: [sdb] killing request 2012-09-24T21:09:32.913518+03:00 d3xt3r01 kernel: [ 284.813362] sd 9:0:0:0: rejecting I/O to offline device 2012-09-24T21:09:32.913522+03:00 d3xt3r01 kernel: [ 284.813382] sd 9:0:0:0: rejecting I/O to offline device 2012-09-24T21:09:32.913526+03:00 d3xt3r01 kernel: [ 284.813399] sd 9:0:0:0: rejecting I/O to offline device 2012-09-24T21:09:32.913530+03:00 d3xt3r01 kernel: [ 284.813428] sd 9:0:0:0: [sdb] Unhandled error code 2012-09-24T21:09:32.913534+03:00 d3xt3r01 kernel: [ 284.813435] sd 9:0:0:0: [sdb] 2012-09-24T21:09:32.913539+03:00 d3xt3r01 kernel: [ 284.813439] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 2012-09-24T21:09:32.913543+03:00 d3xt3r01 kernel: [ 284.813446] sd 9:0:0:0: [sdb] CDB: 2012-09-24T21:09:32.913546+03:00 d3xt3r01 kernel: [ 284.813449] Read(10): 28 00 00 07 aa 70 00 00 10 00 2012-09-24T21:09:32.913550+03:00 d3xt3r01 kernel: [ 284.813466] end_request: I/O error, dev sdb, sector 502384 2012-09-24T21:09:32.929259+03:00 d3xt3r01 kernel: [ 284.829046] usb 2-2.2: USB disconnect, device number 5 The drive died ( as in shut down .. I have to manually plug it out and back in the power outlet now )... -- 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
