From: Anisse Astier <anisse@astier.eu>
To: linux-uvc-devel@lists.sourceforge.net,
linux-media@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: UVCvideo: Failed to resubmit video URB (-27) with Linux 3.3.3
Date: Thu, 26 Apr 2012 20:07:21 +0200 [thread overview]
Message-ID: <20120426200721.0c3ca642@destiny.ordissimo> (raw)
[-- Attachment #1: Type: text/plain, Size: 2262 bytes --]
Hi,
I'm experiencing a problem with uvcvideo with kernel 3.3.3 and today's
Linus' tree.
Problem not reproduced in 3.2.15, so this could be labelled as a regression.
See webcam lsusb and (verbose!) dmesg log in attachment, which exhibits
the problem.
We see lots of error (-18 = -EXDEV), that indicate that URB was too late
and then dropped, and they add up until we reach the "Failed to resubmit
video URB" scheduling issue.
Installed libv4l version is 0.8.6.
I'm reproducing this with: gst-launch-0.10 --verbose v4l2src ! xvimagesink
(Skype exhibits the problem too, while it isn't using gstreamer, so it
really seems to come from kernel. Also, doesn't happen with 3.2)
This is the first part of the problem. The second part is that if I
restart the webcam with gst-launch after the first failure, I have a
total freeze, just after these messages in the log (fetched with
netconsole, I wasn't able to get a panic trace):
[ 191.796217] uvcvideo: Marking buffer as bad (error bit set).
[ 191.796233] uvcvideo: Marking buffer as bad (error bit set).
[ 191.796244] uvcvideo: Marking buffer as bad (error bit set).
[ 191.796252] uvcvideo: Marking buffer as bad (error bit set).
[ 191.796259] uvcvideo: Frame complete (EOF found).
[ 191.796265] uvcvideo: EOF in empty payload.
[ 192.972803] uvcvideo: Marking buffer as bad (error bit set).
[ 192.972818] uvcvideo: Dropping payload (out of sync).
[ 194.289463] uvcvideo: Marking buffer as bad (error bit set).
[ 194.289478] uvcvideo: Frame complete (FID bit toggled).
[ 194.289486] uvcvideo: Marking buffer as bad (error bit set).
[ 194.289493] uvcvideo: Frame complete (FID bit toggled).
[ 194.289499] uvcvideo: Marking buffer as bad (error bit set).
[ 194.289505] uvcvideo: Frame complete (FID bit toggled).
[ 194.289511] uvcvideo: Marking buffer as bad (error bit set).
[ 194.289518] uvcvideo: Frame complete (FID bit toggled).
[ 194.289524] uvcvideo: Marking buffer as bad (error bit set).
[ 194.289531] uvcvideo: Frame complete (FID bit toggled).
Last but not least, uvcvideo is un-bisectable because there were a few
crash-fixes during the 3.3 development cycle. I started bisecting and got
kernel panics.
Regards,
--
Anisse
[-- Attachment #2: log-uvc-crash.gz --]
[-- Type: application/x-gzip, Size: 31508 bytes --]
[-- Attachment #3: lsusb.txt.gz --]
[-- Type: application/x-gzip, Size: 2235 bytes --]
next reply other threads:[~2012-04-26 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 18:07 Anisse Astier [this message]
2012-05-02 12:24 ` UVCvideo: Failed to resubmit video URB (-27) with Linux 3.3.3 Laurent Pinchart
2012-05-03 14:34 ` Anisse Astier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120426200721.0c3ca642@destiny.ordissimo \
--to=anisse@astier.eu \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-uvc-devel@lists.sourceforge.net \
--cc=mchehab@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.