From: Michal Pecio <michal.pecio@gmail.com>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [BUG] NOHZ tick-stop error: local softirq work is pending
Date: Sat, 29 Aug 2026 20:14:01 +0200 [thread overview]
Message-ID: <20260829201401.2b107cd1.michal.pecio@gmail.com> (raw)
Hi,
I'm getting these warnings on current mainline. Quite reliable trigger
is I/O load (like md5sum /dev/sda) on an otherwise idle system:
[ 86.082138] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 117.959975] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 121.054544] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 121.988208] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 143.932445] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 156.083120] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 156.685222] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 156.789911] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
[ 158.986070] NOHZ tick-stop error: local softirq work is pending, handler #40!!!
I see it consistently across several reboots. I also did two v7.2
boots with the same workload and these ran cleanly 10 minutes each,
so it looks like a merge window regression.
The system is ordinary x86-64 with CONFIG_PREEMPT.
grep HZ .config:
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 is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
It seems bisectable, but maybe somebody has better ideas?
Regards,
Michal
next reply other threads:[~2026-08-29 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 18:14 Michal Pecio [this message]
2026-08-30 5:56 ` Thomas Gleixner
2026-08-30 8:35 ` Michal Pecio
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=20260829201401.2b107cd1.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@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®