Stranger and stranger...
I moved the USB adapter to a different slot so it's now behind fewer bridges:
-[0000:00]-+-00.0
+-01.0-[0000:01-04]----00.0-[0000:02-04]--+-02.0-[0000:03]--
| \-04.0-[0000:04]--
+-03.0-[0000:05]----00.0
+-07.0-[0000:06-07]----00.0-[0000:07]--+-00.0
| +-00.1
| \-00.2
The devices listed here are:
00:00.0 Host bridge: Intel Corporation X58 I/O Hub to ESI Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13)
01:00.0 PCI bridge: Integrated Device Technology, Inc. PES12T3G2 PCI Express Gen2 Switch (rev 01)
02:02.0 PCI bridge: Integrated Device Technology, Inc. PES12T3G2 PCI Express Gen2 Switch (rev 01)
02:04.0 PCI bridge: Integrated Device Technology, Inc. PES12T3G2 PCI Express Gen2 Switch (rev 01)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13)
06:00.0 is 06:00.0 PCI bridge: PLX Technology, Inc. PEX 8111 PCI Express-to-PCI Bridge (rev 21)
07:00.0 USB Controller: NEC Corporation USB (rev 43)
07:00.1 USB Controller: NEC Corporation USB (rev 43)
07:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
Now, here's the odd thing...
these devices lock up the NEC USB adapter:
Bus 001 Device 004: ID 1307:0165 Transcend Information, Inc. 2GB/4GB Flash Drive
But this one doesn't:
Bus 005 Device 003: ID 0951:1603 Kingston Technology Data Traveler 1GB/2GB Pen Drive
Ah! Because the latter is hot in high-speed mode:
/dev/sdd:
Timing cached reads: 2 MB in 2.75 seconds = 745.72 kB/sec
Timing buffered disk reads: 4 MB in 5.52 seconds = 741.76 kB/sec
And the Transcend sometimes messes up even using the Intel motherboard USB controller:
[ 1076.501986] usb 1-4: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 4 ret -110
[ 1081.490979] usb 1-4: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 0 len 2 ret -110
but that's not fatal.
--
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
