Bug 759643 - 2.6.41.3-1.fc15 uvcvideo broken with 0402:5606, "Failed to submit URB 0 (-28)"
Summary: 2.6.41.3-1.fc15 uvcvideo broken with 0402:5606, "Failed to submit URB 0 (-28)"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-02 22:09 UTC by James
Modified: 2011-12-02 22:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-02 22:21:32 UTC
Type: ---

Attachments (Terms of Use)
dmesg output (70.46 KB, text/x-log)
2011-12-02 22:09 UTC, James 		no flags Details
lsusb -vvvv output (42.40 KB, text/plain)
2011-12-02 22:10 UTC, James 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description James 2011-12-02 22:09:51 UTC 
Created attachment 539798 [details]
dmesg output

My webcam (USB device 0402:5606) no longer works with 2.6.41.3-1.fc15.x86_64. The salient entries in dmesg are:


$ dmesg|grep uvcvideo
[   24.767456] uvcvideo: Found UVC 1.00 device USB2.0 Camera (0402:5606)
[   24.827711] usbcore: registered new interface driver uvcvideo
[   31.074510] uvcvideo: UVC non compliance - GET_MIN/MAX(PROBE) incorrectly supported. Enabling workaround.
[ 2548.370802] uvcvideo: Failed to submit URB 0 (-28).


Complete log and output of lsusb are attached. Testing with Cheese results in the error messages


libv4l2: error turning on stream: No space left on device

** (cheese:3115): WARNING **: Error starting streaming on device '/dev/video0'.


** (cheese:3115): WARNING **: Could not negotiate format


Works fine with kernel-2.6.41.1-3.fc15.x86_64.
Comment 1 James 2011-12-02 22:10:17 UTC 
Created attachment 539799 [details]
lsusb -vvvv output
Comment 2 James 2011-12-02 22:21:32 UTC 
Well, it seems happy again with 2.6.41.4-1.fc15.x86_64. (Possibly f0cc710a6dec5b808a6f13f1f8853c094fce5f12 ?)
Note You need to log in before you can comment on or make changes to this bug.