From: Jiang Liu <liuj97@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
mingo@kernel.org, torvalds@linux-foundation.org,
cmetcalf@tilera.com, tony.luck@intel.com, sivanich@sgi.com,
akpm@linux-foundation.org, ralf@linux-mips.org,
greg.pearson@hp.com, ink@jurassic.park.msu.ru,
tglx@linutronix.de, rth@twiddle.net,
kamezawa.hiroyu@jp.fujitsu.com, paulus@samba.org,
linux-kernel@vger.kernel.org, hpa@zytor.com, anton@samba.org,
lethal@linux-sh.org, davem@davemloft.net,
benh@kernel.crashing.org, dhowells@redhat.com,
mattst88@gmail.com, fenghua.yu@intel.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched/numa: Rewrite the CONFIG_NUMA sched domain support
Date: Tue, 29 May 2012 08:32:03 +0800 [thread overview]
Message-ID: <4FC41903.1060705@gmail.com> (raw)
In-Reply-To: <CAE9FiQWB23V=XoyzQaq1X+JNtUcV=4bLQ1sGCMOTjKRqAV7XuQ@mail.gmail.com>
Hi Yinghai,
Does this patch fix your issue? https://lkml.org/lkml/2012/5/9/183.
I have encountered a similar issue on an IA64 platform and the patch above
works around it. But the root cause is a BIOS bug that the order of CPUs
in MADT table doesn't conform to the ACPI specification and the first CPU
in MADT is not the BSP, which breaks some assumption of the booting code
and causes the core dump.
Thanks!
On 05/11/2012 01:54 AM, Yinghai Lu wrote:
> On Thu, May 10, 2012 at 10:44 AM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>> On Thu, 2012-05-10 at 10:30 -0700, Yinghai Lu wrote:
>>> not sure if this one or other is related....
>>>
>>> got this from 8 socket Nehalem-ex box.
>>>
>>> [ 25.549259] mtrr_aps_init() done
>>> [ 25.554298] ------------[ cut here ]------------
>>> [ 25.554549] WARNING: at kernel/sched/core.c:6086 build_sched_domains+0x1a9/0x2d0()
>>
>> oops,.. could you get me the output of:
>>
>> cat /sys/devices/system/node/node*/distance
>>
>> for that machine? I'll see if I can reproduce using numa=fake.
>
> [ 0.000000] ACPI: SLIT: nodes = 8
> [ 0.000000] 10 15 20 15 15 20 20 20
> [ 0.000000] 15 10 15 20 20 15 20 20
> [ 0.000000] 20 15 10 15 20 20 15 20
> [ 0.000000] 15 20 15 10 20 20 20 15
> [ 0.000000] 15 20 20 20 10 15 15 20
> [ 0.000000] 20 15 20 20 15 10 20 15
> [ 0.000000] 20 20 15 20 15 20 10 15
> [ 0.000000] 20 20 20 15 20 15 15 10
>
>
> [root@yhlu-pc2 ~]# cat /sys/devices/system/node/node*/distance
> 10 15 15 20 15 20 20 20
> 15 10 20 15 20 15 20 20
> 15 20 10 15 20 20 15 20
> 20 15 15 10 20 20 20 15
> 15 20 20 20 10 15 20 15
> 20 15 20 20 15 10 15 20
> 20 20 15 20 20 15 10 15
> 20 20 20 15 15 20 15 10
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-05-29 0:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 14:29 [tip:sched/core] sched/numa: Rewrite the CONFIG_NUMA sched domain support tip-bot for Peter Zijlstra
2012-05-10 17:30 ` Yinghai Lu
2012-05-10 17:44 ` Peter Zijlstra
2012-05-10 17:54 ` Yinghai Lu
2012-05-29 0:32 ` Jiang Liu [this message]
2012-05-29 12:13 ` Peter Zijlstra
2012-05-29 17:12 ` Yinghai Lu
2012-05-24 21:23 ` Tony Luck
2012-05-25 7:31 ` Peter Zijlstra
2012-05-25 14:24 ` Tony Luck
2012-05-25 16:26 ` Tony Luck
2012-05-29 0:19 ` Anton Blanchard
2012-06-05 7:16 ` Alex Shi
2012-06-06 7:43 ` Alex Shi
2012-06-06 9:15 ` Peter Zijlstra
2012-06-07 0:34 ` Alex Shi
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=4FC41903.1060705@gmail.com \
--to=liuj97@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=greg.pearson@hp.com \
--cc=hpa@zytor.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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