linux-kernel - Re: [2.6.35] usb 2.0 em28xx kernel panic general protection fault: 0000 [#1] SMP RIP: 0010:[<ffffffffa004fbc5>] [<ffffffffa004fbc5>] em28xx_isoc_copy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C62D3EE.5000907@infradead.org>
Date:	Wed, 11 Aug 2010 13:46:38 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Pete Eberlein <pete@...soray.com>
CC:	Sander Eikelenboom <linux@...elenboom.it>,
	Devin Heitmueller <dheitmueller@...nellabs.com>,
	mrechberger@...il.com, gregkh@...e.de,
	linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
	linux-usb@...r.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]

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/