On Tue, 3 Sep 2013, Sarah Sharp wrote: > > With the USB 2.0 hub, I could use usbmon to check out why the device > > does not work. Using usbmon on a USB 3.0 hub does not seem to show any > > valuable output. I tried both usbmon client and 'cat 6u' (where 6 is > > the bus id) to check usbmon output. > > Did you run `lsusb -t` to find out which bus the device is actually > under? The xHCI host registers two roothubs: a USB 2.0 roothub and a > USB 3.0 roothub. You want to record usbmon for the USB 2.0 roothub (the > bus marked with a 480 MB speed). > > You can also try recording all USB traffic through the 0u file. > > > I am the developer for this usb device and the device works fine on a > > 1.11 and a 2.0 hub. > > Do you mean that it works fine behind an external USB 1.1 or USB 2.0 hub > attached to an xHCI port, or do you mean it works under an EHCI, UHCI, > or OHCI host? Please send `lsusb -t` and `sudo lsusb -v` output for > both the failing and passing cases. > > > With the kernel xhci debugging option, there is a > > lot of output, I am wondering if there is a usbmon-like debugging > > mechanism for xhci. > > Can you send dmesg with CONFIG_USB_XHCI_HCD_DEBUGGING turned on and > CONFIG_USB_DEBUG turned on? The lack of output from usbmon is probably because the kernel isn't sending any URBs to the new device. The Set-Address request is sent automatically by the xHCI controller, and if it doesn't work then there's nothing for the kernel to communicate with. 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
