Messages in this thread | | | Date | Mon, 9 Jan 2006 15:41:27 -0800 | From | Andrew Morton <> | Subject | Re: Problems with 2.6.15-mm1 and mm2. |
| |
Martin Bligh <mbligh@google.com> wrote: > > 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 >
Yes, I asked Greg about that - we don't know what's causing it yet. I have a bad feeling that this bug will go into Linus's tree if we don't fix it quick.
I had problems with gregkh-pci-x86-pci-domain-support-the-meat.patch. It might be worth reverting that.
> > 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? >
I'm not aware of any buggy x86_64 patches in -mm2 :(
I guess you don't have the time to sit down and do a bisection search. It'd take a solid few hours... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |