On Tue, Aug 03, 2010 at 10:20:58AM -0400, Alan Stern wrote: > On Tue, 3 Aug 2010, Jeff Chua wrote: > > > I'm trying out USB3.0 and connected a hard disk enclosure with a known-good > > hard disk to an USB 3.0 express-card. > > > > > From dmesg, it's able to recognize the card and disk, but I can't even use > > "fdisk /dev/sdb" ... what else do I need? > > > > xhci_hcd 0000:05:00.0: enabling device (0000 -> 0002) > > xhci_hcd 0000:05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > > xhci_hcd 0000:05:00.0: setting latency timer to 64 > > xhci_hcd 0000:05:00.0: xHCI Host Controller > > xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3 > > xhci_hcd 0000:05:00.0: irq 19, io mem 0xf0000000 > > usb usb3: No SuperSpeed endpoint companion for config 1 interface 0 > > altsetting 0 ep 129: using minimum values > > xHCI xhci_add_endpoint called for root hub > > xHCI xhci_check_bandwidth called for root hub > > hub 3-0:1.0: USB hub found > > hub 3-0:1.0: 4 ports detected > > hub 3-0:1.0: unable to enumerate USB device on port 3 > > usb 3-1: new SuperSpeed USB device using xhci_hcd and address 2 > > xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > > xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > > xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > > xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > > > > Initializing USB Mass Storage driver... > > scsi7 : usb-storage 3-2:1.0 > > usbcore: registered new interface driver usb-storage > > USB Mass Storage support registered. > > scsi 7:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 0 > > sd 7:0:0:0: Attached scsi generic sg1 type 0 > > sd 7:0:0:0: [sdb] Attached SCSI removable disk > > > > > > > > # here's the same disk connected to USB2.0 port showing the partition table and > > fdisk works > > > > Initializing USB Mass Storage driver... > > scsi6 : usb-storage 1-1.2:1.0 > > usbcore: registered new interface driver usb-storage > > USB Mass Storage support registered. > > scsi 6:0:0:0: Direct-Access SAMSUNG MMDOE56G5MXP-0VB VBM1 PQ: 0 ANSI: 0 > > sd 6:0:0:0: Attached scsi generic sg1 type 0 > > sd 6:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 GiB) > > sd 6:0:0:0: [sdb] Write Protect is off > > sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00 > > sd 6:0:0:0: [sdb] Assuming drive cache: write through > > sd 6:0:0:0: [sdb] Assuming drive cache: write through > > sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 > > sdb14 sdb15 > > > sd 6:0:0:0: [sdb] Assuming drive cache: write through > > sd 6:0:0:0: [sdb] Attached SCSI disk > > > > > > It seems USB3.0 cannot detect the disk. USB2.0 says it's "SAMSUNG > > MMDOE56G5MXP-0VB VBM1 PQ: 0 ANSI: 0" and that's same as plug straight to > > the notebook SATA controller. I checked linux/drivers/scsi/sd.c and > > sdkp->media_present = 0 so skipped sd_read_capacity(). > > > > > > Running on Linux-2.6.35. Is this a USB3.0 problem or usb-storage issue? > > How do I go about to debug this? > > Post a usbmon trace showing what happens when you connect the drive to > a USB-3 controller. Instructions are in Documentation/usb/usbmon.txt. Also, please enable CONFIG_USB_XHCI_HCD_DEBUGGING, and post the contents of `tail -f /var/log/kern.log > xhci.log` when you run fdisk. Sarah Sharp -- 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
