Heads up Linux 2.6.38-rc4 compile problems.
----- Original Message -----
> Hey Eric,
> On Mon, Feb 14, 2011 at 12:34 AM, Eric W. Biederman
> <email@example.com> wrote:
> > And for completeness. When I was rebooting v2.6.38-rc4 to start running
> > 795abaf1e4e188c4171e3cd3dbb11a9fcacaf505 I hit this.
> > Sigh. I wish crash worked on something besides redhats enterprise
> > kernels. Then I could use the system core file I have to do more than
> > extract the dmesg.
I update the upstream version of crash typically once a month.
Perhaps you are using an older version? I just built a 2.6.38-rc4
kernel, and the latest version of crash (5.1.2) works OK with it:
[root@hp-z400-02 ~]# crash
Copyright (C) 2002-2011 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005 NEC Corporation
Copyright (C) 1999, 2002, 2007 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.
GNU gdb (GDB) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
DATE: Tue Feb 15 08:57:17 2011
LOAD AVERAGE: 0.37, 0.10, 0.04
VERSION: #1 SMP Mon Feb 14 17:41:17 EST 2011
MACHINE: x86_64 (3067 Mhz)
MEMORY: 4 GB
TASK: ffff8801363f9710 [THREAD_INFO: ffff880135f2a000]
STATE: TASK_RUNNING (ACTIVE)
> Then you should cc firstname.lastname@example.org (now cc'd) and work with
> Dave Anderson (e.g. get him your vmlinux and core files, which version
> of crash you're using and how it fails). Dave does an amazing job of
> working through crash issues which are reported against upstream
> kernels -- the key first step is the report.
> Crash-utility mailing list
Crash-utility mailing list