From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jochen Striepe <jochen@tolot.escape.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: 3.10.5: rcu_sched detected stalls on CPUs/tasks
Date: Fri, 6 Dec 2013 06:54:41 -0800 [thread overview]
Message-ID: <20131206145441.GA24148@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131206135804.GI2208@pompeji.miese-zwerge.org>
On Fri, Dec 06, 2013 at 02:58:04PM +0100, Jochen Striepe wrote:
> Hi again,
>
> On Thu, Dec 05, 2013 at 04:26:14PM -0800, Paul E. McKenney wrote:
> > Hmmm... Does the following patch help?
> [...]
> > rcu: Kick CPU halfway to RCU CPU stall warning
>
> The stall didn't appear at all since my last email, running 3.12.x
> kernels since release. But I will test your patch later today. I assume
> applying on top of 3.12.3 is correct?
3.12.3 should take that patch just fine.
Thanx, Paul
next prev parent reply other threads:[~2013-12-06 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130813103202.GB2338@pompeji.miese-zwerge.org>
[not found] ` <20130818180232.GL29406@linux.vnet.ibm.com>
[not found] ` <20130818184848.GA2398@pompeji.miese-zwerge.org>
2013-09-09 21:58 ` 3.10.5: rcu_sched detected stalls on CPUs/tasks Jochen Striepe
2013-09-09 22:27 ` Paul E. McKenney
2013-09-10 7:45 ` Jochen Striepe
2013-09-10 17:54 ` Paul E. McKenney
2013-09-11 10:34 ` Jochen Striepe
2013-09-14 11:28 ` Jochen Striepe
2013-09-14 18:36 ` Paul E. McKenney
2013-09-23 16:49 ` Jochen Striepe
2013-12-06 0:26 ` Paul E. McKenney
2013-12-06 13:58 ` Jochen Striepe
2013-12-06 14:54 ` Paul E. McKenney [this message]
2013-12-10 11:22 ` Jochen Striepe
2013-12-16 22:40 ` Paul E. McKenney
2013-12-22 2:25 ` Jochen Striepe
2013-12-22 4:58 ` Paul E. McKenney
2013-12-27 17:15 ` Jochen Striepe
2013-12-27 18:08 ` 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=20131206145441.GA24148@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=jochen@tolot.escape.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).