On Sat, Jun 11, 2011 at 06:54:50PM +0000, Michael Niederle wrote: > Hi, Sarah! > > > There are two patches that Greg pushed to Linus yesterday that should > > solve this issue: > > > > e2b0217 xhci: Add defines for hardcoded slot states > > 001fd38 xhci: Do not issue device reset when device is not setup > > > > If you test with latest tree, it should fix your issue. The patches are > > marked as being bound for the stable trees. > > > > Let me know if you run into any other problems with the Etron xHCI host. > > I applied the two patches (with minimal adjustments) to a 2.6.39 kernel and > they worked well! Great! > I append the kernel log created by attaching a USB-3-pen-drive. It contains > several warnings. Do you mean these warnings: > [ 205.305183] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep > [ 205.305712] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep > [ 205.306336] xhci_hcd 0000:02:00.0: WARN: short transfer on control ep Don't worry about those, the xHCI driver is just being stupidly verbose. That's fixed in the 3.0 kernel. > I'm also not sure, whether the pen-drive works at its full > speed (I benchmarked about 37MB/s (read), but expected about 70 to 90MB/s). Are you plugging in a USB 2.0 device or a USB 3.0 device? Because your device enumerated as a USB 2.0 (high speed) device: > 0x101 [ 203.360838] usb 3-1: new high speed USB device number 2 using xhci_hcd Googling around suggests the Kingston DT Ultimate should be a USB 3.0 device, but I need to be sure. 37 MB/s is pretty much all you'll get out of a USB 2.0 device, when you take 8b10b encoding and the crufty design of the USB mass storage driver (BoT driver) into account. You need to have a USB 3.0 device to fully use the USB 3.0 bus bandwidth. Then you should see a minimum of around 175 MB/s with an SSD in a USB 3.0 enclosure. > Lots of thanks to you, Greg and all the others involved for this great support! You're welcome. :) 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
