From: Peter Zijlstra <peterz@infradead.org>
To: Ben Hutchings <benh@debian.org>
Cc: Frede_Feuerstein@gmx.net, Ingo Molnar <mingo@elte.hu>,
603229@bugs.debian.org, LKML <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: Scheduler grouping failure; division by zero in select_task_rq_fair
Date: Mon, 29 Nov 2010 12:50:25 +0100 [thread overview]
Message-ID: <1291031425.32004.16.camel@laptop> (raw)
In-Reply-To: <1290975266.3292.316.camel@localhost>
On Sun, 2010-11-28 at 20:14 +0000, Ben Hutchings wrote:
> [ 0.856002] Pid: 2, comm: kthreadd Not tainted 2.6.32-5-amd64 #1 W1100z/2100z
What's in that kernel? is that simply the latest .32-stable?
> [ 0.536554] CPU0 attaching sched-domain:
> [ 0.540004] domain 0: span 0-1 level MC
> [ 0.548002] groups: 0 1
> [ 0.560003] domain 1: span 0-3 level NODE
> [ 0.568002] groups:
> [ 0.574179] ERROR: domain->cpu_power not set
> [ 0.576002]
> [ 0.580002] ERROR: groups don't span domain->span
> [ 0.584004] CPU1 attaching sched-domain:
> [ 0.588007] domain 0: span 0-1 level MC
> [ 0.596002] groups: 1 0 (cpu_power = 1023)
> [ 0.612002] ERROR: parent span is not a superset of domain->span
> [ 0.616003] domain 1: span 1-3 level CPU
> [ 0.624002] groups: 1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
> [ 0.644003] domain 2: span 0-3 level NODE
> [ 0.652004] groups: 1-3 (cpu_power = 4096)
> [ 0.668002] ERROR: domain->cpu_power not set
> [ 0.672002]
> [ 0.676002] ERROR: groups don't span domain->span
> [ 0.680004] CPU2 attaching sched-domain:
> [ 0.684003] domain 0: span 2-3 level MC
> [ 0.692003] groups: 2 3
> [ 0.704003] domain 1: span 1-3 level CPU
> [ 0.712003] groups: 2-3 (cpu_power = 2048) 1 (cpu_power = 2048)
> [ 0.736003] domain 2: span 0-3 level NODE
> [ 0.744003] groups: 1-3 (cpu_power = 4096)
> [ 0.760003] ERROR: domain->cpu_power not set
> [ 0.764003]
> [ 0.768003] ERROR: groups don't span domain->span
> [ 0.772004] CPU3 attaching sched-domain:
> [ 0.776003] domain 0: span 2-3 level MC
> [ 0.784003] groups: 3 2
> [ 0.794183] domain 1: span 1-3 level CPU
> [ 0.800003] groups: 2-3 (cpu_power = 2048) 1 (cpu_power = 2048)
> [ 0.822183] domain 2: span 0-3 level NODE
> [ 0.828003] groups: 1-3 (cpu_power = 4096)
> [ 0.842180] ERROR: domain->cpu_power not set
> [ 0.844003]
> [ 0.848003] ERROR: groups don't span domain->span
Hrm that smells like the architecture topology setup is wrecked, looks
like the NUMA setup is bonkers.
I really know very little about that code, I think Tejun recently poked
at that in an attempt to merge 32 and 64bit x86.
Also, its very weird CPU0 only gets to have 2 domains, while the other
3 get 3 domains..
Ingo, who knows this stuff?
next prev parent reply other threads:[~2010-11-29 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290449310.3868.13.camel@localhost>
[not found] ` <1290470134.6770.929.camel@localhost>
[not found] ` <1290514638.3892.16.camel@localhost>
[not found] ` <1290900814.3292.84.camel@localhost>
[not found] ` <1290920436.4255.1025.camel@localhost>
2010-11-28 20:14 ` Scheduler grouping failure; division by zero in select_task_rq_fair Ben Hutchings
2010-11-29 11:50 ` Peter Zijlstra [this message]
2010-11-29 13:58 ` Frede Feuerstein
2010-11-29 16:26 ` Ben Hutchings
2010-11-29 18:06 ` Ingo Molnar
2010-12-14 10:07 ` Frede Feuerstein
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=1291031425.32004.16.camel@laptop \
--to=peterz@infradead.org \
--cc=603229@bugs.debian.org \
--cc=Frede_Feuerstein@gmx.net \
--cc=benh@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tj@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 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.