public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: Zero size /proc/vmcore on ia64
Date: Thu, 08 Feb 2007 13:07:37 +0000	[thread overview]
Message-ID: <20070208130736.GC7304@verge.net.au> (raw)
In-Reply-To: <20070205015901.GA31446@verge.net.au>

On Thu, Feb 08, 2007 at 03:52:15PM +0800, Zou, Nanhai wrote:
> 
>   Those values are wrong, 
> Could you test we a 2.6.20 plus the patch? 

I tried 2.6.20 + your patch.
I tried the same with the addition of Bob Picco's patch to stop
the crash-kernel crashing.
And I tried with Sparse and Discontig memory.
And in all cases I get much the same result :(

I'm wondering if perhaps its got something to do with kexec-tools,
I'm using kexec-tools-testing from git. Is there any possibility
you could send a static binary the version that you are using
(if its from Eric's old tree cross compiling doesn't really work)?

Or perhaps my kernel config is odd.

> Also it will be helpful to print efi_memmap in purgatory code.

Indeed. Do you have any way to dump purgatory's console across
a serial port? The vga console and I are on opposite sides of town
at the moent.


-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


  parent reply	other threads:[~2007-02-08 13:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05  1:59 Zero size /proc/vmcore on ia64 Horms
2007-02-08  2:07 ` Zou, Nanhai
2007-02-08  3:06 ` Horms
2007-02-08  4:21 ` Zou Nan hai
2007-02-08  5:46 ` Vivek Goyal
2007-02-08  7:36 ` Horms
2007-02-08  7:52 ` Zou, Nanhai
2007-02-08 13:07 ` Horms [this message]
2007-02-08 23:45 ` Zou, Nanhai
2007-02-13 17:25 ` Bernhard Walle
2007-02-14  8:27 ` Magnus Damm
2007-02-14  9:57 ` Zou, Nanhai
2007-02-14 11:46 ` Magnus Damm
2007-02-15  2:06 ` Zou, Nanhai
2007-02-15  2:17 ` Zou, Nanhai
2007-02-15  3:46 ` Horms

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=20070208130736.GC7304@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-ia64@vger.kernel.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