From: Sander Eikelenboom <linux@eikelenboom.it>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Pete Eberlein <pete@sensoray.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 22:56:09 +0200 [thread overview]
Message-ID: <1718769257.20100811225609@eikelenboom.it> (raw)
In-Reply-To: <AANLkTin7JxN81tpM+=rmN6jjnOBkd6c+Cy9tx5vruSZ7@mail.gmail.com>
Hello Devin,
Yes i can confirm it was my mistake, with video4linux2 it works.
--
Sander
Wednesday, August 11, 2010, 8:31:56 PM, you wrote:
> On Wed, Aug 11, 2010 at 12:46 PM, Mauro Carvalho Chehab
> <mchehab@infradead.org> wrote:
>> 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.
> I agree with Mauro completely. There is nothing userland should be
> able to do which results in a panic (and I have no reason to believe
> Pete was suggesting otherwise). That said, it's really useful to know
> that this is some sort of v4l1 backward compatibility problem.
> I'll see if I can reproduce this here.
> Thanks,
> Devin
--
Best regards,
Sander mailto:linux@eikelenboom.it
next prev parent reply other threads:[~2010-08-11 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 22:12 Sander Eikelenboom
2010-08-10 22:45 ` Devin Heitmueller
2010-08-10 22:57 ` Sander Eikelenboom
2010-08-11 2:33 ` Devin Heitmueller
2010-08-11 7:25 ` Sander Eikelenboom
2010-08-11 15:58 ` Pete Eberlein
2010-08-11 16:46 ` Mauro Carvalho Chehab
2010-08-11 18:31 ` Devin Heitmueller
2010-08-11 20:56 ` Sander Eikelenboom [this message]
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=1718769257.20100811225609@eikelenboom.it \
--to=linux@eikelenboom.it \
--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=mchehab@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®