rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Qian Cai <cai@lca.pw>
Cc: "Joel Fernandes (Google)" <joel@joelfernandes.org>,
	Tejun Heo <tj@kernel.org>, Josh Triplett <josh@joshtriplett.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	rcu@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "rcu: React to callback overload by aggressively seeking quiescent states" hangs on boot
Date: Fri, 13 Dec 2019 22:40:48 -0800	[thread overview]
Message-ID: <20191214064048.GI2889@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CAA6354A-C747-4BE0-8EDC-C06E3C1D7D08@lca.pw>

On Fri, Dec 13, 2019 at 06:11:16PM -0500, Qian Cai wrote:
> 
> 
> > On Dec 13, 2019, at 5:46 PM, Paul E. McKenney <paulmck@kernel.org> wrote:
> > 
> > I am running this on a number of x86 systems, but will try it on a
> 
> The config to reproduce includes several debugging options that might
> required to recreate.

If you run without those debugging options, do you still see the hangs?
If not, please let me know which debugging are involved.

> > wider variety.  If I cannot reproduce it, would you be willing to
> > run diagnostics?
> 
> Yes.

Very good!  Let me see what I can put together.  (No luck reproducing
at my end thus far.)

> > Just to double-check...  Are you running rcutorture built into the kernel?
> > (My guess is "no", but figured that I should ask.)
> 
> No as you can see from the config I linked in the original email.

Fair point, and please accept my apologies for the pointless question.

							Thanx, Paul

  reply	other threads:[~2019-12-14  6:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13  6:13 "rcu: React to callback overload by aggressively seeking quiescent states" hangs on boot Qian Cai
2019-12-13 22:46 ` Paul E. McKenney
2019-12-13 23:11   ` Qian Cai
2019-12-14  6:40     ` Paul E. McKenney [this message]
     [not found]       ` <CAA42JLbBFkpYHXRVvyveYO76DnbkE3gyRW-=qmBGZcJTAiB6Uw@mail.gmail.com>
2019-12-15 19:29         ` Dexuan-Linux Cui
2019-12-15 20:20         ` Paul E. McKenney
2019-12-15 20:40           ` Dexuan Cui
2019-12-15 20:56             ` Paul E. McKenney
2019-12-15 21:02               ` Dexuan Cui
     [not found] <BCD69C9E-4E61-405F-A514-36096E0F34F4@lca.pw>
2019-12-15 20:18 ` Paul E. McKenney
2019-12-15 20:19 ` Dexuan Cui

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=20191214064048.GI2889@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=cai@lca.pw \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tj@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).