mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, haveblue@us.ibm.com,
	kravetz@us.ibm.com
Subject: Re: [PATCH] SPARSEMEM + NUMA can't handle unaligned memory regions?
Date: Tue, 09 May 2006 09:32:22 +0100	[thread overview]
Message-ID: <44605396.40507@shadowen.org> (raw)
In-Reply-To: <20060509070343.57853679F2@ozlabs.org>

Michael Ellerman wrote:
> I can't believe I'm the first person to see this, so I imagine I'm missing
> something. Perhaps it's only an issue on powerpc?
> 
> I have a machine with some memory at 0, then a hole, and then some more memory
> which doesn't start on a section boundary. This is causing the following
> crash:
> 
> add_region nid 1 start_pfn 0x77c0 pages 0x840
> add_region nid 1 start_pfn 0x0 pages 0x6000

Nasty, could you send me your full boot log and your config and I'll
have a look at it.  I can say this code has been booted on a lot of
power boxes and I've never seen that before!  :)

Anyhow, will take a look and see if we can avoid iterating over the area
to find it.

-apw

  reply	other threads:[~2006-05-09  8:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09  7:03 Michael Ellerman
2006-05-09  8:32 ` Andy Whitcroft [this message]
2006-05-09  9:11   ` Michael Ellerman
2006-05-09 10:24     ` Andy Whitcroft
2006-05-09 13:34 ` Andy Whitcroft
2006-05-09 14:28   ` Andy Whitcroft
2006-05-09 16:26     ` Dave Hansen
2006-05-09 16:31       ` Andy Whitcroft
2006-05-10  6:06     ` Michael Ellerman
2006-05-10 10:51       ` [PATCH] sparsemem record nid during memory present Andy Whitcroft
2006-05-09 16:05   ` [PATCH] SPARSEMEM + NUMA can't handle unaligned memory regions? mike kravetz
2006-05-09 16:14     ` Andy Whitcroft

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=44605396.40507@shadowen.org \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=kravetz@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    /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

Powered by JetHome