From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Pete Eberlein <pete@sensoray.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
mrechberger@gmail.com, gregkh@suse.de,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [2.6.35] usb 2.0 em28xx kernel panic general protection fault: 0000 [#1] SMP RIP: 0010:[<ffffffffa004fbc5>] [<ffffffffa004fbc5>] em28xx_isoc_copy_vbi+0x62e/0x812 [em28xx]
Date: Wed, 11 Aug 2010 13:46:38 -0300 [thread overview]
Message-ID: <4C62D3EE.5000907@infradead.org> (raw)
In-Reply-To: <1281542325.2360.86.camel@pete-desktop>
Em 11-08-2010 12:58, Pete Eberlein escreveu:
> On Wed, 2010-08-11 at 09:25 +0200, Sander Eikelenboom wrote:
>> Hello Devin,
>>
>> Yes it's completely reproducible for a change:
>>
>> ffmpeg -f video4linux -r 25 -s 720x576 -i /dev/video0 out.flv
>> gave an error:
>
> Use -f video4linux2.
>
> The -f video4linux option uses the old video4linux1 API. I have seen
> similar strange behavior when I used that ffmpeg option with a v4l2
> driver I am developing. Also, ffmpeg does not use libv4l.
Still, we have a bug to fix. The driver shouldn't generating a PANIC if accessed
via V4L1 API.
Cheers,
Mauro.
next prev parent reply other threads:[~2010-08-11 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 22:12 [2.6.35] usb 2.0 em28xx kernel panic general protection fault: 0000 [#1] SMP RIP: 0010:[<ffffffffa004fbc5>] [<ffffffffa004fbc5>] em28xx_isoc_copy_vbi+0x62e/0x812 [em28xx] Sander Eikelenboom
2010-08-10 22:45 ` Devin Heitmueller
2010-08-10 22:45 ` Devin Heitmueller
2010-08-10 22:57 ` Sander Eikelenboom
2010-08-11 2:33 ` Devin Heitmueller
2010-08-11 2:33 ` Devin Heitmueller
2010-08-11 7:25 ` Sander Eikelenboom
2010-08-11 15:58 ` Pete Eberlein
2010-08-11 15:58 ` Pete Eberlein
2010-08-11 16:46 ` Mauro Carvalho Chehab [this message]
2010-08-11 18:31 ` Devin Heitmueller
2010-08-11 18:31 ` Devin Heitmueller
2010-08-11 20:56 ` Sander Eikelenboom
2010-08-11 23:04 ` Andy Walls
2010-08-11 23:04 ` Andy Walls
2010-08-17 18:11 ` Maciej Rutecki
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=4C62D3EE.5000907@infradead.org \
--to=mchehab@infradead.org \
--cc=dheitmueller@kernellabs.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=mrechberger@gmail.com \
--cc=pete@sensoray.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.