[Crash-utility] unaligned access messages in crash 4.0-3.14 ia64

[Josh Giles]

Hi Dave!

I'm seeing unaligned access messages using crash on an IA64 w/~512MB. I
don't see any glaring problems with the backtraces themselves:

crash /usr/lib/debug/lib/modules/2.6.18-1.2839.el5/vmlinux
/var/crash/2006-12-11-15\:11/vmcore

crash 4.0-3.14
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(3615): unaligned access to 0x60000000001c34a4, ip=0x4000000000277420
crash(3615): unaligned access to 0x60000000001c34ac, ip=0x4000000000277420
crash(3615): unaligned access to 0x60000000001c34b4, ip=0x4000000000277420
crash(3615): unaligned access to 0x60000000001c34bc, ip=0x4000000000277420
crash(3615): unaligned access to 0x60000000001c34c4, ip=0x4000000000277420
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"...

KERNEL: /usr/lib/debug/lib/modules/2.6.18-1.2839.el5/vmlinux
DUMPFILE: /var/crash/2006-12-11-15:11/vmcore
CPUS: 4
DATE: Mon Dec 11 15:10:22 2006
UPTIME: 13:54:59
LOAD AVERAGE: 0.00, 0.00, 0.00
TASKS: 104
NODENAME: falcon.lab.boston.redhat.com
RELEASE: 2.6.18-1.2839.el5
VERSION: #1 SMP Tue Dec 5 22:53:49 EST 2006
MACHINE: ia64 (1495 Mhz)
MEMORY: 472.9 MB
PANIC: "SysRq : Trigger a crashdump"
PID: 2983
COMMAND: "bash"
TASK: e000000034000000 [THREAD_INFO: e000000034001040]
CPU: 2
CPU: 2
STATE: TASK_RUNNING (SYSRQ)
---------------------------------------------------------------

I can create a bugzilla for this problem if it turns out to be a real one.

-Josh