From: Peter Zijlstra <peterz@infradead.org>
To: Anna-Maria Gleixner <anna-maria@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: sched/core warning triggers on rcu torture test
Date: Tue, 26 Jun 2018 18:32:55 +0200 [thread overview]
Message-ID: <20180626163255.GG2458@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1806261709001.19188@somnus>
On Tue, Jun 26, 2018 at 06:16:04PM +0200, Anna-Maria Gleixner wrote:
> Hi,
>
> during rcu torture tests (TREE04 and TREE07) I noticed, that a
> WARN_ON_ONCE() in sched core triggers on a recent 4.18-rc2 based
> kernel (6f0d349d922b ("Merge
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net")) as well as
> on a 4.17.3.
>
> I'm running the tests on a machine with 144 cores:
>
> tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 144 --duration 120 --configs "9*TREE07"
> tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 144 --duration 120 --configs "18*TREE04"
>
>
> The warning was introduced by commit d84b31313ef8 ("sched/isolation:
> Offload residual 1Hz scheduler tick").
>
>
> Output looks similar for all tests I did (this one is the output of
> the 4.18-rc2 based kernel):
>
> WARNING: CPU: 11 PID: 906 at kernel/sched/core.c:3138 sched_tick_remote+0xb6/0xc0
That's nohz_full stuff, is that a normal part of rcutorture? In any
case, is the one housekeeping CPU getting seriously overloaded or
something?
next prev parent reply other threads:[~2018-06-26 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 16:16 Anna-Maria Gleixner
2018-06-26 16:32 ` Peter Zijlstra [this message]
2018-06-26 17:48 ` Paul E. McKenney
2018-06-27 10:40 ` Frederic Weisbecker
2018-06-27 14:25 ` Paul E. McKenney
2018-06-28 16:33 ` Frederic Weisbecker
2018-06-28 16:44 ` Paul E. McKenney
2018-06-28 19:04 ` Paul E. McKenney
2018-06-27 11:29 ` Frederic Weisbecker
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=20180626163255.GG2458@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=anna-maria@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®