2.6.12-rc1 panic on startup (acpi_
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startup
Here is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=view
2.6.16-rc1 panic on startup (acpi)
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 5 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startupHere is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=view
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 12 lines · Neal Becker
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 5 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startupHere is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=view
It died in pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?
Neal, booting with `vga=extended' or similar will help prevent the oops from scrolling off the display.
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 9 lines · Andrew Morton
Quoted 8 lines · Neal Becker
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 3 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startup
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Here is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=viewIt died in
pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?
Yes. Can you try 2.6.16-rc2? Is this a x86-64 machine?
thanks,
greg k-h
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 10 lines · Greg Kroah-Hartman
Quoted 9 lines · Andrew Morton
Quoted 8 lines · Neal Becker
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 3 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startup
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Here is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=viewIt died in
pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?Yes. Can you try 2.6.16-rc2? Is this a x86-64 machine?
I can hit this on my dv8000 too. It's still there in 2.6.12-rc2-git3 I'm building a kernel with Randy's 'pause after printk' patch right now to catch the top of the oops. It's enormous. Even with a 50 line display, and x86-64s dual-line backtrace, it scrolls off the top.
Dave
Re: 2.6.16-rc1 panic on startup (acpi)
In reply to Greg KHQuoted 12 lines · Greg KH
Quoted 11 lines · Andrew Morton
Quoted 9 lines · Neal Becker
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 6 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startupHere is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=
view
Quoted 7 lines
Quoted 2 lines
It died in
pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?Yes. Can you try 2.6.16-rc2? Is this a x86-64 machine?
thanks,
This is 2.6.16-rc2. Yes, this is an x86-64. I have a new picture, I put here:
Re: 2.6.16-rc1 panic on startup (acpi)
In reply to Dave JonesQuoted 16 lines · Dave Jones
Quoted 15 lines · Greg Kroah-Hartman
Quoted 14 lines · Andrew Morton
Quoted 12 lines · Neal Becker
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 5 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startupHere is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=view
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
It died in
pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?Yes. Can you try 2.6.16-rc2? Is this a x86-64 machine?
I can hit this on my dv8000 too. It's still there in 2.6.12-rc2-git3 I'm building a kernel with Randy's 'pause after printk' patch right now to catch the top of the oops. It's enormous. Even with a 50 line display, and x86-64s dual-line backtrace, it scrolls off the top.
Just be patient. A boot can take a few minutes... ;)
Signature · 1 line
~Randy
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 20 lines · Randy.Dunlap
Quoted 18 lines · Dave Jones
Quoted 17 lines · Greg Kroah-Hartman
Quoted 15 lines · Andrew Morton
Quoted 12 lines · Neal Becker
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 5 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startupHere is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=viewIt died in
pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
Yes. Can you try 2.6.16-rc2? Is this a x86-64 machine?
I can hit this on my dv8000 too. It's still there in 2.6.12-rc2-git3 I'm building a kernel with Randy's 'pause after printk' patch right now to catch the top of the oops. It's enormous. Even with a 50 line display, and x86-64s dual-line backtrace, it scrolls off the top.
Just be patient. A boot can take a few minutes... ;)
It doesn't get that far. What did bugger things up though was the NMI watchdog kicking in. I've thrown a touch_nmi_watchdog in the delay, and kicked off another build hoping for a cleaner dump.
In the meantime, here's what I got..
http://people.redhat.com/davej/DSC00148.JPG
Dave
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 30 lines · Dave Jones
Quoted 20 lines · Randy.Dunlap
Quoted 18 lines · Dave Jones
Quoted 17 lines · Greg Kroah-Hartman
Quoted 15 lines · Andrew Morton
Quoted 12 lines · Neal Becker
Sorry, I meant 2.6.16-rc1 (not 2.6.12)
Quoted 5 lines · Neal Becker
HP dv8000 notebook
2.6.15 is fine, but 2.6.12-rc1 panics immediately on startupHere is a picture of some traceback
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=124152&action=viewIt died in
pci_mmcfg_read(). Greg, didn't a crash in there get fixed recently?Quoted 8 lines
Quoted 6 lines
Quoted 1 line
Yes. Can you try 2.6.16-rc2? Is this a x86-64 machine?
I can hit this on my dv8000 too. It's still there in 2.6.12-rc2-git3 I'm building a kernel with Randy's 'pause after printk' patch right now to catch the top of the oops. It's enormous. Even with a 50 line display, and x86-64s dual-line backtrace, it scrolls off the top.
Just be patient. A boot can take a few minutes... ;)
Quoted 7 lines
It doesn't get that far. What did bugger things up though was the NMI watchdog kicking in. I've thrown a
touch_nmi_watchdogin the delay, and kicked off another build hoping for a cleaner dump.In the meantime, here's what I got..
Andi, didn't your change for this function make it into Linus's tree?
thanks,
greg k-h
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 5 lines · Greg KH
Quoted 3 lines
In the meantime, here's what I got..
Andi, didn't your change for this function make it into Linus's tree?
Yes
Workaround is pci=nommconf btw
-Andi
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 7 lines · Andi Kleen
Quoted 5 lines · Greg KH
Quoted 3 lines
In the meantime, here's what I got..
Andi, didn't your change for this function make it into Linus's tree?
Quoted 8 lines
Yes
See
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm
it;h=1de6bf33bc4601d856c286ad5c7d515468e24bbbWorkaround is pci=nommconf btw
Yes! This patch worked.
Re: 2.6.16-rc1 panic on startup (acpi)
In reply to Andi KleenQuoted 6 lines · Andi Kleen
Quoted 4 lines · Greg KH
Quoted 3 lines
In the meantime, here's what I got..
Quoted 8 lines
Quoted 1 line
Andi, didn't your change for this function make it into Linus's tree?
Yes
Workaround is pci=nommconf btw
I'm puzzled. I'm still seeing this crash with latest -git which has this patch (I just double checked the source I built). The pci=nommconf workaround does indeed work though.
Dave
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 4 lines · Dave Jones
Quoted 1 line
Workaround is pci=nommconf btw
I'm puzzled. I'm still seeing this crash with latest -git which has this patch (I just double checked the source I built).
That's surprising. Can you addr2line the exactly address it's crashing on?
-Andi
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 5 lines · Andi Kleen
Quoted 3 lines
Quoted 1 line
Workaround is pci=nommconf btw
I'm puzzled. I'm still seeing this crash with latest -git which has this patch (I just double checked the source I built).
That's surprising. Can you addr2line the exactly address it's crashing on?
Still there in todays git snapshot.
http://people.redhat.com/davej/dsc00150.jpg is the top of the oops.
Full traceback isacpi_os_derive_pci_id_2acpi_os_derive_pci_idacpi_ev_pci_config_region_setupacpi_os_acquire_objectacpi_ev_pci_config_region_setupacpi_ev_address_space_dispatchcache_alloc_debugcheck_afteracpi_ex_access_regionacpi_ex_field_datum_ioacpi_os_acquire_ojbectacpi_ex_extract_from_fieldacpi_ut_create_internal_objectacpi_ex_read_data_from_fieldacpi_ex_resolve_node_to_valueacpi_ds_init_object_from_opacpi_ex_resolve_to_valueacpi_ex_resolve_operandsacpi_ds_exec_end_opacpi_ps_parse_loopacpi_ps_parse_amlacpi_ps_execute_passacpi_ps_execute_methodacpi_ns_evaluate_by_handleacpi_ns_evaluate_realativeacpi_ut_evalute_objectacpi_ut_execute_STAacpi_ut_release_mutexacpi_ns_get_device_callback
vsscanfacpi_os_wait_semaphoreacpi_ns_get_device_callbackacpi_ns_walk_namespaceacpi_get_devicesfind_pci_rootbridgeacpi_get_pci_rootbridge_handlepci_acpi_find_root_bridgeacpi_platform_notifydevice_addpci_create_buspci_scan_bus_parentedpci_acpi_scan_rootacpi_pci_root_addacpi_bus_driver_initacpi_add_single_objectacpi_bus_scanacpi_scan_initacpi_event_init
init
Here's pci_mm_cfg from that kernel..
d+0>: push %r15
0xffffffff802d6e36 <pci_mmcfg_read+2>: push %r14 0xffffffff802d6e38 <pci_mmcfg_read+4>: push %r13 0xffffffff802d6e3a <pci_mmcfg_read+6>: push %r12 0xffffffff802d6e3c <pci_mmcfg_read+8>: push %rbp 0xffffffff802d6e3d <pci_mmcfg_read+9>: push %rbx 0xffffffff802d6e3e <pci_mmcfg_read+10>: sub $0x8,%rsp 0xffffffff802d6e42 <pci_mmcfg_read+14>: mov %edi,%r15d 0xffffffff802d6e45 <pci_mmcfg_read+17>: mov %esi,%r14d 0xffffffff802d6e48 <pci_mmcfg_read+20>: mov %edx,%r12d 0xffffffff802d6e4b <pci_mmcfg_read+23>: mov %ecx,%ebp 0xffffffff802d6e4d <pci_mmcfg_read+25>: mov %r8d,%ebx 0xffffffff802d6e50 <pci_mmcfg_read+28>: mov %r9,%r13 0xffffffff802d6e53 <pci_mmcfg_read+31>: test %r9,%r9 0xffffffff802d6e56 <pci_mmcfg_read+34>: je 0xffffffff802d6e70 <pci_mmcfg_read+60> 0xffffffff802d6e58 <pci_mmcfg_read+36>: cmp $0xff,%esi 0xffffffff802d6e5e <pci_mmcfg_read+42>: ja 0xffffffff802d6e70 <pci_mmcfg_read+60> 0xffffffff802d6e60 <pci_mmcfg_read+44>: cmp $0xff,%edx 0xffffffff802d6e66 <pci_mmcfg_read+50>: ja 0xffffffff802d6e70 <pci_mmcfg_read+60> 0xffffffff802d6e68 <pci_mmcfg_read+52>: cmp $0xfff,%ecx 0xffffffff802d6e6e <pci_mmcfg_read+58>: jle 0xffffffff802d6e77 <pci_mmcfg_read+67> 0xffffffff802d6e70 <pci_mmcfg_read+60>: mov $0xffffffea,%eax 0xffffffff802d6e75 <pci_mmcfg_read+65>: jmp 0xffffffff802d6edf <pci_mmcfg_read+171> 0xffffffff802d6e77 <pci_mmcfg_read+67>: callq 0xffffffff802d6cf0 <pci_dev_base> 0xffffffff802d6e7c <pci_mmcfg_read+72>: mov %rax,%rdx 0xffffffff802d6e7f <pci_mmcfg_read+75>: test %rax,%rax 0xffffffff802d6e82 <pci_mmcfg_read+78>: jne 0xffffffff802d6ea5 <pci_mmcfg_read+113> 0xffffffff802d6e84 <pci_mmcfg_read+80>: mov %r13,%r9 0xffffffff802d6e87 <pci_mmcfg_read+83>: mov %ebx,%r8d 0xffffffff802d6e8a <pci_mmcfg_read+86>: mov %ebp,%ecx 0xffffffff802d6e8c <pci_mmcfg_read+88>: mov %r12d,%edx 0xffffffff802d6e8f <pci_mmcfg_read+91>: mov %r14d,%esi 0xffffffff802d6e92 <pci_mmcfg_read+94>: mov %r15d,%edi 0xffffffff802d6e95 <pci_mmcfg_read+97>: pop %rbx 0xffffffff802d6e96 <pci_mmcfg_read+98>: pop %rbx 0xffffffff802d6e97 <pci_mmcfg_read+99>: pop %rbp 0xffffffff802d6e98 <pci_mmcfg_read+100>: pop %r12 0xffffffff802d6e9a <pci_mmcfg_read+102>: pop %r13 0xffffffff802d6e9c <pci_mmcfg_read+104>: pop %r14 0xffffffff802d6e9e <pci_mmcfg_read+106>: pop %r15 0xffffffff802d6ea0 <pci_mmcfg_read+108>: jmpq 0xffffffff802d56a1 <pci_conf1_read> 0xffffffff802d6ea5 <pci_mmcfg_read+113>: cmp $0x2,%ebx 0xffffffff802d6ea8 <pci_mmcfg_read+116>: je 0xffffffff802d6ec1 <pci_mmcfg_read+141> 0xffffffff802d6eaa <pci_mmcfg_read+118>: cmp $0x4,%ebx 0xffffffff802d6ead <pci_mmcfg_read+121>: je 0xffffffff802d6ed0 <pci_mmcfg_read+156> 0xffffffff802d6eaf <pci_mmcfg_read+123>: dec %ebx 0xffffffff802d6eb1 <pci_mmcfg_read+125>: jne 0xffffffff802d6edd <pci_mmcfg_read+169> 0xffffffff802d6eb3 <pci_mmcfg_read+127>: movslq %ebp,%rax 0xffffffff802d6eb6 <pci_mmcfg_read+130>: lea (%rdx,%rax,1),%rax 0xffffffff802d6eba <pci_mmcfg_read+134>: mov (%rax),%al
We blew up here ^^^
0xffffffff802d6ebc <pci_mmcfg_read+136>: movzbl %al,%eax 0xffffffff802d6ebf <pci_mmcfg_read+139>: jmp 0xffffffff802d6ed9 <pci_mmcfg_read+165> 0xffffffff802d6ec1 <pci_mmcfg_read+141>: movslq %ebp,%rax 0xffffffff802d6ec4 <pci_mmcfg_read+144>: lea (%rdx,%rax,1),%rax 0xffffffff802d6ec8 <pci_mmcfg_read+148>: mov (%rax),%ax 0xffffffff802d6ecb <pci_mmcfg_read+151>: movzwl %ax,%eax 0xffffffff802d6ece <pci_mmcfg_read+154>: jmp 0xffffffff802d6ed9 <pci_mmcfg_read+165> 0xffffffff802d6ed0 <pci_mmcfg_read+156>: movslq %ebp,%rax 0xffffffff802d6ed3 <pci_mmcfg_read+159>: lea (%rdx,%rax,1),%rax 0xffffffff802d6ed7 <pci_mmcfg_read+163>: mov (%rax),%eax 0xffffffff802d6ed9 <pci_mmcfg_read+165>: mov %eax,0x0(%r13) 0xffffffff802d6edd <pci_mmcfg_read+169>: xor %eax,%eax 0xffffffff802d6edf <pci_mmcfg_read+171>: pop %r11 0xffffffff802d6ee1 <pci_mmcfg_read+173>: pop %rbx 0xffffffff802d6ee2 <pci_mmcfg_read+174>: pop %rbp 0xffffffff802d6ee3 <pci_mmcfg_read+175>: pop %r12 0xffffffff802d6ee5 <pci_mmcfg_read+177>: pop %r13 0xffffffff802d6ee7 <pci_mmcfg_read+179>: pop %r14 0xffffffff802d6ee9 <pci_mmcfg_read+181>: pop %r15 0xffffffff802d6eeb <pci_mmcfg_read+183>: retq
Dave
Re: 2.6.16-rc1 panic on startup (acpi)
Quoted 9 lines · Dave Jones
Quoted 5 lines · Andi Kleen
Quoted 3 lines
Quoted 1 line
Workaround is pci=nommconf btw
I'm puzzled. I'm still seeing this crash with latest -git which has this patch (I just double checked the source I built).
That's surprising. Can you addr2line the exactly address it's crashing on?
Still there in todays git snapshot.
http://people.redhat.com/davej/dsc00150.jpg is the top of the oops.
Actually I think this is pilot error. I've been running a mispatched tree.
Dave