Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: Dave Anderson <anderson@redhat.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: Fri, 12 Sep 2008 15:21:30 -0700	[thread overview]
Message-ID: <48CAEB6A.8080405@sgi.com> (raw)
In-Reply-To: <48CAD340.7000701@redhat.com>

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

Dave Anderson wrote:
> Try using at least -d4 and redirect the output to a file.  It's much
> more verbose than the above, but it shows every readmem() made from
> the dumpfile:
> 
>  # crash -d4 vmlinux vmcore.cp > /tmp/debug.cp
>  q
>  # crash -d4 vmlinux vmcore.makedumpfile > /tmp/debug.makedumpfile
>  q
>  #
> 
> Then compare the two outputs -- they should be pretty much identical
> (except for any crash utility user addresses) until the vmcore.makedumpfile
> fails.  So you should see a successful readmem() of e0000060031417a8 in
> the "vmcore.cp" debug output at the point where it fails doing the
> read in "vmcore.makedumpfile" above.
> 
> What's kind of strange is that pglist_data.node_zones structure that
> it's reading from is in the same page as the base pglist_data
> at e000006003140000, i.e., at page offset 17a8 (6056).  And the code
> looks like it has already read data from that same page prior to
> reading the "zone spanned pages".  (I'm presuming that the ia64 page
> size you're using is greater than 4k).  But the -d4 output will
> confirm that.

Looks like it.

In the case of 'cp':
...
<readmem: a0000001010be338, KVADDR, "pgdat_list", 8, (ROE),
600fffffff8abfc0>
<readmem: e00000600315fb70, KVADDR, "pglist node_id", 4, (FOE),
600fffffff8ac01c>
                        <readmem: e00000600315fb48, KVADDR,
"node_mem_map", 8, (FOE), 600fffffff8ac020>
<readmem: e00000600315fb58, KVADDR, "pglist node_start_pfn", 8, (FOE),
600fffffff8ac030>
<readmem: e00000600315fb68, KVADDR, "pglist node_spanned_pages", 8,
(FOE), 600fffffff8ac040>
<readmem: e00000600315fb60, KVADDR, "pglist node_present_pages", 8,
(FOE), 600fffffff8ac048>
<readmem: e00000600315fb50, KVADDR, "pglist bdata", 8, (FOE),
600fffffff8ac090> node_table[0]:
             id: 0

          pgdat: e000006003140000
           size: 62720

        present: 62720
        mem_map: a07ffff8fdd0a800

    start_paddr: 6003000000
    start_mapnr: 6292224

<readmem: e0000060031417a8, KVADDR, "zone spanned_pages", 8, (FOE),
600fffffff8ac058>
                    <readmem: e0000060031416c8, KVADDR, "zone[_struct]
free_pages", 8, (FOE), 600fffffff8ac050>

...


In the case of makedumpfile:
...
<readmem: a0000001010be338, KVADDR, "pgdat_list", 8, (ROE),
600ffffffff4bfb0>
<readmem: e00000600315fb70, KVADDR, "pglist node_id", 4, (FOE),
600ffffffff4c00c>
<readmem: e00000600315fb48, KVADDR, "node_mem_map", 8, (FOE),
600ffffffff4c010>
<readmem: e00000600315fb58, KVADDR, "pglist node_start_pfn", 8, (FOE),
600ffffffff4c020>
<readmem: e00000600315fb68, KVADDR, "pglist node_spanned_pages", 8,
(FOE), 600ffffffff4c030>
<readmem: e00000600315fb60, KVADDR, "pglist node_present_pages", 8,
(FOE), 600ffffffff4c038>
<readmem: e00000600315fb50, KVADDR, "pglist bdata", 8, (FOE),
600ffffffff4c080> node_table[0]:
             id: 0

          pgdat: e000006003140000
           size: 62720

        present: 62720
        mem_map: a07ffff8fdd0a800

    start_paddr: 6003000000
    start_mapnr: 6292224

<readmem: e0000060031417a8, KVADDR, "zone spanned_pages", 8, (FOE),
600ffffffff4c048>
crash: page excluded: kernel virtual address: e0000060031417a8  type:
"zone spanned_pages"



jay

> 
> 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-12 22:22 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 [this message]
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=48CAEB6A.8080405@sgi.com \
    --to=jlan@sgi.com \
    --cc=anderson@redhat.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