USB_ERR_TIMEOUT and USB_ERR_STALLED
I am trying to use RELENG_8 to monitor a number of APC upses and it seems when there are more than one, I start to see a lot of USB errors with the devices coming and going In the logs, I see a lot of # grep USB /var/log/all.log | tail Oct 21 10:24:05 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:25:47 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:27:45 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:29:44 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:30:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:32:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:37:04 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:38:38 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:44:14 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:45:09 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 # usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: EHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: product 0xf103 vendor 0x2001 at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.3: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: Back-UPS RS 1500 FW:8.g9a.D USB FW:g9a American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.5: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.6: Back-UPS RS 1500 FW:8.g9a.D USB FW:g9a American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.7: Back-UPS RS 1500 FW:8.g4 .D USB FW:g4 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.8: USB2.0 Hub vendor 0x05e3 at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.9: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.10: Back-UPS RS 1500 FW:8.g7 .D USB FW:g7 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.11: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON This is with a kernel from Oct 4th, i386. Any idea what might be up or how to debug this ?? Setting hw.usb.debug to anything 0 causes the system to almost hang under the load unfortunately. ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
USB 3.0 Fails To Attach Western Digital My Book 3.0
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: xh...@pci0:5:0:0: class=0x0c0330 card=0x 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 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 = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x 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 = 0x 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= Output when plugging in the WD 3.0 into the 2.0 port: Oct 21 01:15:20 gandalf root: Unknown USB device: vendor 0x1058 product 0x1123 bus uhub3 Oct 21 01:15:20 gandalf kernel: ugen3.4: Western Digital at usbus3 Oct 21 01:15:20 gandalf kernel: umass0: Western Digital My Book 3.0, class 0/0, rev 2.10/10.10, addr 4 on usbus3 Oct 21 01:15:20 gandalf kernel: umass0: SCSI over Bulk-Only; quirks = 0x Oct 21 01:15:21 gandalf kernel: umass0:9:0:-1: Attached to scbus9 Oct 21 01:15:28 gandalf kernel: da0 at umass-sim0 bus 0 scbus9 target 0 lun 0 Oct 21 01:15:28 gandalf kernel: da0: WD My Book 3.0 1123 1010 Fixed Direct Access SCSI-4 device Oct 21 01:15:28 gandalf kernel: da0: 40.000MB/s transfers Oct 21 01:15:28 gandalf kernel: da0: 953867MB (1953519616 512 byte sectors: 255H 63S/T 121600C) Output when plugging in 2.0 device into the 3.0 port: Oct 21 01:09:54 gandalf root: Unknown USB device: vendor 0x090c product 0x1000 bus uhub4 Oct 21 01:09:54 gandalf kernel: ugen4.2: USB at usbus4 Oct 21 01:09:54 gandalf kernel: umass1: USB Flash Disk, class 0/0, rev 2.00/11.00, addr 1 on usbus4 Oct 21 01:09:54 gandalf kernel: umass1: SCSI over Bulk-Only; quirks = 0x Oct 21 01:09:55 gandalf kernel: umass1:10:1:-1: Attached to scbus10 Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Oct 21 01:09:56 gandalf kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Oct 21 01:09:56 gandalf kernel: da1 at umass-sim1 bus 1 scbus10 target 0 lun 0 Oct 21 01:09:56 gandalf kernel: da1: USB Flash Disk 1100 Fixed Direct Access SCSI-0 device Oct 21 01:09:56 gandalf kernel: da1: 40.000MB/s transfers Oct 21 01:09:56 gandalf kernel: da1: 956MB (1957888 512 byte sectors: 64H 32S/T 956C) --Michael ___ freebsd-usb@freebsd.org mailing list
Re: USB 3.0 Fails To Attach Western Digital My Book 3.0
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: xh...@pci0:5:0:0: class=0x0c0330 card=0x 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 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 = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x 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 = 0x 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 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB_ERR_TIMEOUT and USB_ERR_STALLED
On Thursday 21 October 2010 17:02:30 Mike Tancsa wrote: I am trying to use RELENG_8 to monitor a number of APC upses and it seems when there are more than one, I start to see a lot of USB errors with the devices coming and going In the logs, I see a lot of # grep USB /var/log/all.log | tail Oct 21 10:24:05 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:25:47 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:27:45 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:29:44 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:30:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:32:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:37:04 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:38:38 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:44:14 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:45:09 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 # usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: EHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: product 0xf103 vendor 0x2001 at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.3: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: Back-UPS RS 1500 FW:8.g9a.D USB FW:g9a American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.5: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.6: Back-UPS RS 1500 FW:8.g9a.D USB FW:g9a American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.7: Back-UPS RS 1500 FW:8.g4 .D USB FW:g4 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.8: USB2.0 Hub vendor 0x05e3 at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.9: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.10: Back-UPS RS 1500 FW:8.g7 .D USB FW:g7 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.11: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON This is with a kernel from Oct 4th, i386. Any idea what might be up or how to debug this ?? Setting hw.usb.debug to anything 0 causes the system to almost hang under the load unfortunately. ---Mike Weongyo is working on a usbdump utility to monitor ongoing USB traffic. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
