From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: tglx@linutronix.de, peterz@infradead.org,
preeti@linux.vnet.ibm.com, viresh.kumar@linaro.org,
mtosatti@redhat.com, linux-kernel@vger.kernel.org,
sasha.levin@oracle.com
Subject: Re: Possible issue with commit 4961b6e11825?
Date: Mon, 7 Dec 2015 20:01:23 +0100 [thread overview]
Message-ID: <20151207190120.GB20032@lerouge> (raw)
In-Reply-To: <20151204232022.GA15891@linux.vnet.ibm.com>
On Fri, Dec 04, 2015 at 03:20:22PM -0800, Paul E. McKenney wrote:
> Hello!
>
> Are there any known issues with commit 4961b6e11825 (sched: core: Use
> hrtimer_start[_expires]())?
>
> The reason that I ask is that I am about 90% sure that an rcutorture
> failure bisects to that commit. I will be running more tests on
> 3497d206c4d9 (perf: core: Use hrtimer_start()), which is the predecessor
> of 4961b6e11825, and which, unlike 4961b6e11825, passes a 12-hour
> rcutorture test with scenario TREE03. In contrast, 4961b6e11825 gets
> 131 RCU CPU stall warnings, 132 reports of one of RCU's grace-period
> kthreads being starved, and 525 reports of one of rcutorture's kthreads
> being starved. Most of the test runs hang on shutdown, which is no
> surprise if an RCU CPU stall is happening at about that time.
I have no idea what the issue is but maybe you have the RCU stall backtrace
somewhere?
next prev parent reply other threads:[~2015-12-07 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 23:20 Possible issue with commit 4961b6e11825? Paul E. McKenney
2015-12-05 19:01 ` Paul E. McKenney
2015-12-06 2:36 ` Viresh Kumar
2015-12-06 5:18 ` Paul E. McKenney
2015-12-06 20:56 ` Paul E. McKenney
2015-12-07 19:01 ` Frederic Weisbecker [this message]
2015-12-07 20:00 ` Paul E. McKenney
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=20151207190120.GB20032@lerouge \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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