From: Bernhard Walle <bwalle@suse.de>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: Jay Lan <jlan@sgi.com>, kexec@lists.infradead.org
Subject: Re: makedumpfile fails on SGI machine
Date: Mon, 18 Aug 2008 13:00:25 +0200 [thread overview]
Message-ID: <20080818130025.0282e471@halley.suse.de> (raw)
In-Reply-To: <48A9228A.3070005@mxs.nes.nec.co.jp>
Hi,
* Ken'ichi Ohmichi [2008-08-18 16:19]:
> Bernhard Walle wrote:
> > * Ken'ichi Ohmichi [2008-08-05 21:07]:
> >> BTW, I'd like to know some conditions of this problem.
> >> So please let me know the makedumpfile commandline which you run.
> >> Ex. # makedumpfile -d 31 -x vmlinux /proc/vmcore dumpfile
> >
> > # makedumpfile -d 3 -D vmcore.sles11 vmcore.sles11.filtered
> >
> >> I doubt that makedumpfile cannot distinguish the pgtable correctly.
> >> I created the debugging patch. Please run makedumpfile-1.2.7 applied
> >> with it by '-D' option, and report the output.
> >> According to your kernel .config file, the output should contain
> >> "PAGETABLE_4L : ON".
> >
> > See the attachment.
>
> Thanks for the log.
> makedumpfile can distinguish the pgtable correctly.
>
> Can the crash utility translate the virtual address 0xa0007fff8f900000
> to physical address ? Please run the following subcommand on the crash
> utility.
>
> crash> vtop 0xa0007fff8f900000
crash> vtop 0xa0007fff8f900000
VIRTUAL PHYSICAL
a0007fff8f900000 (not mapped)
PAGE DIRECTORY: a000000100914000
PGD: a000000100914000 => 30030bc000
PUD: e0000030030bfff8 => 30030c0000
PMD: e0000030030c3e38 => 30030c4000
PTE: e0000030030c7200 => 0
But I guess that's normal with virtual memory maps:
$ zgrep VIRTUAL_M /proc/config.gz
CONFIG_VIRTUAL_MEM_MAP=y
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
“Make everything as simple as possible, but not simpler.”
-- Albert Einstein
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-08-18 11:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 14:14 makedumpfile fails on SGI machine Bernhard Walle
2008-07-31 1:46 ` Ken'ichi Ohmichi
2008-07-31 8:47 ` Bernhard Walle
2008-07-31 10:25 ` Ken'ichi Ohmichi
2008-07-31 11:18 ` Bernhard Walle
2008-07-31 11:36 ` Ken'ichi Ohmichi
2008-07-31 11:38 ` Bernhard Walle
2008-08-05 12:07 ` Ken'ichi Ohmichi
2008-08-05 15:11 ` Bernhard Walle
2008-08-18 7:19 ` Ken'ichi Ohmichi
2008-08-18 11:00 ` Bernhard Walle [this message]
2008-08-19 12:14 ` Ken'ichi Ohmichi
2008-08-27 9:00 ` Ken'ichi Ohmichi
2008-08-28 1:43 ` Jay Lan
2008-08-28 4:33 ` Ken'ichi Ohmichi
2008-08-28 7:25 ` Bernhard Walle
2008-08-29 6:45 ` [PATCH][ia64] Fix the difference between node_mem_map and node_start_pfn. (Re: makedumpfile fails on SGI machine) Ken'ichi Ohmichi
2008-08-29 16:54 ` Bernhard Walle
2008-09-01 2:13 ` Ken'ichi Ohmichi
2008-08-29 18:14 ` Jay Lan
2008-08-29 20:12 ` Jay Lan
2008-09-01 2:32 ` Ken'ichi Ohmichi
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=20080818130025.0282e471@halley.suse.de \
--to=bwalle@suse.de \
--cc=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=oomichi@mxs.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