ia64: What the stack trace of a slave cpu kdump should save?
Quoted 41 lines · Jay Lan (on Thu, 02 Nov 2006 10:48:51 -0800) wrote:
Hi,
I have a vmcore created by NMI on an SN. The gdb backtrace showed the slave cpu as below:
# gdb vmlinux vmcore-nmi-10 GNU gdb 6.4 Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "ia64-suse-linux"...Using host libthread_db library "/lib/libthread_db.so.1".#0
crash_save_this_cpu() atarch/ia64/kernel/crash.c:57warning: Source file is more recent than executable.
57memcpy(buf, name, note->n_namesz);
(gdb) bt
#0crash_save_this_cpu() atarch/ia64/kernel/crash.c:57
#10xa00000010005f580inkdump_cpu_freeze(info=<value optimized out>,
arg=0x1) atarch/ia64/kernel/crash.c:166
#20xa00000010000c9f0inunw_init_running() atinclude/linux/bitmap.h:237#30xa00000010005ef70inkdump_init_notifier(self=0xa000000100b47d78,
val=<value optimized out>, data=0xe000003007157b70)
atarch/ia64/kernel/crash.c:217
#40xa0000001000cf0d0innotifier_call_chain(nl=0xe000003014bcb3f8, val=13,
v=0xe000003007157b70) atkernel/sys.c:144
#50xa0000001000cf170inatomic_notifier_call_chain(nh=0xe000003014bcb3f0,
val=21, v=0xe000003007157b70) atkernel/sys.c:229
#60xa000000100048480inia64_init_handler(regs=0xe000003007157e40,
sw=<value optimized out>, sos=<value optimized out>)
atinclude/asm/kdebug.h:88
#70xa0000001000493a0inia64_os_init_virtual_begin()
atinclude/asm/kdebug.h:88
(gdb)
Quoted 2 lines
It is the stack _after_ NMI is triggered. Is this supposed to be? What do you see on other (ie not SN) ia64 platforms?
This is standard for INIT on any IA64 box, it is not SN specific. IA64 MCA/INIT run on separate stacks and tasks. Read Documentation/ia64/mca.txt and arch/ia64/kernel/mca.c::ia64_mca_modify_original_stack