Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Anderson <anderson@redhat.com>
To: Jay Lan <jlan@sgi.com>
Cc: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>,
	kexec@lists.infradead.org, Hedi Berriche <hedi@sgi.com>
Subject: Re: the exiting makedumpfile is almost there... :)
Date: Tue, 23 Sep 2008 16:47:49 -0400	[thread overview]
Message-ID: <48D955F5.5050508@redhat.com> (raw)
In-Reply-To: <48D94F89.5010607@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]

Jay Lan wrote:
> Ken'ichi Ohmichi wrote:
> 
>>Hi Jay,
> 
> 
> Hi Ken'ichi,
> 
> 
>>My IA64 linux-2.6.27-rc7 kernel could boot by your patches and its kdump
>>succeeded, thanks. But I cannot reproduce this problem unfortunately.
>>Could you send me your kernel .config file to reproduce it ?
> 
> 
> 
> I just emailed you my .config.
> 
> 
>>And could you please research the reason why the page of virtual address
>>0xe0000060031417a8 is excluded ?  This patch is for researching it.
>>Please apply it against makedumpfile-1.2.9, and create a dump file
>>by makedumpfile with "-e 0xe0000060031417a8" option. The reason why
>>excluding the page is printed like the following:
> 
> 
> The excluded page moved. It is at at e0000060030f0000 type: "pmd page".
> The change that Dave said helped him did not help me though.

Did you initialize the reset_cache variable to 1 at the top of the function?
I forgot to put that in my post.

In any case, you still want to debug that function.  Since you know what
the target pfn being skipped is: 60030f0000 >> PAGE_SHIFT, you can
dump out the page->flags field in exclude_unnecessary_pages() when it
comes up in the loop.  Then when you run crash on the "cp" dumpfile,
do a "kmem -p 60030f0000", which will show the associated page struct
address and a few fields within it.  My guess is that the page->flags
field that you saw in makedumpfile's exclude_unnecessary_pages() will
not be the same as what you see running crash.

Dave


Dave


[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

      reply	other threads:[~2008-09-23 20:49 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
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 [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=48D955F5.5050508@redhat.com \
    --to=anderson@redhat.com \
    --cc=hedi@sgi.com \
    --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