From: Ricardo Cerqueira <rmcc@linuxtv.org>
To: Brian Marete <bgmarete@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.15-rc1
Date: Thu, 24 Nov 2005 16:56:53 +0000 [thread overview]
Message-ID: <1132851413.3229.12.camel@frolic> (raw)
In-Reply-To: <6dd519ae0511240209y712549bep6ba626134bb6f502@mail.gmail.com>
Hello;
On Thu, 2005-11-24 at 10:09 +0000, Brian Marete wrote:
[snip]
> saa7130[0]: option to override the default value.
> Unable to handle kernel NULL pointer dereference at virtual address 000006d0
> printing eip:
> c0299163
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> Modules linked in: saa7134 video_buf v4l2_common v4l1_compat ir_common
> videodev via_agp agpgart snd_via82xx snd_ac97_codec snd_ac97_bus
> snd_mpu401_uart snd_rawmidi snd_seq_device snd_rtctimer snd_pcm_oss
> snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore video fan
> button thermal processor via_rhine fuse md5 ipv6 loop rtc pcspkr
> ide_cd cdrom dm_mod
> CPU: 0
> EIP: 0060:[<c0299163>] Not tainted VLI
> EFLAGS: 00010296 (2.6.15-rc1)
> EIP is at input_register_device+0x9/0x180
This is due to a bug that's already been identified in v4l's input
support, caused by recent changes in the kernel's own input layer. A
patch has been proposed at the v4l list but it hasn't been tested yet.
A good way to skip this for now is to add "options saa7134 disable_ir=1"
to you modprobe.conf.
Be aware that v4l @ rc1 has other problems related to kernel VMA changes
that render video-buf unusable, and have been fixed after the release of
rc1. You may want to try the latest -mm.
--
RC
next prev parent reply other threads:[~2005-11-24 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 10:09 Oops in 2.6.15-rc1 Brian Marete
2005-11-24 11:32 ` Lee Revell
2005-11-24 16:56 ` Ricardo Cerqueira [this message]
2005-11-24 18:26 ` Dmitry Torokhov
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=1132851413.3229.12.camel@frolic \
--to=rmcc@linuxtv.org \
--cc=bgmarete@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
/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.