Re: sched: CPU #1's llc-sibling CPU #0 is not on the same node!

[Tim Gardner]

On 02/25/2013 08:02 AM, Tim Gardner wrote:
> Is this an expected warning ? I'll boot a vanilla kernel just to be sure.
> 
> rebased against ab7826595e9ec51a51f622c5fc91e2f59440481a in Linus' repo:
> 

Same with a vanilla kernel, so it doesn't appear that any Ubuntu cruft
is having an impact:

[    0.170435] ------------[ cut here ]------------
[    0.170450] WARNING: at arch/x86/kernel/smpboot.c:324
topology_sane.isra.2+0x71/0x84()
[    0.170452] Hardware name: S2600CP
[    0.170454] sched: CPU #1's llc-sibling CPU #0 is not on the same
node! [node: 1 != 0]. Ignoring dependency.
[    0.156000] smpboot: Booting Node   1, Processors  #1
[    0.170455] Modules linked in:
[    0.170460] Pid: 0, comm: swapper/1 Not tainted 3.8.0+ #1
[    0.170461] Call Trace:
[    0.170466]  [<ffffffff810597bf>] warn_slowpath_common+0x7f/0xc0
[    0.170473]  [<ffffffff810598b6>] warn_slowpath_fmt+0x46/0x50
[    0.170477]  [<ffffffff816cc752>] topology_sane.isra.2+0x71/0x84
[    0.170482]  [<ffffffff816cc9de>] set_cpu_sibling_map+0x23f/0x436
[    0.170487]  [<ffffffff816ccd0c>] start_secondary+0x137/0x201
[    0.170502] ---[ end trace 09222f596307ca1d ]---

rtg
-- 
Tim Gardner tim.gardner@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/