From: Andy Whitcroft <apw@shadowen.org>
To: Bob Picco <bob.picco@hp.com>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>, Andi Kleen <ak@suse.de>,
Dave Hansen <haveblue@us.ibm.com>,
Janne M O Heikkinen <jmoheikk@cc.helsinki.fi>,
matthew.e.tolentino@intel.com, discuss@x86-64.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86_64: 2.6.14 with NUMA panics at boot
Date: Thu, 03 Nov 2005 17:06:28 +0000 [thread overview]
Message-ID: <436A4394.5080608@shadowen.org> (raw)
In-Reply-To: <20051103144305.GA22938@localhost.localdomain>
Bob Picco wrote:
> Matt responded to a private that I posted to Dave and Matt. Matt is
> traveling and told me to go ahead and post a fix.
>
> I removed memory_present called from the FLATMEM routine contig_initmem_init.
> Otherwise my original quick patch used for testing SPARSEMEM EXTREME
> was nearly complete.
>
> I've boot tested all three configurations (SPARSEMEM, DISCONTIGMEM and CONTIG)
> on my DL585 (4 node machine).
I'll test on it and let you know if it works for me too.
Thanks.
-apw
prev parent reply other threads:[~2005-11-03 17:07 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
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 [this message]
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=436A4394.5080608@shadowen.org \
--to=apw@shadowen.org \
--cc=ak@suse.de \
--cc=bob.picco@hp.com \
--cc=discuss@x86-64.org \
--cc=haveblue@us.ibm.com \
--cc=jmoheikk@cc.helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=mbligh@mbligh.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.