From: patchwork-bot+netdevbpf@kernel.org
To: Asmaa Mnebhi <asmaa@nvidia.com>
Cc: davem@davemloft.net, f.fainelli@gmail.com, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, tbogendoerfer@suse.de,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, davthompson@nvidia.com
Subject: Re: [PATCH net v4] mlxbf_gige: Fix intermittent no ip issue
Date: Sun, 07 Jan 2024 15:20:21 +0000 [thread overview]
Message-ID: <170464082183.11926.8134099660170040578.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240105155946.23121-1-asmaa@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 5 Jan 2024 10:59:46 -0500 you wrote:
> Although the link is up, there is no ip assigned on setups with high background
> traffic. Nothing is transmitted nor received. The RX error count keeps on
> increasing. After several minutes, the RX error count stagnates and the
> GigE interface finally gets an ip.
>
> The issue is that mlxbf_gige_rx_init() is called before phy_start().
> As soon as the RX DMA is enabled in mlxbf_gige_rx_init(), the RX CI reaches the max
> of 128, and becomes equal to RX PI. RX CI doesn't decrease since the code hasn't
> ran phy_start yet.
> Bring the PHY up before starting the RX.
>
> [...]
Here is the summary with links:
- [net,v4] mlxbf_gige: Fix intermittent no ip issue
https://git.kernel.org/netdev/net/c/ef210ef85d5c
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-01-07 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 15:59 [PATCH net v4] mlxbf_gige: Fix intermittent no ip issue Asmaa Mnebhi
2024-01-07 15:20 ` 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=170464082183.11926.8134099660170040578.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asmaa@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tbogendoerfer@suse.de \
/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).