>
> What happens if you apply the attached patch?  (it's against
> the current 4.0-3.8 version, but should apply)

Failed at different location.

Thanks,
 - jay

(jackhammer,157) crash vmlinuz-2.6.18-kdump vmcore

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(26323): unaligned access to 0x60000000001bf1cc, ip=0x400000000026d0f0
crash(26323): unaligned access to 0x60000000001bf1d4, ip=0x400000000026d0f0
crash(26323): unaligned access to 0x60000000001bf1dc, ip=0x400000000026d0f0
crash(26323): unaligned access to 0x60000000001bf1e4, ip=0x400000000026d0f0
crash(26323): unaligned access to 0x60000000001bf1ec, ip=0x400000000026d0f0
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 structure member offset: zone_zone_mem_map
       FILE: memory.c  LINE: 11401  FUNCTION: dump_memory_nodes()

[./crash] error trace: => 4000000000231c90

  4000000000231c90: OFFSET_verify+336
 

        if (symbol_exists("pgdat_list") && !IS_SPARSEMEM())
                vt->flags |= NODES;

Also, can you do this:

  $ gdb vmlinuz-2.6.18-kdump
  ...
  (gdb) ptype struct pglist_data

Dave