From: Robin Holt <holt@sgi.com>
To: Sachithanantham_Saravanan@emc.com
Cc: linux-ia64@vger.kernel.org, yakker@sgi.com,
yakker@turbolinux.com, yakker@alacritech.com, matt@aparity.com,
linux-kernel@vger.kernel.org
Subject: Re: LKCD on 2.6 IA64 Linux Kernel
Date: Tue, 25 Jan 2005 17:13:15 +0000 [thread overview]
Message-ID: <20050125171315.GA4951@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <50C05B7AA7D6924FB5E384EF14BC647BCBBD63@inba1mx2.corp.emc.com>
On Tue, Jan 25, 2005 at 03:16:21PM -0000, Sachithanantham_Saravanan@emc.com wrote:
> Hi all,
>
> I tried using lkcd on a ia64 machine running on 2.6.5-7.111 SuSe Kernel for
> debugging. I configured the swap device as the dump device and I created
> panics,oops to generate dumps. The dump happens in /var/log/dump on a "lkcd
> save" after a reboot. When I use lcrash to trace the task of the process
> that caused the dump, I get some data misalignment errors as listed below.
> And interestingly this happens only for the trace of the process that
> generated the panic/oops. For all other processes in the dump trace is
> giving me the proper output. Looks like the issue is specific to ia64 as I
> did not encounter any such errors on my i386 machine on the same kernel.
> Pointers to any patches or what the problem is will be of help to me.
Which version of lcrash are you using? I think you will need to build the
latest version of lcrash from the oss.sgi.com web page in order to use the
dumps created by the SuSE kernel. Not sure though.
Robin
next prev parent reply other threads:[~2005-01-25 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 15:16 LKCD on 2.6 IA64 Linux Kernel Sachithanantham_Saravanan
2005-01-25 17:13 ` Robin Holt [this message]
2005-01-25 17:48 ` Jason Uhlenkott
2005-01-25 23:58 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050125171315.GA4951@lnx-holt.americas.sgi.com \
--to=holt@sgi.com \
--cc=Sachithanantham_Saravanan@emc.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@aparity.com \
--cc=yakker@alacritech.com \
--cc=yakker@sgi.com \
--cc=yakker@turbolinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox