On Thu, 7 Jun 2012, Sarah Sharp wrote: > On Mon, Jun 04, 2012 at 06:24:50PM +0100, James wrote: > > Hello, > > > > I'm experiencing issues with Canon EOS DSLRs (60D, 400D -- both have > > USB 2.0 connections) when connected to a USB 3.0 port on my > > notebook. After connecting it, the camera seems to be recognised by > > the kernel, but is sometimes unusable by gphoto2; Nautilus never > > seems to recognise it on USB 3.0. In dmesg, immediately after > > connecting: > > > > > > [ 72.674463] usb 3-1: new high-speed USB device number 2 using xhci_hcd > > [ 72.764255] usb 3-1: New USB device found, idVendor=04a9, idProduct=3215 > > [ 72.764265] usb 3-1: New USB device strings: Mfr=1, Product=2, > > SerialNumber=0 > > [ 72.764272] usb 3-1: Product: Canon Digital Camera > > [ 72.764276] usb 3-1: Manufacturer: Canon Inc. > > [ 72.765264] usb 3-1: ep 0x81 - rounding interval to 32768 > > microframes, ep desc says 0 microframes > > [ 72.765275] usb 3-1: ep 0x2 - rounding interval to 32768 > > microframes, ep desc says 0 microframes > > Can you please post the output of `sudo lsusb -v -d 04a9:3215`? Your > device is advertising an endpoint interval of zero microframes, and the > xHCI driver is setting the internally used interval to the highest > interval. That would make interrupt or isochronous transfers take a > *very* long time. The xHCI driver should just set the interval to one > microframe instead. I've seen those sorts of messages many times before. They probably are bulk endpoints. Alan Stern -- 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
