On Tue, 6 Nov 2012, Jason J. Herne wrote: > Here is the pcap file, as captured from Wireshark. > > On Tue, Nov 6, 2012 at 10:46 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > On Mon, 5 Nov 2012, Jason J. Herne wrote: > > > >> I have a Seagate ST3000DM 3.0TB Sata Drive enclosed in a Vantec > >> NexStar CX USB 3.0/2.0 Enclosure. This enclosure/drive is not > >> properly recognized by Linux when plugged in via a USB 2.0 port. My > >> dmesg output, at first, seems like all is well. but then the drive > >> activity light starts flashing rapidly and never stops. After 20-30 > >> seconds I see a "reset high-speed USB device" message. The /dev/sdx > >> device node is created for the drive, but no sdxN nodes are created > >> and any program accessing the /dev/sdx node hangs. I have tried this > >> drive with 3 different computers all running Ubuntu 12.04 (kernel > >> 3.2.0-30-generic-pae) or Ubuntu 11.10 (kernel 3.0.0-12). I have also > >> tried the 3.7.0-rc4-next kernel. The problem persists on all of the > >> above kernels. > >> > >> It is worth noting that the drive is properly recognized by Windows 7 > >> running on the same hardware as my Ubuntu install. > >> > >> I am providing some output that I hope is useful for diagnosing the > >> problem. I can collect more if needed. I can also provide the raw > >> tcpdump capture file as saved by Wireshark. I don't understand much > >> of the trace I collected, but it seems to get interesting around Frame > >> 108: URB status: Remote I/O error (-EREMOTEIO) (-121). The trace shows that everything works perfectly up until the first READ command sent to the drive. The computer tries to read the first 8 blocks (4096 bytes) from the drive, but the drive sends no data back at all. After 30 seconds the computer gives up and tries to reset the drive. There's no easy way to tell what's different about Windows. Maybe a USB log of the Windows interaction would show something, maybe not. 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
