From: Jay Lan <jlan@sgi.com>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: kexec@lists.infradead.org, Hedi Berriche <hedi@sgi.com>
Subject: Re: the exiting makedumpfile is almost there... :)
Date: Fri, 12 Sep 2008 06:38:21 -0700 [thread overview]
Message-ID: <48CA70CD.2090500@sgi.com> (raw)
In-Reply-To: <48C9D22A.5010404@mxs.nes.nec.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]
Ken'ichi Ohmichi wrote:
> Hi Hedi, Jay,
>
> Hedi Berriche wrote:
>> In addition to what other folks have mentioned about giving the latest crash
>> version a try, I'd like to point out that makedumpfile did spit a couple of
>> warnings while creating the vmcore
>>
>>
>> | Can't distinguish the pgtable.
>> | The kernel version is not supported.
>> | The created dumpfile may be incomplete.
>>
>> these warnings added to the fact that later on crash choked with
>>
>> | NOTE: page_hash_table does not exist in this kernel
>> | crash: page excluded: kernel virtual address: e000006003108e00 type:
>>
>> seem to suggest that the makedumpfile warnings could be relevant to the
>> end result.
>
> Oh, good point.
> If makedumpfile cannot distinguish the pgtable, it guesses PGTABLE_3 and
> creates a dumpfile. If Jay's kernel .config file has CONFIG_PGTABLE_4=y,
> makedumpfile misunderstands the pgtable. If it has CONFIG_PGTABLE_4=y,
> could you please try the attached patch ? This patch is only for debugging,
> and I'll investigate the cause.
My .config uses CONFIG_PGTABLE_3=y.
I will try to build makedumpfile-1.2.9 and report back.
Thanks
jay
>
>
> Thanks
> Ken'ichi Ohmichi
>
> ---
> diff -puN backup/makedumpfile-1.2.9/ia64.c makedumpfile/ia64.c
> --- backup/makedumpfile-1.2.9/ia64.c 2008-09-04 16:31:58.000000000 +0900
> +++ makedumpfile/ia64.c 2008-09-12 11:27:38.000000000 +0900
> @@ -79,6 +79,7 @@ get_machdep_info_ia64(void)
> vt.mem_flags |= MEMORY_PAGETABLE_3L;
> DEBUG_MSG("PAGETABLE_3L : ON\n");
> } else {
> + vt.mem_flags |= MEMORY_PAGETABLE_4L;
> MSG("Can't distinguish the pgtable.\n");
> }
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-09-12 13:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 23:28 the exiting makedumpfile is almost there... :) Jay Lan
2008-09-11 2:03 ` Ken'ichi Ohmichi
2008-09-11 8:21 ` Bernhard Walle
2008-09-11 2:31 ` Ken'ichi Ohmichi
2008-09-11 14:13 ` Dave Anderson
2008-09-11 14:32 ` Hedi Berriche
2008-09-12 2:21 ` Ken'ichi Ohmichi
2008-09-12 13:38 ` Jay Lan [this message]
2008-09-12 19:49 ` Jay Lan
2008-09-12 20:38 ` Dave Anderson
2008-09-12 22:21 ` Jay Lan
2008-09-15 15:24 ` Dave Anderson
2008-09-22 11:14 ` Ken'ichi Ohmichi
2008-09-23 15:41 ` Dave Anderson
2008-09-24 1:09 ` Ken'ichi Ohmichi
2008-09-24 18:30 ` Jay Lan
2008-09-24 21:56 ` Jay Lan
2008-09-25 6:38 ` Ken'ichi Ohmichi
2008-09-25 11:31 ` Ken'ichi Ohmichi
2008-09-25 19:22 ` Jay Lan
2008-09-26 0:17 ` Ken'ichi Ohmichi
2008-09-23 20:20 ` Jay Lan
2008-09-23 20:47 ` Dave Anderson
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=48CA70CD.2090500@sgi.com \
--to=jlan@sgi.com \
--cc=hedi@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