Date: Thu, 21 Oct 2010 22:53:57 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-usb@freebsd.org Cc: mav@freebsd.org Subject: Re: USB 3.0 Fails To Attach Western Digital My Book 3.0 Message-ID: <201010212253.57555.hselasky@c2i.net> In-Reply-To: <4CBFEBF5.30203@comcast.net> References: <4CBFEBF5.30203@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 21 October 2010 09:29:57 Michael Martin wrote: > Thanks for the new USB 3.0 effort! > > I'm testing it out on 9.0-CURRENT amd64. The controller seems to find a > 2.0 usb stick fine. However, when I plug in a Western Digital 3.0 > drive, the device fails to attach. The WD drive attaches fine when > plugging into a 2.0 port on the motherboard. > > Controller info: > > xhci0@pci0:5:0:0: class=0x0c0330 card=0xffffffff chip=0x01941033 > rev=0x03 hdr=0x00 > vendor = 'NEC Electronics Hong Kong' > class = serial bus > subclass = USB > bar [10] = type Memory, range 64, base 0xfbbfe000, size 8192, > enabled cap 01[50] = powerspec 3 supports D0 D3 current D0 > cap 05[70] = MSI supports 8 messages, 64 bit > cap 11[90] = MSI-X supports 8 messages in map 0x10 > cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0003[140] = Serial 1 ffffffffffffffff > ecap 0018[150] = unknown 1 > > WD 3.0 Drive Info ( while plugged into the 2.0 port ): > > ugen3.4: <My Book 3.0 Western Digital> at usbus3, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0210 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x1058 > idProduct = 0x1123 > bcdDevice = 0x1010 > iManufacturer = 0x0001 <Western Digital> > iProduct = 0x0002 <My Book 3.0> > iSerialNumber = 0x0003 <XXXRemovedXXX> > bNumConfigurations = 0x0001 > > Output when plugging in the Western Digital 3.0 into the 3.0 port: > > Oct 21 01:03:54 gandalf root: Unknown USB device: vendor 0x1058 product > 0x1123 bus uhub4 > Oct 21 01:03:54 gandalf kernel: ugen4.2: <Western Digital> at usbus4 > Oct 21 01:03:54 gandalf kernel: umass0: <Western Digital My Book 3.0, > class 0/0, rev 3.00/10.10, addr 1> on usbus4 > Oct 21 01:03:54 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = > 0x0000 > Oct 21 01:03:55 gandalf kernel: umass0:9:0:-1: Attached to scbus9 > Oct 21 01:03:57 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 error=28 > Oct 21 01:03:57 gandalf last message repeated 2 times > Oct 21 01:03:57 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > offset= size= error= > Oct 21 01:04:03 gandalf kernel: ugen4.2: <Western Digital> at usbus4 > (disconnected) > Oct 21 01:04:03 gandalf kernel: umass0: at uhub4, port 2, addr 1 > (disconnected) > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): lost device > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): got CAM status 0xa > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0:0:0): fatal error, > failed to attach to device > Oct 21 01:04:03 gandalf kernel: (da0:umass-sim0:0: > Oct 21 01:04:03 gandalf kernel: 0:0): removing device entry > Oct 21 01:04:14 gandalf root: ZFS: zpool I/O failure, zpool=wd3.1 error=28 > Oct 21 01:04:14 gandalf last message repeated 2 times > Oct 21 01:04:14 gandalf root: ZFS: vdev I/O failure, zpool=wd3.1 path= > offset= size= error= > Hi, 1) Try to enable UMASS debugging (you maybe need to rebuild kernel with options USB_DEBUG): sysctl hw.usb.umass.debug=-1 2) Also try to boot without umass in the kernel. What is the output from usbconfig, like descriptors, etc ... in USB 3.0 mode. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201010212253.57555.hselasky>