Jay Lan wrote:

Hi Dave,
I have another vmcore that gdb (6.4) was able to display bt
but crash failed to come up. This copy of crash contains
the changes you suggested on my previous failure report (10/26).
I am not sure if this was caused by the fault of this vmcore, since
gdb only showed one thread. There should be another thread. But i
think i should let you know and let you decide if this is the
case.
Thanks,
- jay

(jackhammer,113) crash vmlinux vmcore-nmi-10
crash 4.0-3.5
Copyright (C) 2002, 2003, 2004, 2005, 2006 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005 Fujitsu Limited
Copyright (C) 2005 NEC Corporation
Copyright (C) 1999, 2002 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program 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. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.
crash(1203): unaligned access to 0x60000000001bf1cc, ip=0x400000000026d090
crash(1203): unaligned access to 0x60000000001bf1d4, ip=0x400000000026d090
crash(1203): unaligned access to 0x60000000001bf1dc, ip=0x400000000026d090
crash(1203): unaligned access to 0x60000000001bf1e4, ip=0x400000000026d090
crash(1203): unaligned access to 0x60000000001bf1ec, ip=0x400000000026d090
GNU gdb 6.1
Copyright 2004 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-unknown-linux-gnu"...
crash: invalid (optional) structure member offsets:
pglist_data_node_next or pglist_data_pgdat_next
       FILE: memory.c LINE: 11504 FUNCTION: node_table_init()
[/usr/people/jlan/bin/crash] error trace: => 4000000000231740
4000000000231740: OFFSET_option+432
WARNING: Because this kernel was compiled with gcc version 4.1.0, certain
         commands or command options may fail unless crash is invoked with
         the "--readnow" command line option.

But -- if you commented out the setting of (vt->flags | NODES) in
vm_init() as I suggested, how is it possible to even make it to
line 11504 in node_table_init() below? You're crashing in the
OFFSET_OPTION() call below:

11490 node_table_init(void)
11491 {
11492 int n;
11493 ulong pgdat;
11494
11495 /*
11496   * Override numnodes -- some kernels may leave it at 1 on a system
11497   * with multiple memory nodes.
11498   */
11499 if (vt->flags & NODES) {
11500          get_symbol_data("pgdat_list", sizeof(void *), &pgdat);
11501
11502          for (n = 0; pgdat; n++) {
11503                  readmem(pgdat + OFFSET_OPTION(pglist_data_node_next,
11504                          pglist_data_pgdat_next), KVADDR,
11505                          &pgdat, sizeof(void *), "pglist_data node_next",
11506                          FAULT_ON_ERROR);
11507   }

Dave