From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: davem@davemloft.net, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, nic_swsd@realtek.com,
netdev@vger.kernel.org, me@lagy.org
Subject: Re: [PATCH net-next] r8169: fix rare issue with broken rx after link-down on RTL8125
Date: Sat, 14 Oct 2023 00:50:24 +0000 [thread overview]
Message-ID: <169724462401.2191.2301272788594728307.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9edde757-9c3b-4730-be3b-0ef3a374ff71@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Oct 2023 08:51:13 +0200 you wrote:
> In very rare cases (I've seen two reports so far about different
> RTL8125 chip versions) it seems the MAC locks up when link goes down
> and requires a software reset to get revived.
> Realtek doesn't publish hw errata information, therefore the root cause
> is unknown. Realtek vendor drivers do a full hw re-initialization on
> each link-up event, the slimmed-down variant here was reported to fix
> the issue for the reporting user.
> It's not fully clear which parts of the NIC are reset as part of the
> software reset, therefore I can't rule out side effects.
> Therefore apply the fix to net-next only. If no side effects are
> reported, it can be submitted for stable later.
>
> [...]
Here is the summary with links:
- [net-next] r8169: fix rare issue with broken rx after link-down on RTL8125
https://git.kernel.org/netdev/net-next/c/621735f59064
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:[~2023-10-14 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 6:51 [PATCH net-next] r8169: fix rare issue with broken rx after link-down on RTL8125 Heiner Kallweit
2023-10-14 0: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=169724462401.2191.2301272788594728307.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=me@lagy.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).