From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: edumazet@google.com, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, nic_swsd@realtek.com,
netdev@vger.kernel.org, ken.milmore@gmail.com
Subject: Re: [PATCH net] Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already"
Date: Tue, 21 May 2024 09:50:27 +0000 [thread overview]
Message-ID: <171628502791.29879.3558658720405565780.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9b5b6f4c-4f54-4b90-b0b3-8d8023c2e780@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 15 May 2024 08:18:01 +0200 you wrote:
> This reverts commit 7274c4147afbf46f45b8501edbdad6da8cd013b9.
>
> Ken reported that RTL8125b can lock up if gro_flush_timeout has the
> default value of 20000 and napi_defer_hard_irqs is set to 0.
> In this scenario device interrupts aren't disabled, what seems to
> trigger some silicon bug under heavy load. I was able to reproduce this
> behavior on RTL8168h. Fix this by reverting 7274c4147afb.
>
> [...]
Here is the summary with links:
- [net] Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already"
https://git.kernel.org/netdev/net/c/eabb8a9be1e4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-05-21 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 6:18 [PATCH net] Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" Heiner Kallweit
2024-05-15 12:23 ` Eric Dumazet
2024-05-16 21:10 ` Ken Milmore
2024-05-16 21:31 ` Ken Milmore
2024-05-20 13:50 ` Heiner Kallweit
2024-05-20 15:55 ` Ken Milmore
2024-05-20 19:54 ` Simon Horman
2024-05-21 9:50 ` patchwork-bot+netdevbpf [this message]
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=171628502791.29879.3558658720405565780.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=ken.milmore@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).