Re: Isochronous URB submission failure upon resume
Alan Stern <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, 2 Sep 2007, Laurent Pinchart wrote: > I'm not sure to know to which device uvcvideo is bound. What do the numbers > in 'usb 4-1:1.1' mean ? Do the first two digits relate to the bus# and port# > as found in /proc/bus/usb/devices ? The driver is bound to the Chicony device > listed in /proc/bus/usb/devices. The "4" is the bus number. The "-1" means port 1 on the root hub. (Note that this shows up as port 0 in /proc/bus/usb/devices for some unknown reason.) The ":1.1" means configuration 1, interface 1. > > -45 is -EL2NSYNC, which is used only by ehci-hcd. It indicates that > > the URB was submitted after the first time slot had already expired. > > Shouldn't the URB_ISO_ASAP flag prevent that from happening ? It should. You might want to look at http://bugzilla.kernel.org/show_bug.cgi?id=7694 That part of the code has never been fully reliable. Christopher "Monty" Montgomery tried fixing it up, but I don't think his fixes were all accepted. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel