From: Hans de Goede <hdegoede@redhat.com>
To: Frank Dierich <frank.dierich@googlemail.com>
Cc: linux-usb <linux-usb@vger.kernel.org>,
linux-media@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [Bug] 0ac8:0321 Vimicro generic vc0321 Camera is not working and causes crashes since 3.2
Date: Wed, 18 Sep 2013 15:55:02 +0200 [thread overview]
Message-ID: <5239B0B6.9070605@redhat.com> (raw)
In-Reply-To: <52389E8E.3050202@googlemail.com>
Hi,
On 09/17/2013 08:25 PM, Frank Dierich wrote:
>> On 09/09/2013 02:09 PM, Hans de Goede wrote:
>>> Thanks for the bug report, looking at the bug reports, they all report an error of -71 which is
>>> EPROTO, which typically means something is wrong at the USB level.
>>>
>>> And nothing has changed for the driver in question between 3.1 and 3.2 , so I believe this regression
>>> is caused by changes to the usb sub-system, likely changes to the EHCI driver.
> I have tested the new 3.12.0-rc1 kernel and the regression is still present. It causes that Cheese crashes with a segmentation fault and I get the following errors
>
> [ 139.868628] gspca_main: ISOC data error: [21] len=0, status=-71
> [ 139.904620] gspca_main: ISOC data error: [12] len=0, status=-71
> [ 139.936595] gspca_main: ISOC data error: [9] len=0, status=-71
> [ 139.968576] gspca_main: ISOC data error: [17] len=0, status=-71
> [ 140.036571] gspca_main: ISOC data error: [16] len=0, status=-71
> [ 140.037364] video_source:sr[2570]: segfault at 8 ip 00007f0430d6868c sp 00007f0406c02900 error 4 in libgstreamer-0.10.so.0.30.0[7f0430d15000+de000]
> [ 140.068533] gspca_main: ISOC data error: [24] len=0, status=-71
> [ 140.104519] gspca_main: ISOC data error: [15] len=0, status=-71
> [ 140.168474] gspca_main: ISOC data error: [20] len=0, status=-71
> [ 140.200461] gspca_main: ISOC data error: [28] len=0, status=-71
Note I'm not claiming there is not problem, but since your testing indicated
that things broken between 3.1 and 3.2, I'm pretty sure that the breakage
is not caused by changes to the vimicro driver, as that driver was not
changed between 3.1 and 3.2.
As I already said in my previous mail, the best way forward with this is probably
to bisect the problem, and then send a mail to linux-usb@vger.kernel.org about this.
Please CC me on this mail.
Regards,
Hans
prev parent reply other threads:[~2013-09-18 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 11:37 [Bug] 0ac8:0321 Vimicro generic vc0321 Camera is not working and causes crashes since 3.2 Frank Dierich
2013-09-09 12:09 ` Hans de Goede
[not found] ` <522F6378.8000808@googlemail.com>
2013-09-17 18:25 ` Frank Dierich
2013-09-18 13:55 ` Hans de Goede [this message]
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=5239B0B6.9070605@redhat.com \
--to=hdegoede@redhat.com \
--cc=frank.dierich@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@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).