From: Andrew Morton <akpm@osdl.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc2-mm1 - BUG: unable to handle kernel NULL pointer dereference at virtual address 0000003a
Date: Fri, 10 Feb 2006 12:38:48 -0800 [thread overview]
Message-ID: <20060210123848.7cb84eeb.akpm@osdl.org> (raw)
In-Reply-To: <a44ae5cd0602101224l63886192sec85a8771cf77ba9@mail.gmail.com>
Miles Lane <miles.lane@gmail.com> wrote:
>
> BUG: unable to handle kernel NULL pointer dereference at virtual
> address 0000003a
> printing eip:
> 0000003a
> *pde = 00000000
> Oops: 0000 [#1]
> SMP
> last sysfs file: /devices/pci0000:00/0000:00:02.2/usb3/idProduct
> Modules linked in: sr_mod eth1394 snd_mpu401 8250_pnp snd_mpu401_uart
> snd_rawmidi pcspkr ehci_hcd autofs4 vfat
> fat 3c59x mii forcedeth parport_pc parport 8250 serial_core ohci1394
> ieee1394 ohci_hcd uhci_hcd usbcore conta
> iner ide_cd cdrom ide_scsi
> CPU: 0
> EIP: 0060:[<0000003a>] Not tainted VLI
> EFLAGS: 00010286 (2.6.16-rc2-mm1 #9)
> EIP is at 0x3a
> eax: ffffff85 ebx: 00000000 ecx: 00000000 edx: 00000020
> esi: 00020070 edi: 12000000 ebp: 00000000 esp: f6b60c70
> ds: 007b es: 007b ss: 0068
> Process cdrom_id (pid: 3482, threadinfo=f6b60000 task=f6b6f6f0)
> Stack: <0>00000000 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> 00000000 00000000 00000000 00000000 00000043 00000000 0000400c c04aaca4
> 0000000c ffffff85 00000000 00000002 00000001 00007530 00000000 f64006ac
> Call Trace:
> <c01038b9> show_stack_log_lvl+0xaa/0xb5 <c01039fd> show_registers+0x139/0x1a5
> <c0103cf6> die+0x162/0x1ef <c01120e6> do_page_fault+0x389/0x4cc
> <c01032bf> error_code+0x4f/0x54
> Code: Bad EIP value.
> BUG: cdrom_id/3482, lock held at task exit time!
> [dfca557c] {init_once}
> .. held by: cdrom_id: 3482 [f6b6f6f0, 123]
> ... acquired at: do_open+0x61/0x2f0
gack, what a mess. At a guess, I'd say that block_dev.c:do_open() found a
stupid value in disk->fops->open and did an indirect jump to it.
What is `cdrom_id'?
Can you describe what was happening at the time? What does your cdrom
setup look like, which cdrom drivers were loaded at the time, etc?
It might help if you could change the value of CONFIG_FRAME_POINTER, try
again, see if we can get a better backtrace.
Also, try disabling cdrom_id (mv cdrom_id cdrom_id~), then when the machine
is booted, run `strace cdrom_id'. But one would need to work out which
arguments were begin passed to cdrom_id.
prev parent reply other threads:[~2006-02-10 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 20:24 Miles Lane
2006-02-10 20:38 ` Andrew Morton [this message]
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=20060210123848.7cb84eeb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.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®