From: Michael Ellerman <michael@ellerman.id.au>
To: Andy Whitcroft <apw@shadowen.org>
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 19:11:11 +1000 [thread overview]
Message-ID: <1147165871.8704.14.camel@localhost.localdomain> (raw)
In-Reply-To: <44605396.40507@shadowen.org>
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
On Tue, 2006-05-09 at 09:32 +0100, Andy Whitcroft wrote:
> 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! :)
Ah yeah, I seem to have neglected to mention it's a kdump boot :} Sorry.
That's why we get the strangely aligned memory sections. The section
starting at 0 is for the kdump kernel, the bit at 0x77c0 covers some
firmware that's allocated there by the first kernel.
I can still give you a .config and log if you want it, but not 'til
tomorrow morning.
> Anyhow, will take a look and see if we can avoid iterating over the area
> to find it.
Yeah it's a bit nasty having the loop. I figure on most configs it'll
pop on the first iteration, but still.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-05-09 9:11 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
2006-05-09 9:11 ` Michael Ellerman [this message]
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=1147165871.8704.14.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@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
Powered by JetHome