From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [bisected] "sched: Allow per-cpu kernel threads to run on online && !active" causes warning
Date: Sat, 30 Jul 2016 13:25:52 +0200 [thread overview]
Message-ID: <20160730112552.GA3744@osiris> (raw)
In-Reply-To: <alpine.DEB.2.11.1607271717320.19896@nanos>
On Wed, Jul 27, 2016 at 05:23:05PM +0200, Thomas Gleixner wrote:
> On Wed, 27 Jul 2016, Heiko Carstens wrote:
> > [ 3.162961] ([<0000000000176c30>] select_task_rq+0xc0/0x1a8)
> > [ 3.162963] ([<0000000000177d64>] try_to_wake_up+0x2e4/0x478)
> > [ 3.162968] ([<000000000015d46c>] create_worker+0x174/0x1c0)
> > [ 3.162971] ([<0000000000161a98>] alloc_unbound_pwq+0x360/0x438)
>
> > For some unknown reason select_task_rq() gets called with a task that has
> > nr_cpus_allowed == 0. Hence "cpu = cpumask_any(tsk_cpus_allowed(p));"
> > within select_task_rq() will set cpu to nr_cpu_ids which in turn causes the
> > warning later on.
> >
> > It only happens with more than one node, otherwise it seems to work fine.
> >
> > Any idea what could be wrong here?
>
> create_worker()
> tsk = kthread_create_on_node();
> kthread_bind_mask(tsk, pool->attrs->cpumask);
> do_set_cpus_allowed(tsk, mask);
> set_cpus_allowed_common(tsk, mask);
> cpumask_copy(&tsk->cpus_allowed, mask);
> tsk->nr_cpus_allowed = cpumask_weight(mask);
> wake_up_process(task);
>
> So this looks like pool->attrs->cpumask is simply empty.....
Just had some time to look into this a bit more. Looks like we initialize
the cpu_to_node_masks (way) too late on s390 for fake numa. So Peter's
patch just revealed that problem.
I'll see if initializing the masks earlier will fix this, but I think it
will.
next prev parent reply other threads:[~2016-07-30 11:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 12:54 [bisected] "sched: Allow per-cpu kernel threads to run on online && !active" causes warning Heiko Carstens
2016-07-27 15:23 ` Thomas Gleixner
2016-07-30 11:25 ` Heiko Carstens [this message]
2016-08-08 7:45 ` Ming Lei
2016-08-15 11:19 ` Heiko Carstens
2016-08-15 22:48 ` Tejun Heo
2016-08-16 7:55 ` Heiko Carstens
2016-08-16 15:20 ` Tejun Heo
2016-08-16 15:29 ` Peter Zijlstra
2016-08-16 15:42 ` Tejun Heo
2016-08-16 22:19 ` Heiko Carstens
2016-08-17 9:20 ` Michael Holzheu
2016-08-17 13:58 ` Tejun Heo
2016-08-18 9:30 ` Michael Holzheu
2016-08-18 14:42 ` Tejun Heo
2016-08-19 9:52 ` Michael Holzheu
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=20160730112552.GA3744@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox