From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: tglx@linutronix.de, peterz@infradead.org,
preeti@linux.vnet.ibm.com, viresh.kumar@linaro.org,
mtosatti@redhat.com, fweisbec@gmail.com
Cc: linux-kernel@vger.kernel.org, sasha.levin@oracle.com
Subject: Re: Possible issue with commit 4961b6e11825?
Date: Sun, 6 Dec 2015 12:56:03 -0800 [thread overview]
Message-ID: <20151206205603.GA9008@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151205190124.GA1990@linux.vnet.ibm.com>
On Sat, Dec 05, 2015 at 11:01:24AM -0800, Paul E. McKenney wrote:
> 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.
> >
> > But perhaps 3497d206c4d9 was just getting lucky, hence additional testing
> > over the weekend.
>
> And it was getting lucky. In a set of 24 two-hour runs (triple parallel)
> on an earlier commit (not 3497d206c4d9, no clue what I was thinking) got
> me two failed runs, for a total of 49 reports of one of RCU's grace-period
> kthreads being starved, no reports of rcutorture's kthreads being starved,
> and no hangs on shutdown. So much lower failure rate, but still failures.
>
> At this point, I am a bit disgusted with bisection, so my next test cycle
> (36 two-hour runs on a system capable of doing three concurrently) is on
> the most recent -rcu, but with CPU hotplug disabled. If that shows failures,
> then I hammer 3497d206c4d9 hard.
And no failures on current -rcu with CPU hotplug disabled. So this
seems to be specific to CPU hotplug. So my next step is to fix some
remaining known CPU-hotplug issues in RCU.
And Thomas, when you get those CPU-hotplug patches ready, I have a testcase
for you! ;-)
Thanx, Paul
next prev parent reply other threads:[~2015-12-06 20:55 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 [this message]
2015-12-07 19:01 ` Frederic Weisbecker
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=20151206205603.GA9008@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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 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.