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, Baoquan He <bhe@redhat.com>
Subject: makedumpfile: Issue with aarch64 support
Date: Fri, 15 May 2015 07:21:19 +0530	[thread overview]
Message-ID: <55555117.4080708@redhat.com> (raw)

Hi Atsushi,

* I am adding aarch64 support in makedumpfile. Preliminary patch is here 
[1]. I am having some issue with the dumpdisk created by makedumpfile. 
See, if you get any clue with following inputs.

* I used cp option in kdump.conf to have a good elf vmcore in 
/var/crash/..../vmcore.

* If I run crash over this elf vmcore, then everything goes fine.

* Now I use makedumpfile [1] for dumpdisk creation

  and compression just goes fine.
  # makedumpfile -l --message-level 1 -d 31 /var/crash/..../vmcore vmcore
  Copying data                       : [100.0 %] |

  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
crash: seek error: kernel virtual address: fffffe01ffde2000  type:
"memory section"

* I tried by removing -d option in makedumpfile , still same issue.

* A print for vaddr in vaddr_to_paddr_arm64 does not show address
fffffe01ffde2000 being asked for translation by makedumpfile core. 
Infact all the vaddr printed are in the range of directly mapped kernel 
VAs, so I did not consider to add support for other memory section like 
vmalloc, vmemmap etc at this point.

Thanks in advance for your help.

~Pratyush

[1] 
https://github.com/pratyushanand/makedumpfile/commit/073bc204c3422d6cee72eed89edb47281ead1a2e

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

             reply	other threads:[~2015-05-15  1:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  1:51 Pratyush Anand [this message]
2015-05-15  7:00 ` makedumpfile: Issue with aarch64 support Atsushi Kumagai
2015-05-15 18:16   ` Pratyush Anand

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=55555117.4080708@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.