From: Vivek Goyal <vgoyal@in.ibm.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>,
kexec-ml <kexec@lists.infradead.org>,
Dan Aloni <da-x@monatomic.org>,
crash mailing list <crash-utility@redhat.com>
Subject: Re: [PATCH 0/2] vmcoreinfo support for dump filtering #2
Date: Tue, 11 Sep 2007 09:22:50 +0530 [thread overview]
Message-ID: <20070911035250.GA5053@in.ibm.com> (raw)
In-Reply-To: <20070910113521.755d0433.rdunlap@xenotime.net>
On Mon, Sep 10, 2007 at 11:35:21AM -0700, Randy Dunlap wrote:
> On Fri, 7 Sep 2007 17:57:46 +0900 Ken'ichi Ohmichi wrote:
>
> > Hi,
>
> > I released a new makedumpfile (version 1.2.0) with vmcoreinfo support.
> > I updated the patches for linux and kexec-tools.
> >
> > PATCH SET:
> > [1/2] [linux-2.6.22] Add vmcoreinfo
> > The patch is for linux-2.6.22.
> > The patch adds the vmcoreinfo data. Its address and size are output
> > to /sys/kernel/vmcoreinfo.
> >
> > [2/2] [kexec-tools] Pass vmcoreinfo's address and size
> > The patch is for kexec-tools-testing-20070330.
> > (http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/)
> > kexec command gets the address and size of the vmcoreinfo data from
> > /sys/kernel/vmcoreinfo, and passes them to the second kernel through
> > ELF header of /proc/vmcore. When the second kernel is booting, the
> > kernel gets them from the ELF header and creates vmcoreinfo's PT_NOTE
> > segment into /proc/vmcore.
>
> Hi,
> When using the vmcoreinfo patches, what tool(s) are available for
> analyzing the vmcore (dump) file? E.g., lkcd or crash or just gdb?
>
> gdb works for me, but I tried to use crash (4.0-4.6 from
> http://people.redhat.com/anderson/) and crash complained:
>
> crash: invalid kernel virtual address: 0 type: "cpu_pda entry"
>
> Should crash work, or does it need to be modified?
>
Hi Randy,
Crash should just work. It might broken on latest kernel. Copying it
to crash-utility mailing list. Dave will be able to tell us better.
> This is on a 2.6.23-rc3 kernel with vmcoreinfo patches and a dump file
> with -l 31 (dump level 31, omitting all possible pages).
>
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-09-11 3:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 8:57 [PATCH 0/2] vmcoreinfo support for dump filtering #2 Ken'ichi Ohmichi
2007-09-10 18:35 ` Randy Dunlap
2007-09-11 3:52 ` Vivek Goyal [this message]
2007-09-11 4:45 ` [Crash-utility] " Piet Delaney
2007-09-11 5:23 ` Randy Dunlap
2007-09-11 5:58 ` Horms
2007-09-11 14:03 ` Dave Anderson
2007-09-11 16:25 ` Randy Dunlap
2007-09-11 18:12 ` Dave Anderson
2007-09-11 23:01 ` Randy Dunlap
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=20070911035250.GA5053@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=crash-utility@redhat.com \
--cc=da-x@monatomic.org \
--cc=kexec@lists.infradead.org \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.