From: Dave Hansen <haveblue@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Janne M O Heikkinen <jmoheikk@cc.helsinki.fi>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86_64: 2.6.14 with NUMA panics at boot
Date: Sat, 29 Oct 2005 19:30:17 +0200 [thread overview]
Message-ID: <1130607017.12551.5.camel@localhost> (raw)
In-Reply-To: <200510291841.49214.ak@suse.de>
On Sat, 2005-10-29 at 18:41 +0200, Andi Kleen wrote:
> On Saturday 29 October 2005 16:54, Janne M O Heikkinen wrote:
> > On Sat, 29 Oct 2005, Janne M O Heikkinen wrote:
> >
> > > No, I get same panics with numa=noacpi or even with numa=off. If I compile
> > > 2.6.14 kernel without CONFIG_ACPI_NUMA it does boot.
> >
> > It wasn't removing of CONFIG_ACPI_NUMA that made it boot after all, I had
> > also changed memory model from "Sparse" to "Discontiguous". And now
> > when I recompiled with CONFIG_ACPI_NUMA=y and with "Discontiguous" memory
> > model it booted just fine.
>
> Ok, that would explain it. I never test sparse, only discontiguous.
> sparse is only an experimental option that is not really maintained
> yet. Probably need to disable it if it's broken.
>
> Perhaps Dave H. knows what to do with it.
I'll try to dig up an Opteron machine on Monday and see what I can do.
-- Dave
next prev parent reply other threads:[~2005-10-29 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 19:26 x86_64: 2.6.14 with NUMA panics at boot Janne M O Heikkinen
2005-10-28 21:06 ` Andi Kleen
2005-10-28 22:06 ` Janne M O Heikkinen
2005-10-28 22:21 ` Janne M O Heikkinen
2005-10-29 10:01 ` Andi Kleen
2005-10-29 11:08 ` Janne M O Heikkinen
2005-10-29 14:54 ` Janne M O Heikkinen
2005-10-29 16:41 ` Andi Kleen
2005-10-29 17:30 ` Dave Hansen [this message]
2005-10-31 0:17 ` Bob Picco
2005-10-31 2:12 ` Andi Kleen
2005-10-31 1:40 ` Bob Picco
2005-10-31 3:28 ` Andi Kleen
2005-10-31 2:46 ` Bob Picco
2005-11-02 5:07 ` Martin J. Bligh
2005-11-02 18:08 ` Andy Whitcroft
2005-11-03 14:43 ` Bob Picco
2005-11-03 17:06 ` 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=1130607017.12551.5.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=ak@suse.de \
--cc=jmoheikk@cc.helsinki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.