From: Martin Bligh <mbligh@google.com>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Problems with 2.6.15-mm1 and mm2.
Date: Mon, 09 Jan 2006 09:59:43 -0800 [thread overview]
Message-ID: <43C2A48F.6030407@google.com> (raw)
OK, so on -mm1 we get:
Unable to handle kernel NULL pointer dereference at virtual address 00000004
printing eip:
c01fccd2
*pde = 0042d001
*pte = 00000000
Oops: 0000 [#1]
SMP
last sysfs file:
Modules linked in:
CPU: 0
EIP: 0060:[<c01fccd2>] Not tainted VLI
EFLAGS: 00010286 (2.6.15-mm1-autokern1)
EIP is at pci_call_probe+0x1a/0xa1
eax: 00000000 ebx: ffffffed ecx: e748a030 edx: c03a4680
esi: e7767800 edi: c03a4680 ebp: ffffffff esp: e749fef0
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=e749e000 task=e748a030)
Stack: <0>ffffffed e7767800 c03a4680 c03a46ac c01fcd8c c03a4680 e7767800
c03a441c
<0>c03a4680 e7767800 c03a46ac c01fcdbf c03a4680 e7767800
e7767800 00000000
<0>e7767848 c021c265 e7767848 e7767848 00000000 c021c311
c021c34a c03a46ac
Call Trace:
[<c01fcd8c>] __pci_device_probe+0x33/0x47
[<c01fcdbf>] pci_device_probe+0x1f/0x34
[<c021c265>] driver_probe_device+0x3a/0x84
[<c021c311>] __driver_attach+0x0/0x60
[<c021c34a>] __driver_attach+0x39/0x60
[<c021ba18>] bus_for_each_dev+0x47/0x6d
[<c01f4d5a>] kobject_add+0x76/0x95
[<c021c385>] driver_attach+0x14/0x18
[<c021c311>] __driver_attach+0x0/0x60
[<c021be30>] bus_add_driver+0x54/0x87
[<c021c72c>] driver_register+0x3b/0x3e
[<c01fcfa6>] __pci_register_driver+0x7e/0x8c
[<c03f646d>] qla1280_init+0xc/0xf
[<c03e4789>] do_initcalls+0x4b/0x99
[<c0100393>] init+0x98/0x195
[<c01002fb>] init+0x0/0x195
[<c0100ea9>] kernel_thread_helper+0x5/0xb
from the NUMA-Q. http://test.kernel.org/19793/debug/console.log
------------------------------------------------------------------
on -mm2 I get the x86_64 seems to lock up (NFI why ... looking at it),
the NUMA-Q and x440 panic (very similar to the above).
I think Andy figured out what was causing those panics. Can we drop
those patches until they're fixed?
Thanks,
M.
next reply other threads:[~2006-01-09 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 17:59 Martin Bligh [this message]
2006-01-09 23:41 ` Andrew Morton
2006-01-10 0:05 ` Martin Bligh
2006-01-10 0:46 ` Andrew Morton
2006-01-10 0:50 ` Martin Bligh
2006-01-10 14:52 ` Andy Whitcroft
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=43C2A48F.6030407@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome