From: Andrew Morton <akpm@osdl.org>
To: Mike Galbraith <efault@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: 2.6.18-rc3-mm2: oops in device_bind_driver()
Date: Sat, 12 Aug 2006 18:02:56 -0700 [thread overview]
Message-ID: <20060812180256.445caea9.akpm@osdl.org> (raw)
In-Reply-To: <1155385726.6151.6.camel@Homer.simpson.net>
On Sat, 12 Aug 2006 12:28:46 +0000
Mike Galbraith <efault@gmx.de> wrote:
> Greetings,
>
> I'm hitting the oops below, though not on every boot.
>
> DEV: registering device: ID = 'dvb0'
> PM: Adding info for bttv-sub:dvb0
> saa7130/34: v4l2 driver version 0.2.14 loaded
> bus bttv-sub: add device dvb0
> bttv0: add subdevice "dvb0"
> BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing eip:
> c126e43f
> *pde = 00000000
> Oops: 0000 [#1]
> 4K_STACKS PREEMPT SMP
> last sysfs file: /class/input/input2/name
> Modules linked in: saa7134 bt878 ir_kbd_i2c bttv video_buf ir_common sd_mod i2c_i801 btcx_risc snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm tveeprom ohci1394 snd_timer snd_page_alloc prism54 snd_mpu401 ieee1394 snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore
> CPU: 1
> EIP: 0060:[<c126e43f>] Not tainted VLI
> EFLAGS: 00010246 (2.6.18-rc3-mm2-smp #169)
> EIP is at device_bind_driver+0x49/0xd0
> eax: 00000000 ebx: c1fdb048 ecx: f8b4e268 edx: 00000000
> esi: c1fdb084 edi: f8b46db8 ebp: dfccef98 esp: dfccef80
> ds: 007b es: 007b ss: 0068
> Process probe-0000:02:0 (pid: 3623, ti=dfcce000 task=dff57030 task.ti=dfcce000)
> Stack: f8b46d80 dfccef98 c11de322 c1fdb048 00000000 f8b46db8 dfccefc4 c126e56d
> c146e438 c145210e f8b3c243 c1fdb114 c1fdb114 c1fa3740 fffffffc dfccbe8c
> c1fa3740 dfccefe4 c10361d6 c126e4c6 ffffffff ffffffff c10360f2 00000000
> Call Trace:
> [<c126e56d>] really_probe+0xa7/0x10c
> [<c10361d6>] kthread+0xe4/0xe8
> [<c1001005>] kernel_thread_helper+0x5/0xb
> DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb
> Leftover inexact backtrace:
> [<c1003f83>] show_stack_log_lvl+0xa6/0xcb
> [<c1004180>] show_registers+0x1d8/0x286
> [<c100437f>] die+0x151/0x333
> [<c10197f9>] do_page_fault+0x26b/0x51f
> [<c13e02c9>] error_code+0x39/0x40
> [<c126e56d>] really_probe+0xa7/0x10c
> [<c10361d6>] kthread+0xe4/0xe8
> [<c1001005>] kernel_thread_helper+0x5/0xb
> Code: 00 89 44 24 08 c7 44 24 04 ac 53 40 c1 c7 04 24 f0 e3 46 c1 e8 38 4b db ff 31 f6 89 f0 83 c4 0c 5b 5e 5f 5d c3 8b 83 14 01 00 00 <8b> 00 89 44 24 08 8d 83 cc 00 00 00 89 44 24 04 c7 04 24 10 e4
> EIP: [<c126e43f>] device_bind_driver+0x49/0xd0 SS:ESP 0068:dfccef80
I'd assume that you have CONFIG_PCI_MULTITHREAD_PROBE set, and
gregkh-driver-driver-multithread.patch and
gregkh-driver-pci-multithreaded-probe.patch have found a DVB race.
next prev parent reply other threads:[~2006-08-13 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 12:28 2.6.18-rc3-mm2: oops in device_bind_driver() Mike Galbraith
2006-08-13 1:02 ` Andrew Morton [this message]
2006-08-13 5:50 ` Mike Galbraith
2006-08-14 21:03 ` Greg KH
2006-08-14 21:28 ` Mauro Carvalho Chehab
2006-08-14 23:52 ` Greg KH
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=20060812180256.445caea9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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