From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [Regression 3.1->3.2, bisected] UVC-webcam: kernel panic when starting capturing
Date: Mon, 16 Jul 2012 01:24:55 +0200 [thread overview]
Message-ID: <1649650.cNT61xzOAf@avalon> (raw)
In-Reply-To: <50031C83.7060703@googlemail.com>
Hi Frank,
On Sunday 15 July 2012 21:39:47 Frank Schäfer wrote:
> Am 15.07.2012 14:07, schrieb Laurent Pinchart:
> > On Thursday 12 July 2012 21:07:56 Frank Schäfer wrote:
> >> Hi,
> >>
> >> when I start capturing from the UVC-webcam 2232:1005 ("WebCam
> >> SCB-0385N") of my netbook, I get a kernel panic.
> >> You can find a screenshot of the backtrace here:
> >>
> >> http://imageshack.us/photo/my-images/9/img125km.jpg/
> >>
> >> This is a regression which has been introduced between kernel 3.2-rc2
> >> and 3.2-rc3 with the following commit:
> >>
> >> 3afedb95858bcc117b207a7c0a6767fe891bdfe9 is the first bad commit
> >> commit 3afedb95858bcc117b207a7c0a6767fe891bdfe9
> >> Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >> Date: Thu Nov 3 07:24:34 2011 -0300
> >>
> >> [media] uvcvideo: Don't skip erroneous payloads
> >>
> >> Instead of skipping the payload completely, which would make the
> >> resulting image corrupted anyway, store the payload normally and mark
> >> the buffer as erroneous. If the no_drop module parameter is set to 1
> >> the buffer will then be passed to userspace, and tt will then be up
> >> to the application to decide what to do with the buffer.
> >>
> >> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
> >
> > I'm puzzled. Your screenshot shows the uvc_video_stats_decode() function
> > in the stack trace, but that function wasn't present in
> > 3afedb95858bcc117b207a7c0a6767fe891bdfe9. Could you please send me a stack
> > trace corresponding to 3afedb95858bcc117b207a7c0a6767fe891bdfe9 ?
> >
> > Your stack trace looks similar to the problem reported in
> > https://bugzilla.redhat.com/show_bug.cgi?id=836742.
> > 3afedb95858bcc117b207a7c0a6767fe891bdfe9 might have introduced a different
> > bug, possibly fixed in a later commit.
>
> Hmm... you're right.
> The screenshot I've sent to you was made during the bisection process at
> a commit somewhere between 3.2-rc7 and 3.2-rc8.
> It seems that this one is slightly different from the others.
>
> This one is made at commit 3afedb95858bcc117b207a7c0a6767fe891bdfe9 (the
> first bad commit):
>
> http://imageshack.us/photo/my-images/811/img130hv.jpg
>
> and this one is made at 3.5.rc6+:
>
> http://imageshack.us/photo/my-images/440/img127u.jpg
Thank you. Could you please try the patch I've attached to
https://bugzilla.redhat.com/show_bug.cgi?id=836742 ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-07-15 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 19:07 [Regression 3.1->3.2, bisected] UVC-webcam: kernel panic when starting capturing Frank Schäfer
2012-07-15 12:07 ` Laurent Pinchart
2012-07-15 19:39 ` Frank Schäfer
2012-07-15 23:24 ` Laurent Pinchart [this message]
2012-07-16 13:32 ` Frank Schäfer
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=1649650.cNT61xzOAf@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).