From: Bouchard Louis <louis.bouchard@canonical.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: kexec@lists.infradead.org
Subject: Re: makedumpfile availability for x86 3.2 kernels
Date: Wed, 02 May 2012 16:42:21 +0200 [thread overview]
Message-ID: <4FA147CD.1060600@canonical.com> (raw)
In-Reply-To: <20120427132448.d7854fd6.kumagai-atsushi@mxc.nes.nec.co.jp>
Hello Kumagai-san,
Le 27/04/2012 06:24, Atsushi Kumagai a écrit :
> Hello Louis,
> Sorry, I haven't tested makedumpfile for 3.2 kernel yet, but I think it
> will work fine. If makedumpfile doesn't work in your environmental, then
> would you report it ?
>
> For your information, Suzuki reported that makedumpfile works for 3.2 kernel
> on ppc32.
>
> http://lists.infradead.org/pipermail/kexec/2012-February/006022.html
>
>
> Thanks
> Atsushi Kumagai
Following your advice, I tested it on our current kernel build. One of
the Ubuntu kernel developper tested it as well and here is what we get :
> makedumpfile -g vmcoreinfo-3.2.0-24-generic -x ../../build/build-generic/vmlinux
> The kernel version is not supported.
> The created dumpfile may be incomplete.
> generate_vmcoreinfo: Can't find the memory type.
>
> makedumpfile Failed.
I am rebuilding makedumpfile from the latest source (our version is
1.3.7 which is rather old) and will try to debug it further. I will let
you know what I find.
Kind regards,
...Louis
--
Louis Bouchard
Backline Support Analyst
Canonical Ltd
Ubuntu support: http://landscape.canonical.com
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2012-05-02 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 20:27 makedumpfile availability for x86 3.2 kernels Bouchard Louis
2012-04-27 4:24 ` Atsushi Kumagai
2012-04-27 15:25 ` Bouchard Louis
2012-05-10 7:37 ` Bouchard Louis
2012-05-11 4:52 ` Atsushi Kumagai
2012-05-02 14:42 ` Bouchard Louis [this message]
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=4FA147CD.1060600@canonical.com \
--to=louis.bouchard@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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