Panic on boot with 2.6.18-mm3 on 4-CPU (PIII, 700Mhz) NUMAQ system.
This machine boots fine with 2.6.18-mm1 with an almost identical config
file.
config file, lspci-vvv and complete dmesg attached.
Pls let me know if you need more info.
Suka
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000004
printing eip:
c024e80c
*pde = 00529001
*pte = 00000000
Oops: 0000 [#1]
SMP
last sysfs file:
Modules linked in:
CPU: 0
EIP: 0060:[<c024e80c>] Not tainted VLI
EFLAGS: 00010286 (2.6.18-mm3 #1)
EIP is at pci_call_probe+0x1c/0xe0
eax: 00000000 ebx: dfe63c00 ecx: c10fca90 edx: c048ad60
esi: dfe63c00 edi: 0000000f ebp: dfcacf20 esp: c10ffe70
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, ti=c10fe000 task=c10fca90 task.ti=c10fe000)
Stack: dfe63c00 ffffffed ffffffed dfe63c00 c048b1c0 c024e935 c048b1c0 dfe63c00
c048ad60 c048b1c0 dfe63c00 c048b1f4 c024e97f c048b1c0 dfe63c00 dfe63c48
dfcacf20 c0276069 dfe63c48 00000286 dfff9060 000000d0 c048b1f4 dfcacf20
Call Trace:
[<c024e935>] __pci_device_probe+0x65/0x80
[<c024e97f>] pci_device_probe+0x2f/0x50
[<c0276069>] really_probe+0xf9/0x100
[<c0276158>] driver_probe_device+0xc8/0xe0
[<c03ae79d>] klist_next+0x5d/0xa0
[<c0276210>] __driver_attach+0x0/0xa0
[<c02762a0>] __driver_attach+0x90/0xa0
[<c0275279>] bus_for_each_dev+0x69/0x80
[<c02762d5>] driver_attach+0x25/0x30
[<c0276210>] __driver_attach+0x0/0xa0
[<c0275943>] bus_add_driver+0x73/0x140
[<c024eca4>] __pci_register_driver+0x74/0x90
[<c050c6f9>] tulip_init+0x29/0x30
[<c04f2a62>] do_initcalls+0x42/0x140
[<c01433eb>] register_irq_proc+0xab/0xd0
[<c01003f0>] init+0x0/0x1a0
[<c0143479>] init_irq_proc+0x39/0x50
[<c01003f0>] init+0x0/0x1a0
[<c0100451>] init+0x61/0x1a0
[<c0103c0b>] kernel_thread_helper+0x7/0x1c
=======================
Code: 74 92 eb 8e 8d 74 26 00 8d bc 27 00 00 00 00 57 56 53 83 ec 08 8b 5c 24 1c 89 e0 25 00 e0 ff ff 8b 08 8b 43 10 8b 79 5c 8b 40 44 <8b> 50 04 85 d2 78 11 0f a3 15 c0 9f 4e c0 19 c0 85 c0 0f 85 8c
EIP: [<c024e80c>] pci_call_probe+0x1c/0xe0 SS:ESP 0068:c10ffe70
<0>Kernel panic - not syncing: Attempted to kill init!
On Fri, 2006-10-06 at 16:59 -0700, Sukadev Bhattiprolu wrote:
> Panic on boot with 2.6.18-mm3 on 4-CPU (PIII, 700Mhz) NUMAQ system.
>
> This machine boots fine with 2.6.18-mm1 with an almost identical config
> file.
>
> config file, lspci-vvv and complete dmesg attached.
>
> Pls let me know if you need more info.
It would be really helpful to isolate down where this started happening?
Did it occur in -mm2? mainline 2.6.18?
If you can isolate it to -mm, try a bisection.
-- Dave
On Mon, 2006-10-09 at 08:39 -0700, Dave Hansen wrote:
> On Fri, 2006-10-06 at 16:59 -0700, Sukadev Bhattiprolu wrote:
> > Panic on boot with 2.6.18-mm3 on 4-CPU (PIII, 700Mhz) NUMAQ system.
> >
> > This machine boots fine with 2.6.18-mm1 with an almost identical config
> > file.
> >
> > config file, lspci-vvv and complete dmesg attached.
> >
> > Pls let me know if you need more info.
>
> It would be really helpful to isolate down where this started happening?
> Did it occur in -mm2? mainline 2.6.18?
>
> If you can isolate it to -mm, try a bisection.
Martin reported the same on -mm2.
Thanks,
Badari