Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hedi Berriche <hedi@sgi.com>
To: kexec@lists.infradead.org
Subject: Re: the exiting makedumpfile is almost there... :)
Date: Thu, 11 Sep 2008 15:32:26 +0100	[thread overview]
Message-ID: <20080911143226.GT29908@sgi.com> (raw)
In-Reply-To: <48C85836.8080606@sgi.com>

On Thu, Sep 11, 2008 at 00:29 Jay Lan wrote:
| a4700rac:/boot # date; makedumpfile -c -d31 -x
| /boot/vmlinux-2.6.27-rc5-default /proc/vmcore
| /mnt/sda9/diskdump/vmcore-2.6.27-rc5-default; date
| Wed Sep 10 14:31:56 PDT 2008
| Can't distinguish the pgtable.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| The kernel version is not supported.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| The created dumpfile may be incomplete.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| Copying data                       : [100 %]

Jay,

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.

One useful experiment would be to find out whether a makdedumpfile generated
vmcore, from the one you saved with cp, does exhibit the same problem.

Cheers,
Hedi.
-- 
Hedi Berriche
GPS Unix
http://www.sgi.com/support

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

  parent reply	other threads:[~2008-09-11 14:32 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 [this message]
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

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=20080911143226.GT29908@sgi.com \
    --to=hedi@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox