mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Peter Zijlstra <peterz@infradead.org>, x86-ml <x86@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: INFO: task rcu_gp:3 blocked for more than 122 seconds.
Date: Fri, 30 Sep 2022 09:11:29 -0700	[thread overview]
Message-ID: <20220930161129.GH4196@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <YzbCtvNWue+qUnT0@zn.tnic>

On Fri, Sep 30, 2022 at 12:19:34PM +0200, Borislav Petkov wrote:
> On Thu, Sep 29, 2022 at 08:37:22AM -0700, Paul E. McKenney wrote:
> > As discussed on IRC, I got nuttin' on this one.  Looks like an RCU
> > expedited grace period is stuck waiting for its workqueue kthread, and
> > that this workqueue kthread is stuck for some reason.
> 
> Yeah, it is not that easy to repro - I need to wait a couple of minutes
> after it boots. Look at the timestamps:
> 
> [  249.149378] INFO: task rcu_gp:3 blocked for more than 122 seconds.
> ^^^^^^^^^^^^^^

That can be annoying!  I well recall one bisection session where each step
took several hours, and where each step required manual intervention,
and where the bug was urgent.  I got the bisection overnight, but was
pretty useless then next day.  ;-)

> But it looks like sched/core is the culprit because merging it into
> Linus master triggers it.

It is possible that Peter would want proof of this.  ;-)

> Lemme bisect that.

Please, and thank you in advance!

							Thanx, Paul

> Stay tuned.
> 
> -- 
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2022-09-30 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  9:26 Borislav Petkov
2022-09-29 15:37 ` Paul E. McKenney
2022-09-30 10:19   ` Borislav Petkov
2022-09-30 16:11     ` Paul E. McKenney [this message]
2022-09-30 16:28       ` Borislav Petkov

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=20220930161129.GH4196@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@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

all inboxes | Powered by JetHome®