From: Vivek Goyal <vgoyal@in.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: fastboot@lists.osdl.org,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Morton Andrew Morton <akpm@osdl.org>
Subject: Re: [Fastboot] kexec+kdump testing with 2.6.12-rc3-mm3
Date: Wed, 11 May 2005 08:23:25 +0530 [thread overview]
Message-ID: <20050511025325.GA3638@in.ibm.com> (raw)
In-Reply-To: <1115769558.26913.1046.camel@dyn318077bld.beaverton.ibm.com>
On Tue, May 10, 2005 at 04:59:18PM -0700, Badari Pulavarty wrote:
> Hi,
>
> I am using kexec+kdump on 2.6.12-rc3-mm3 and it seems to be working
> fine on my 4-way P-III 8GB RAM machine. I did touch testing with
> kexec+kdump and it worked fine. Then ran heavy IO load and forced
> a panic and I was able to collect the dump. But I am not able to
> analyze the dump to find out if I really got a valid dump or not :(
>
Copying to LKML.
Gdb can not open a file larger than 2GB. You have got 8GB RAM hence
/proc/vmcore size must be similar. For testing purposes you can boot first
kernel with mem=2G and then take dump and analyze with gdb.
But we need to work on some crash analysis tools like "crash" to be able
to debug larger files.
> BTW, what architectures kexec+kdump supported ? Does it work on
> x86-64 ?
>
Kexec has been ported to x86-64 but not kdump.
Thanks
Vivek
next parent reply other threads:[~2005-05-11 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1115769558.26913.1046.camel@dyn318077bld.beaverton.ibm.com>
2005-05-11 2:53 ` Vivek Goyal [this message]
2005-05-11 15:20 ` [Fastboot] kexec+kdump testing with 2.6.12-rc3-mm3 Badari Pulavarty
2005-05-12 5:44 ` Vivek Goyal
2005-05-12 10:22 ` Maneesh Soni
2005-05-12 11:28 ` Srivatsa Vaddagiri
2005-05-14 10:33 ` Alexander Nyberg
2005-05-16 8:36 ` Maneesh Soni
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=20050511025325.GA3638@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=akpm@osdl.org \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.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;
as well as URLs for NNTP newsgroup(s).