same problem in F19

3.11.8-200.fc19.x86_64 #1 SMP Wed Nov 13 16:29:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

in addition, I have a lot of these show up in the syslog:

kernel: [ 2540.755503] uvcvideo: Failed to set UVC probe control : -110 (exp. 26)

rmmod uvcvideo and then a modprobe uvcvideo gives:

kernel: [ 3836.518124] uvcvideo: Found UVC 1.00 device <unnamed> (046d:08cc)
kernel: [ 3841.516797] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
kernel: [ 3846.513766] uvcvideo: Failed to query (129) UVC probe control : -110 (exp. 26).
kernel: [ 3846.513774] uvcvideo: Failed to initialize the device (-5).
kernel: [ 3846.514030] usbcore: registered new interface driver uvcvideo
kernel: [ 3846.514036] USB Video Class driver (1.1.1)

and then nothing.  The video device is not created.  If I restart the machine, I can run cheese for about 10 seconds before the errors start, and eventually the camera turns off.

A few other notes.  This camera was working fine in previous kernel versions in Fedora 19, though I am not certain when it broke, it was recent.  I keep the kernels up to date almost daily as they come out in the main release (rarely from the updates-testing repo).

The machine uses an Asus z87i-deluxe with the latest firmware (0702).

I have tried both USB 2 and USB 3 ports with the same behavior.

unplugging/replugging the camera gives the following:

Nov 18 22:38:18 neptune colord: device removed: sysfs-046d-08cc
Nov 18 22:38:28 neptune kernel: [ 4687.948568] usb 3-6: new high-speed USB device number 10 using xhci_hcd
Nov 18 22:38:28 neptune kernel: [ 4688.112816] usb 3-6: New USB device found, idVendor=046d, idProduct=08cc
Nov 18 22:38:28 neptune kernel: [ 4688.112824] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 22:38:28 neptune kernel: [ 4688.112829] usb 3-6: SerialNumber: 4FA2B2A0
Nov 18 22:38:28 neptune kernel: [ 4688.113588] uvcvideo: Found UVC 1.00 device <unnamed> (046d:08cc)
Nov 18 22:38:28 neptune kernel: [ 4688.158065] input: UVC Camera (046d:08cc) as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/input/input20
Nov 18 22:38:28 neptune kernel: [ 4688.185265] ALSA sound/usb/mixer.c:1303 usb_audio: Warning! Unlikely big volume range (=3072), cval->res is probably wrong.
Nov 18 22:38:28 neptune mtp-probe: checking bus 3, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
Nov 18 22:38:28 neptune mtp-probe: bus: 3, device: 10 was not an MTP device
Nov 18 22:38:28 neptune colord: Device added: sysfs-046d-08cc


at this point the device exists, and remains until it is accessed.

When accessed:

Nov 18 22:40:32 neptune kernel: [ 4688.185273] ALSA sound/usb/mixer.c:1307 usb_audio: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1<4>[ 4811.548590] xhci_queue_intr_tx: 7 callbacks suppressed
Nov 18 22:40:37 neptune kernel: [ 4817.097339] xhci_queue_intr_tx: 5 callbacks suppressed
Nov 18 22:40:43 neptune kernel: [ 4822.710049] xhci_queue_intr_tx: 1 callbacks suppressed
Nov 18 22:40:48 neptune kernel: [ 4828.306766] xhci_queue_intr_tx: 29 callbacks suppressed

the callbacks suppressed continue for a bit, then this:

Nov 18 22:43:29 neptune kernel: [ 4988.724713] xhci_queue_intr_tx: 10 callbacks suppressed
Nov 18 22:43:30 neptune kernel: [ 4989.618292] uvcvideo: Failed to query (131) UVC probe control : -32 (exp. 26).
Nov 18 22:43:30 neptune kernel: [ 4989.620135] uvcvideo: Failed to set UVC probe control : -32 (exp. 26).
Nov 18 22:43:55 neptune kernel: [ 5014.296234] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).


The light goes out on the camera, and it becomes unresponsive.

Joel, I would be curious to know if your camera behaves the same way, realizing it is probably integrated, but does it have an on/off switch?

>Joel, I would be curious to know if your camera behaves the same way, realizing it is probably integrated, but does it have an on/off switch?

No on/off switch for me. It fails right at boot, and never works afterwards.

We are conflating two different issues here:
- Joel has camera: 05ca:18ff which is some Ricoh co. Ltd. device?
- Jim has camera: 046d:08cc which is Logitech Orbit, yes?

Since both devices are not listed in the quirks table in 
drivers/media/usb/uvc/uvc_driver.c you could try to see if setting
any quirks will fix the situation.

This is the table of all availavle device quirks:
/* Devices quirks */
#define UVC_QUIRK_STATUS_INTERVAL       0x00000001
#define UVC_QUIRK_PROBE_MINMAX          0x00000002
#define UVC_QUIRK_PROBE_EXTRAFIELDS     0x00000004
#define UVC_QUIRK_BUILTIN_ISIGHT        0x00000008
#define UVC_QUIRK_STREAM_NO_FID         0x00000010
#define UVC_QUIRK_IGNORE_SELECTOR_UNIT  0x00000020
#define UVC_QUIRK_FIX_BANDWIDTH         0x00000080
#define UVC_QUIRK_PROBE_DEF             0x00000100
#define UVC_QUIRK_RESTRICT_FRAME_RATE   0x00000200


So just try to load your module with the option quirks=xyz
Here are the most used ones:
      5  UVC_QUIRK_FIX_BANDWIDTH 
      6  UVC_QUIRK_PROBE_DEF 
      1  UVC_QUIRK_PROBE_EXTRAFIELDS 
     14  UVC_QUIRK_PROBE_MINMAX 
      1  UVC_QUIRK_RESTRICT_FRAME_RATE 
      1  UVC_QUIRK_STATUS_INTERVAL 
     10  UVC_QUIRK_STREAM_NO_FID 

Try them all and let's see if any of them or their combination improve things.

I tried each of these quirks with a 'rmmod uvcvideo ; modprobe uvcvideo quirks=0x<quirk number here>'

All of them still resulted in error messages looking like:

Nov 25 15:20:19 f20 kernel: usbcore: deregistering interface driver uvcvideo
Nov 25 15:20:21 f20 kernel: uvcvideo: Found UVC 1.00 device NoData (05ca:18ff)
Nov 25 15:20:21 f20 kernel: uvcvideo: Forcing device quirks to 0x200 by module parameter for testing purpose.
Nov 25 15:20:21 f20 kernel: uvcvideo: Please report required quirks to the linux-uvc-devel mailing list.
Nov 25 15:20:21 f20 kernel: uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
Nov 25 15:20:21 f20 kernel: uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
Nov 25 15:20:21 f20 kernel: uvcvideo: Failed to initialize the device (-5).
Nov 25 15:20:21 f20 kernel: usbcore: registered new interface driver uvcvideo
Nov 25 15:20:21 f20 kernel: USB Video Class driver (1.1.1)

I also tried with 'trace=0xffff', and it gives out a little more output before failing:

Nov 25 15:20:30 f20 kernel: uvcvideo: Probing generic UVC device 1.6
Nov 25 15:20:30 f20 kernel: uvcvideo: Found format YUV 4:2:2 (YUYV).
Nov 25 15:20:30 f20 kernel: uvcvideo: - 176x144 (30.0 fps)
Nov 25 15:20:30 f20 kernel: uvcvideo: Found a Status endpoint (addr 81).
Nov 25 15:20:30 f20 kernel: uvcvideo: Found UVC 1.00 device NoData (05ca:18ff)
Nov 25 15:20:30 f20 kernel: uvcvideo: Scanning UVC chain: OT 3 <- XU 2 <- IT 1
Nov 25 15:20:30 f20 kernel: uvcvideo: Found a valid video chain (1 -> 3).
Nov 25 15:20:30 f20 kernel: uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
Nov 25 15:20:30 f20 kernel: uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
Nov 25 15:20:30 f20 kernel: uvcvideo: Failed to initialize the device (-5).
Nov 25 15:20:30 f20 kernel: usbcore: registered new interface driver uvcvideo
Nov 25 15:20:30 f20 kernel: USB Video Class driver (1.1.1)

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.13.4-200.fc20.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.