linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NOHZ tick-stop error: Non-RCU local softirq work is pending
Date: Fri, 11 Dec 2020 01:15:15 +0100	[thread overview]
Message-ID: <20201211001515.GA580714@lothringen> (raw)
In-Reply-To: <20201210211756.GZ2657@paulmck-ThinkPad-P72>

On Thu, Dec 10, 2020 at 01:17:56PM -0800, Paul E. McKenney wrote:
> And please see attached.  Lots of output, in fact, enough that it
> was still dumping when the second instance happened.

Thanks!

So the issue is that ksoftirqd is parked on CPU down with vectors
still pending. Either:

1) Ksoftirqd has exited because it has too many to process and it has
   exceeded the time limit, but then it parks, leaving the rest unhandled.

2) Ksoftirqd has completed its work but something has raised a softirq
   after it got parked.

Can you run the following (on top of the previous patch and boot options)
so that we see if (and what) it still triggers (in which case we should be in 2)  ).

diff --git a/kernel/softirq.c b/kernel/softirq.c
index 09229ad82209..7d558cb7a037 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -650,7 +650,9 @@ static void run_ksoftirqd(unsigned int cpu)
 		 * We can safely run softirq on inline stack, as we are not deep
 		 * in the task stack here.
 		 */
-		__do_softirq();
+		do {
+			__do_softirq();
+		} while (kthread_should_park() && local_softirq_pending());
 		local_irq_enable();
 		cond_resched();
 		return;


Thanks!

  reply	other threads:[~2020-12-11  0:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 17:52 NOHZ tick-stop error: Non-RCU local softirq work is pending Paul E. McKenney
2020-11-18 17:54 ` Paul E. McKenney
2020-11-18 20:03   ` Paul E. McKenney
2020-12-10 13:04   ` Frederic Weisbecker
2020-12-10 14:56 ` Frederic Weisbecker
2020-12-10 21:17   ` Paul E. McKenney
2020-12-11  0:15     ` Frederic Weisbecker [this message]
2020-12-11  0:46       ` Paul E. McKenney
2020-12-11  1:40         ` Frederic Weisbecker
2020-12-11  3:24           ` 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=20201211001515.GA580714@lothringen \
    --to=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@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).