From: Jingbai Ma <jingbai.ma@hp.com>
To: Dave Anderson <anderson@redhat.com>
Cc: bhe@redhat.com, nishimura@mxp.nes.nec.co.jp,
usui@mxm.nes.nec.co.jp, d hatayama <d.hatayama@jp.fujitsu.com>,
lisa mitchell <lisa.mitchell@hp.com>,
vgoyal@redhat.com, ruyang@redhat.com,
tachibana@mxm.nes.nec.co.jp, kumagai-atsushi@mxc.nes.nec.co.jp,
chaowang@redhat.com, kexec@lists.infradead.org,
Jingbai Ma <jingbai.ma@hp.com>,
crash-utility@redhat.com
Subject: Re: [PATCH v2] crash utility: fix max_mapnr issue on system has over 44-bit addressing
Date: Sat, 12 Oct 2013 09:56:40 +0800 [thread overview]
Message-ID: <5258AC58.4060308@hp.com> (raw)
In-Reply-To: <1398853173.5067799.1381517552627.JavaMail.root@redhat.com>
On 10/12/2013 02:52 AM, Dave Anderson wrote:
>
> Hello Jingbai,
>
> The old diskdump-compatibility issue has been addressed by this second
> patch, but it fails to work with "split" kdumps.
>
> I only have two sample split compressed kdumps. Despite the dumpfile
> names, both of them were compressed and filtered with "-c -d31".
>
>
>
> I have temporarily placed the sample split dumpfiles above here for you
> to download and test with:
>
> http://people.redhat.com/anderson/kdump_split
>
> Let me know when you have copied them so I can clear up the disk space.
>
> Thanks,
> Dave
I have downloaded the dumpfiles, and have reproduced this issue.
I'm working on this issue now, and will send you a new version soon.
--
Thanks,
Jingbai Ma
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-10-12 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 9:47 [PATCH v2] crash utility: fix max_mapnr issue on system has over 44-bit addressing Jingbai Ma
2013-10-11 18:52 ` Dave Anderson
2013-10-12 1:56 ` Jingbai Ma [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=5258AC58.4060308@hp.com \
--to=jingbai.ma@hp.com \
--cc=anderson@redhat.com \
--cc=bhe@redhat.com \
--cc=chaowang@redhat.com \
--cc=crash-utility@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=lisa.mitchell@hp.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=ruyang@redhat.com \
--cc=tachibana@mxm.nes.nec.co.jp \
--cc=usui@mxm.nes.nec.co.jp \
--cc=vgoyal@redhat.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 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.