public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: ljhc@br.ibm.com
Cc: linux-kernel@vger.kernel.org,
	Christoph Lameter <clameter@sgi.com>,
	Arnd Bergmann <arndb@arndb.de>
Subject: Re: SLUB doesn't work with kdump kernel on Cell
Date: Wed, 8 Aug 2007 23:10:59 +0200	[thread overview]
Message-ID: <200708082310.59997.arnd@arndb.de> (raw)
In-Reply-To: <1186604151.3608.46.camel@localhost.localdomain>

On Wednesday 08 August 2007, Lucio Correia wrote:
>   DMA             0 ->    12288
>   Normal      12288 ->    12288
> early_node_map[2] active PFN ranges
>     0:        0 ->     2560
>     1:    12287 ->    12288

As Christoph found, this memory map is really strange. Other machines
have something like

Zone PFN ranges:
  DMA             0 ->    16384
  Normal      16384 ->    16384
early_node_map[2] active PFN ranges
    0:        0 ->     8192
    1:     8192 ->    16384

Lucio,
What code builds the memory map that gets passed to the kdump kernel?
Does the original kernel see the same map on your machine?

	Arnd <><

  parent reply	other threads:[~2007-08-08 21:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 20:15 SLUB doesn't work with kdump kernel on Cell Lucio Correia
2007-08-08 20:26 ` Christoph Lameter
2007-08-08 20:34   ` Arnd Bergmann
2007-08-08 20:39     ` Christoph Lameter
2007-08-14 15:43   ` Lucio Correia
2007-08-14 19:42     ` Christoph Lameter
2007-08-15  0:57       ` Michael Ellerman
2007-08-15  1:56         ` Christoph Lameter
2007-08-15  2:11         ` Christoph Lameter
2007-08-15 19:57           ` Lucio Correia
2007-08-15 20:21             ` Christoph Lameter
2007-08-08 21:10 ` Arnd Bergmann [this message]
2007-08-09 13:57   ` Lucio Correia
2007-08-10  0:34     ` Michael Ellerman
2007-08-10 15:43       ` [Cbe-oss-dev] " Arnd Bergmann
2007-08-10  0:26   ` Michael Ellerman

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=200708082310.59997.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=arndb@arndb.de \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljhc@br.ibm.com \
    /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