From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"Ziegler, Andreas" <ziegler.andreas@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Subject: Re: 6.1-rt: NOHZ tick-stop error: local softirq work is pending
Date: Thu, 27 Feb 2025 14:43:04 +0100 [thread overview]
Message-ID: <20250227134304.xLBfiIC7@linutronix.de> (raw)
In-Reply-To: <7cace5d70278f8ae1debe8cb8d392fb3f59291ff.camel@siemens.com>
On 2025-02-26 23:23:30 [+0100], Florian Bezdeka wrote:
> > NAPI threads? You have RPS enabled by any chance?
> > Would commit
> > dad6b97702639 ("net: Allow to use SMP threads for backlog NAPI.")
> > 80d2eefcb4c84 ("net: Use backlog-NAPI to clean up the defer_list.")
>
> With NAPI threads I meant the kernel threads driving the NAPI poll
> which can be activated by "echo 1 > /sys/class/net/$device/threaded"
>
> RPS is build configuration wise enabled but not configured.
If RPS is disabled then this might be something else.
> As Felix already reported, backporting the mentioned commits to 6.1
> would require some manual work. Simply picking all the dependencies
> seems too much for now. Will have a look again...
Can you reproduce this on a later (more recent) kernel? What are the
steps to reproduce this?
Sebastian
next prev parent reply other threads:[~2025-02-27 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 9:32 6.1-rt: NOHZ tick-stop error: local softirq work is pending Bezdeka, Florian
2025-02-24 11:55 ` Sebastian Andrzej Siewior
2025-02-25 15:16 ` Florian Bezdeka
2025-02-26 9:17 ` Sebastian Andrzej Siewior
2025-02-26 17:41 ` MOESSBAUER, Felix
2025-02-26 22:23 ` Florian Bezdeka
2025-02-27 13:43 ` Sebastian Andrzej Siewior [this message]
2025-02-28 16:28 ` Florian Bezdeka
2025-02-28 16:41 ` Jan Kiszka
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=20250227134304.xLBfiIC7@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=ziegler.andreas@siemens.com \
/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