-----Original Message-----
From: crash-utility-bounces(a)redhat.com
[mailto:crash-utility-bounces@redhat.com] On Behalf Of Dave Anderson
Sent: Monday, May 14, 2007 12:22 PM
To: Discussion list for crash utility usage, maintenance and
development
Subject: Re: [Crash-utility] Seek error type: "tss_struct ist
array" problem on8-CPU AMD system
"Jansen, Frank" wrote:
> Looking through the changelog, I saw that the 'tss_struct ist array'
> problem on 8-CPU systems had been addressed previously.
However, I'm
> running into this issue on an AMD server with crash 4.0-4.1
and RHEL4
> Update 5 (2.6.9-55.Elsmp).
>
> The output from the crash invocation is the following:
> +++
> [root@well-rhel4564-ps3 dump]# /fpj/crash System_map.2.6.9-55.ELsmp
> vmlinux.debug.2.6.9-55.ELsmp ap3.1178895173.dmp
>
> crash 4.0-4.1
> Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 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 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 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 "x86_64-unknown-linux-gnu"...
>
> crash: seek error: kernel virtual address: 10408119e84 type:
> "tss_struct ist array"
> ---
>
> The server is a 4 dual-core AMD (2.8GHz) with 64GB.
>
> Any insights into how best to troubleshoot this are much
appreciated.
>
> Thanks,
>
> Frank Jansen
I doubt this has anything to do with the 8-cpu issue.
I think that you are right, as the crash -d7 seems to indicate that the
dump may be incomplete(cf. attached crash -d7 output).
A few questions:
Is this an RHEL4 derivative kernel of some kind? I ask
because you're using a system.map file as an argument.
It's a standard kernel, to which we add a couple of our (Egenera)
drivers. I can read the dump without the system map argument, but was
just going off the data provided to me by the person that ran into the
problem.
Anyway, this dumpfile is Egenera's LKCD off-shoot, correct?
Since you got an "lseek" error, the question is whether (1)
the virtual address of 10408119e84 is legitimate, and (2)
whether it is included in your dumpfile.
I think that the virtual address is legitimate, but that the dump is
incomplete at this point.
What does "crash -d7 ..." show?
See attached output
Does crash work on the live system?
Yes, it works
Dave
Thank you again!
Frank
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility