From: keith mannthey <kmannth@us.ibm.com>
To: David Rientjes <rientjes@cs.washington.edu>
Cc: Andrew Morton <akpm@osdl.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
lkml <linux-kernel@vger.kernel.org>,
clameter@engr.sgi.com
Subject: Re: [BUG] i386 2.6.18 cpu_up: attempt to bring up CPU 4 failed : kernel BUG at mm/slab.c:2698!
Date: Fri, 22 Sep 2006 12:44:18 -0700 [thread overview]
Message-ID: <1158954258.7292.6.camel@keithlap> (raw)
In-Reply-To: <Pine.LNX.4.64N.0609212108360.30543@attu1.cs.washington.edu>
On Thu, 2006-09-21 at 21:09 -0700, David Rientjes wrote:
> On Thu, 21 Sep 2006, Andrew Morton wrote:
Well I think there is 3 bug total exposed my unique situation. I think
all 3 issues are generic mainline bugs that have been around for
awhile.
1. SRAT not being mapped (patch submitted to fix boot_ioremap code)
This caused cpus to fail to be borough on line and panicked the box.
2. The panic is bad. I have so far tested the patch David
submitted.... It allowed the cpu_up calls to fail without panicking the
box. Andrew do you want me to test yours or ???
3. Flat mode i386 numa on a real numa system is broken. If there is
only 1 node in the system cpus should think they are apart of some other
node. Patch below.
If cases where a real numa system boots the Flat numa option make sure
the cpus don't claim to be apart on a non-existent node.
Signed-off-by: Keith Mannthey <kmannth@us.ibm.com>
--- linux-2.6.18/arch/i386/kernel/smpboot.c 2006-09-19
20:42:06.000000000 -0700
+++ linux-2.6.18-workes/arch/i386/kernel/smpboot.c 2006-09-21
21:57:55.000000000 -0700
@@ -642,9 +642,13 @@
{
int cpu = smp_processor_id();
int apicid = logical_smp_processor_id();
-
+ int node = apicid_to_node(apicid);
+
+ if (!node_online(node))
+ node = first_online_node;
+
cpu_2_logical_apicid[cpu] = apicid;
- map_cpu_to_node(cpu, apicid_to_node(apicid));
+ map_cpu_to_node(cpu, node);
}
static void unmap_cpu_to_logical_apicid(int cpu)
next prev parent reply other threads:[~2006-09-22 19:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 0:17 [BUG] i386 2.6.18 cpu_up: attempt to bring up CPU 4 failed : kernel BUG at mm/slab.c:2698! keith mannthey
2006-09-22 0:41 ` Andrew Morton
2006-09-22 1:34 ` keith mannthey
2006-09-22 2:09 ` KAMEZAWA Hiroyuki
2006-09-22 2:24 ` KAMEZAWA Hiroyuki
2006-09-22 3:08 ` Andrew Morton
2006-09-22 3:30 ` KAMEZAWA Hiroyuki
2006-09-22 3:38 ` David Rientjes
2006-09-22 3:42 ` Andrew Morton
2006-09-22 3:46 ` Andrew Morton
2006-09-22 4:09 ` David Rientjes
2006-09-22 18:20 ` [PATCH] do not free non slab allocated per_cpu_pageset David Rientjes
2006-09-22 18:22 ` Christoph Lameter
2006-09-22 18:39 ` Andrew Morton
2006-09-22 18:43 ` Christoph Lameter
2006-09-22 18:56 ` Andrew Morton
2006-09-22 19:06 ` Christoph Lameter
2006-09-22 19:10 ` David Rientjes
2006-09-22 19:44 ` keith mannthey [this message]
2006-09-23 5:19 ` [BUG] i386 2.6.18 cpu_up: attempt to bring up CPU 4 failed : kernel BUG at mm/slab.c:2698! Andrew Morton
2006-09-22 2:31 ` keith mannthey
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=1158954258.7292.6.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@cs.washington.edu \
/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