public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Picco <bob.picco@hp.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andi Kleen <ak@suse.de>,
	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: Sun, 30 Oct 2005 19:17:27 -0500	[thread overview]
Message-ID: <20051031001727.GC6019@localhost.localdomain> (raw)
In-Reply-To: <1130607017.12551.5.camel@localhost>

Dave Hansen wrote:	[Sat Oct 29 2005, 01:30:17PM EDT]
> 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
Dave,

This is a slightly modified patch I used on x86_64 for EXTREME testing. The
original 2.6.13-rc1-mhp1 patch didn't apply cleanly against 2.6.14. It will 
apply with this untested patch.  The patch needs to have arch_sparse_init
which is only active for SPARSEMEM. This patch was just for testing EXTREME 
on x86_64 NUMA and needs review.

I think the bootmem allocator is being used before initialized.  This wouldn't
have happened before SPARSEMEM_EXTREME became the default.

If you feel my analysis is correct, I'll generate a cleaner patch and
test on my 4 way.

bob


Index: linux-2.6.14/arch/x86_64/mm/numa.c
===================================================================
--- linux-2.6.14.orig/arch/x86_64/mm/numa.c	2005-10-28 14:24:58.000000000 -0400
+++ linux-2.6.14/arch/x86_64/mm/numa.c	2005-10-30 18:49:20.000000000 -0500
@@ -94,7 +94,6 @@ void __init setup_node_bootmem(int nodei
 	start_pfn = start >> PAGE_SHIFT;
 	end_pfn = end >> PAGE_SHIFT;
 
-	memory_present(nodeid, start_pfn, end_pfn);
 	nodedata_phys = find_e820_area(start, end, pgdat_size); 
 	if (nodedata_phys == -1L) 
 		panic("Cannot find memory pgdat in node %d\n", nodeid);
@@ -280,9 +279,14 @@ unsigned long __init numa_free_all_bootm
 void __init paging_init(void)
 { 
 	int i;
-	for_each_online_node(i) {
+
+	for_each_online_node(i) 
+		memory_present(node_start_pfn(i), node_end_pfn(i));
+	
+	sparse_init();
+
+	for_each_online_node(i) 
 		setup_node_zones(i); 
-	}
 } 
 
 /* [numa=off] */
Index: linux-2.6.14/arch/x86_64/kernel/setup.c
===================================================================
--- linux-2.6.14.orig/arch/x86_64/kernel/setup.c	2005-10-28 14:24:58.000000000 -0400
+++ linux-2.6.14/arch/x86_64/kernel/setup.c	2005-10-30 18:50:05.000000000 -0500
@@ -657,8 +657,6 @@ void __init setup_arch(char **cmdline_p)
 	}
 #endif
 
-	sparse_init();
-
 	paging_init();
 
 	check_ioapic();



  reply	other threads:[~2005-10-31  0:17 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 [this message]
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=20051031001727.GC6019@localhost.localdomain \
    --to=bob.picco@hp.com \
    --cc=ak@suse.de \
    --cc=haveblue@us.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox