On Wed, Jul 24, 2013 at 11:03 PM, Alan Stern <st...@rowland.harvard.edu> wrote: > On Wed, 24 Jul 2013, Philipp Dreimann wrote: > >> Hello, >> >> one of my external HDDs does not work using 3.11-rc2. The drive works >> using 3.10, and 3.9, except for a suspend/resume issue described here: >> https://bugzilla.redhat.com/show_bug.cgi?id=984189 . >> >> dmesg snipped: >> [ 119.334908] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd >> [ 119.347397] usb 4-1: Parent hub missing LPM exit latency info. >> Power management will be impacted. >> [ 119.350614] usb 4-1: New USB device found, idVendor=054c, idProduct=c005 >> [ 119.350620] usb 4-1: New USB device strings: Mfr=1, Product=2, >> SerialNumber=3 >> [ 119.350624] usb 4-1: Product: USB 3.0 SATA Bridge >> [ 119.350627] usb 4-1: Manufacturer: VIA Technologies Inc. >> [ 119.350630] usb 4-1: SerialNumber: l刁A柜鬨xffffffc2\xffffff80籁7鮘d >> [ 119.377782] usb-storage 4-1:1.0: USB Mass Storage device detected >> [ 119.377847] scsi6 : usb-storage 4-1:1.0 >> [ 119.377900] usbcore: registered new interface driver usb-storage >> [ 129.844989] scsi 6:0:0:0: Direct-Access Hitachi HDS5C3030BLE >> MZ6O PQ: 0 ANSI: 6 >> [ 129.845465] sd 6:0:0:0: Attached scsi generic sg1 type 0 >> [ 129.863425] sd 6:0:0:0: [sdb] 732566646 4096-byte logical blocks: >> (3.00 TB/2.72 TiB) >> [ 129.871203] sd 6:0:0:0: [sdb] Write Protect is off >> [ 129.871209] sd 6:0:0:0: [sdb] Mode Sense: 2f 00 00 00 >> [ 129.879196] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: >> enabled, doesn't support DPO or FUA >> [ 160.787920] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd >> [ 160.800582] usb 4-1: Parent hub missing LPM exit latency info. >> Power management will be impacted. >> [ 160.801795] usb 4-1: device firmware changed >> [ 160.801857] usb 4-1: USB disconnect, device number 2 >> [ 160.801938] sd 6:0:0:0: Device offlined - not ready after error recovery >> [ 160.805190] sd 6:0:0:0: [sdb] READ CAPACITY failed >> [ 160.805194] sd 6:0:0:0: [sdb] >> [ 160.805195] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK >> [ 160.805197] sd 6:0:0:0: [sdb] Sense not available. >> [ 160.805218] sd 6:0:0:0: [sdb] Asking for cache data failed >> [ 160.805220] sd 6:0:0:0: [sdb] Assuming drive cache: write through >> [ 160.805233] sdb: detected capacity change from 3000592982016 to 0 >> [ 160.805353] sd 6:0:0:0: [sdb] READ CAPACITY failed >> [ 160.805357] sd 6:0:0:0: [sdb] >> [ 160.805359] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK >> [ 160.805361] sd 6:0:0:0: [sdb] Sense not available. >> [ 160.805383] sd 6:0:0:0: [sdb] No Caching mode page present >> [ 160.805386] sd 6:0:0:0: [sdb] Assuming drive cache: write through >> [ 160.805397] sd 6:0:0:0: [sdb] Attached SCSI disk >> [ 160.806605] xhci_hcd 0000:0e:00.0: xHCI xhci_drop_endpoint called >> with disabled ep ffff880212315e80 >> [ 160.806609] xhci_hcd 0000:0e:00.0: xHCI xhci_drop_endpoint called >> with disabled ep ffff880212315ec0 >> >> kernel log, lsusb and usbmon are attached. I tried usb2 and 3 ports, >> both have the same issue with this drive. Other drives work. > > The problem is caused by some program on your computer sending a > command to the drive that it can't handle (SCSI INQUIRY command with a > transfer length of 512). It is not a kernel problem.
Thanks, I can reproduce the issue using kernel 3.9.9 and $ sg_inq -l 512 /dev/sdb I am guessing that this is the reason for the suspend/resume issues with 3.9 and 3.10 as well. A look at the program's code might reveal why this was not triggered on 3.9 and 3.10 as bad as on 3.11... -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
