All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: Atsushi Kumagai <ats-kumagai@wm.jp.nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"bhe@redhat.com" <bhe@redhat.com>
Subject: Re: makedumpfile: Issue with aarch64 support
Date: Fri, 15 May 2015 23:46:35 +0530	[thread overview]
Message-ID: <55563803.8080202@redhat.com> (raw)
In-Reply-To: <0910DD04CBD6DE4193FCF86B9C00BE9701DB45FE@BPXM01GP.gisp.nec.co.jp>



On Friday 15 May 2015 12:30 PM, Atsushi Kumagai wrote:
>>   But, crash does not like the vmcore
>> >  # crash/lib/modules/.../build/vmlinux vmcore -d 31
>> >
>> ><readmem: fffffe01ffde2000, KVADDR, "memory section", 32, (FOE),
>> >a2c4eb0>
>> ><read_diskdump: addr: fffffe01ffde2000 paddr: 41fffe2000 cnt: 32>
>> >read_diskdump: SEEK_ERROR: paddr/pfn: 41fffe2000/41fffe max_mapnr:
>> >414000
> According to this message, it seems that the max_mapnr in disk_dump_header
> was calculated wrongly by makedumpfile. pfn:41fffe must be exist since
> crash requires it, so max_mapnr must be shortened.
> What is the actual maximum pfn of the original vmcore ? If the number is
> correct, I have no ideas for now...


Thanks a lot for the pointer. I was able to find error in my aarch64 
code after following your pointer.

Will send the patch for review.

~Pratyush

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2015-05-15 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  1:51 makedumpfile: Issue with aarch64 support Pratyush Anand
2015-05-15  7:00 ` Atsushi Kumagai
2015-05-15 18:16   ` Pratyush Anand [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=55563803.8080202@redhat.com \
    --to=panand@redhat.com \
    --cc=ats-kumagai@wm.jp.nec.com \
    --cc=bhe@redhat.com \
    --cc=kexec@lists.infradead.org \
    /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.