From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: There is a Tasks RCU stall warning
Date: Tue, 11 Apr 2017 17:21:07 -0400 [thread overview]
Message-ID: <20170411172107.59030e32@gandalf.local.home> (raw)
In-Reply-To: <20170411211802.GA19165@linux.vnet.ibm.com>
On Tue, 11 Apr 2017 14:18:02 -0700
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> Hello, Steve,
>
> Network connectivity issues... :-/
ug
>
> There is already a Tasks RCU stall warning, but it waits for
> ten -minutes- before complaining. You can change this with the
> rcupdate.rcu_task_stall_timeout kernel boot parameter, if you wish.
>
> Or did you wait longer than ten minutes?
Hmm, I may have waited longer. But I can try again and shorten the
timeout.
-- Steve
next prev parent reply other threads:[~2017-04-11 21:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 21:18 There is a Tasks RCU stall warning Paul E. McKenney
2017-04-11 21:21 ` Steven Rostedt [this message]
2017-04-11 21:32 ` Paul E. McKenney
2017-04-11 21:31 ` Steven Rostedt
2017-04-11 21:34 ` Steven Rostedt
2017-04-11 21:39 ` Steven Rostedt
2017-04-11 21:44 ` Paul E. McKenney
2017-04-11 21:49 ` Steven Rostedt
2017-04-11 21:56 ` Paul E. McKenney
2017-04-11 22:15 ` Steven Rostedt
2017-04-11 23:01 ` Paul E. McKenney
2017-04-11 23:04 ` Paul E. McKenney
2017-04-11 23:11 ` Paul E. McKenney
2017-04-12 3:23 ` Paul E. McKenney
2017-04-12 13:18 ` Steven Rostedt
2017-04-12 14:19 ` Paul E. McKenney
2017-04-12 14:42 ` Steven Rostedt
2017-04-12 15:18 ` Paul E. McKenney
2017-04-12 15:53 ` Steven Rostedt
2017-04-12 16:26 ` Paul E. McKenney
2017-04-12 16:49 ` Steven Rostedt
2017-04-12 14:48 ` Paul E. McKenney
2017-04-12 14:59 ` Steven Rostedt
2017-04-12 16:27 ` Paul E. McKenney
2017-04-12 16:57 ` Steven Rostedt
2017-04-12 17:07 ` Paul E. McKenney
2017-04-12 17:13 ` Steven Rostedt
2017-04-12 20:02 ` 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=20170411172107.59030e32@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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.