ov511 verbose startup.
The changes to ov511 in 2.5.3 seem to generate excessive amounts of blurb on boot up for me..
ov511.c: USB OV511+ camera foundov511.c: model: Creative Labs WebCam 3ov511.c: Sensor is an OV7620ov511.c: Device registered on minor 0
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 137 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110
...
repeat last two lines another dozen or so times...
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 14 lines · Dave Jones
The changes to ov511 in 2.5.3 seem to generate excessive amounts of blurb on boot up for me..
ov511.c: USB OV511+ camera foundov511.c: model: Creative Labs WebCam 3ov511.c: Sensor is an OV7620ov511.c: Device registered on minor 0
usbdevfs:USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 137 ret -75 usb_control/bulk_msg: timeout
usbdevfs:USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 18 ret -110 usb_control/bulk_msg: timeout
usbdevfs:USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 18 ret -110
...
repeat last two lines another dozen or so times...
What userspace program are you using that is talking to the usb device through usbfs? Or is this usbutils trying to determine what driver to load?
thanks,
greg k-h
Quoted 8 lines · Greg KH
Quoted 5 lines
usbdevfs:
USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 18 ret -110 usb_control/bulk_msg: timeout
usbdevfs:USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 18 ret -110
...
repeat last two lines another dozen or so times...What userspace program are you using that is talking to the usb device through usbfs? Or is this usbutils trying to determine what driver to load?
More than likely usbutils. There shouldn't be anything else running on startup that touches usb.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 18 lines · Greg KH
Quoted 15 lines · Dave Jones
The changes to ov511 in 2.5.3 seem to generate excessive amounts of blurb on boot up for me..
ov511.c: USB OV511+ camera foundov511.c: model: Creative Labs WebCam 3ov511.c: Sensor is an OV7620ov511.c: Device registered on minor 0
usbdevfs:USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 137 ret -75 usb_control/bulk_msg: timeout
usbdevfs:USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 18 ret -110 usb_control/bulk_msg: timeout
usbdevfs:USBDEVFS_CONTROLfailed dev 2 rqt 128 rq 6 len 18 ret -110
...
repeat last two lines another dozen or so times...
Quoted 4 lines
What userspace program are you using that is talking to the usb device through usbfs? Or is this usbutils trying to determine what driver to load?
I have been getting reports of -75 (babble?) and -110 errors with both control and iso transfers. The problematic kernels seem to be 2.4.17+, with uhci HCD. IIRC, nearly all of the reports mentioned a Via chipset. There are sporadic reports of corrupted iso packets (blocks of zeros inserted randomly) with uhci under 2.4.17 as well.
This is the first case of a usbfs-related ov511 error that I have seen. Very strange.
Greg (if you know): usbfs is not allowed to access claimed interfaces, correct? (ie. ones that are implicitly claimed because of a successful return from probe()). Are interfaces treated as claimed while probe() is active, so that user-space "probes" cannot interfere with driver probes()?
I use usb-uhci, uhci, and usb-ohci regularly with ov511, and I have never seen any of these problems. There are clearly a number of factors involved here.
Signature · 2 lines
Mark McClelland [email protected]
Quoted 5 lines · Mark McClelland
Greg (if you know): usbfs is not allowed to access claimed interfaces, correct? (ie. ones that are implicitly claimed because of a successful return from
probe()). Are interfaces treated as claimed whileprobe()is active, so that user-space "probes" cannot interfere with driverprobes()?
Yes, but odds are, it is trying to read the configuration of the device, and we don't have control pipe locking, yet :)
Dave, does this problem go away on 2.5.3-pre6?
And which host controller driver are you using?
thanks,
greg k-h
Quoted 3 lines · Greg KH
Yes, but odds are, it is trying to read the configuration of the device, and we don't have control pipe locking, yet :)
Dave, does this problem go away on 2.5.3-pre6?
Yes. From what I recall. I'll build a pre6 later to double check.
Quoted 1 line
And which host controller driver are you using?
CONFIG_USB_UHCI_ALT=y
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 1 line · Greg KH
Dave, does this problem go away on 2.5.3-pre6?
Great, heisenbug. Subsequent reboots under any kernel haven't managed to reproduce the problem.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs