Hi Paul, Frederic, ever since this recent patch got merged into all recent stables: https://lore.kernel.org/all/[email protected]/ ..
.. I am seeing this happen a lot now causing rcutorture failures: "NOHZ tick-stop error: local softirq work is pending" It looks like the "tick-stop error" as local_bh_blocked always returns false on !PREEMPT_RT, so that patch itself seems correct. However, it appears the string in console-badness.sh is different: console-badness.sh:grep -v 'NOHZ tick-stop error: Non-RCU local softirq work is pending, handler' So the string in the script needs an update? Also, considering that it is being grep -v'ed out, any background on why this message is not bad and any history? Why is softirq work pending when the tick is stopped? thanks, - Joel
