[linux-uvc-devel] Failed to resubmit video URB (-1)

[Grozdan]

Hi,

I'm currently running a Logitech C920 webcam together with fswebcam
which takes pictures on a 3 seconds interval. The cam is running 24/7
non-stop and all appears to function well.

I was just wondering what the message below means. I sometimes get it,
usually 2-3 time a day, but it does not appear to be fatal as the
webcam just continues working.

uvcvideo: Failed to resubmit video URB (-1)

Can anyone explain what it means? Specifically the -1 as there are
other "codes" I've seen on the Net like -27, -19, -38, but they appear
to be fatal

Thanks

[Grozdan]

Post by Grozdan
Hi,
I'm currently running a Logitech C920 webcam together with fswebcam
which takes pictures on a 3 seconds interval. The cam is running 24/7
non-stop and all appears to function well.
I was just wondering what the message below means. I sometimes get it,
usually 2-3 time a day, but it does not appear to be fatal as the
webcam just continues working.
uvcvideo: Failed to resubmit video URB (-1)
Can anyone explain what it means? Specifically the -1 as there are
other "codes" I've seen on the Net like -27, -19, -38, but they appear
to be fatal
Thanks
--
Yours truly

Ping?

[Oleksij Rempel]

Hi,

Post by Grozdan
Hi,
I'm currently running a Logitech C920 webcam together with fswebcam
which takes pictures on a 3 seconds interval. The cam is running 24/7
non-stop and all appears to function well.
I was just wondering what the message below means. I sometimes get it,
usually 2-3 time a day, but it does not appear to be fatal as the
webcam just continues working.
uvcvideo: Failed to resubmit video URB (-1)
Can anyone explain what it means? Specifically the -1 as there are
other "codes" I've seen on the Net like -27, -19, -38, but they appear
to be fatal

-1 = -EPERM

linux/Documentation/usb/URB.txt:
"To cancel an URB synchronously, call

void usb_kill_urb(struct urb *urb)

It does everything usb_unlink_urb does, and in addition it waits
until after the URB has been returned and the completion handler
has finished. It also marks the URB as temporarily unusable, so
that if the completion handler or anyone else tries to resubmit it
they will get a -EPERM error. Thus you can be sure that when
usb_kill_urb() returns, the URB is totally idle."