Re: [BUG] NOHZ tick-stop error: local softirq work is pending

[Thomas Gleixner <tglx@kernel.org>]

On Sat, Aug 29 2026 at 20:14, Michal Pecio wrote:
> 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.
>
>
> It seems bisectable, but maybe somebody has better ideas?

It's likely the issue being discussed here:

   https://lore.kernel.org/lkml/20260824105523.GA4121620@noisy.programming.kicks-ass.net/

There is a revert queued which probably will cure it for you unless you
are using Rust drivers. Plus a fix for the remaining Rust specific issue
is on the way.

Thanks,

        tglx