From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linuxppc-dev@lists.ozlabs.org
Subject: ppc64le: `NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #20!!!` when turning off SMT
Date: Tue, 8 Feb 2022 08:32:37 +0100 [thread overview]
Message-ID: <0baca95b-771f-2217-1098-2d0eee568ea7@molgen.mpg.de> (raw)
Dear Linux folks,
On the POWER8 server IBM S822LC running Ubuntu 21.10, Linux 5.17-rc1+
built with
$ grep HZ /boot/config-5.17.0-rc1+
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
once warned about a NOHZ tick-stop error, when I executed `sudo
/usr/sbin/ppc64_cpu --smt=off` (so that KVM would work).
```
$ dmesg
[ 0.000000] Linux version 5.17.0-rc1+
(pmenzel@flughafenberlinbrandenburgwillybrandt.molgen.mpg.de) (Ubuntu
clang version 13.0.0-2, LLD 13.0.0) #1 SMP Fri Jan 28 17:13:04 CET 2022
[…]
[271272.030262] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271272.305726] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271272.549790] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271274.885167] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271275.113896] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271275.412902] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271275.625245] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271275.833107] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271276.041391] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
[271277.244880] NOHZ tick-stop error: Non-RCU local softirq work is
pending, handler #20!!!
```
Kind regards,
Paul
next reply other threads:[~2022-02-08 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 7:32 Paul Menzel [this message]
2022-02-08 7:35 ` Paul Menzel
2022-02-08 13:17 ` Frederic Weisbecker
2022-02-08 13:23 ` Paul A. Clarke
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=0baca95b-771f-2217-1098-2d0eee568ea7@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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®