From: patchwork-bot+netdevbpf@kernel.org
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: opendmb@gmail.com, florian.fainelli@broadcom.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, justin.chen@broadcom.com,
phil@raspberrypi.com, bcm-kernel-feedback-list@broadcom.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] net: bcmgenet: keep RBUF EEE/PM disabled
Date: Thu, 21 May 2026 15:50:17 +0000 [thread overview]
Message-ID: <177937861789.394984.10118621842029368003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260520184320.652053-1-nb@tipi-net.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 May 2026 20:43:20 +0200 you wrote:
> Setting RBUF_EEE_EN | RBUF_PM_EN in RBUF_ENERGY_CTRL breaks the RX
> path on GENET hardware once MAC EEE becomes active. RX traffic stops
> flowing while the link stays up and the usual descriptor/RX error
> counters remain quiet. In that state the MAC still accepts frames
> (rbuf_ovflow_cnt keeps climbing) but RBUF no longer forwards them to
> DMA, so rx_packets is no longer incremented at the netdev level. On
> some boards the corruption ends up as a paging fault in
> skb_release_data via bcmgenet_rx_poll on an LPI exit.
>
> [...]
Here is the summary with links:
- [net] net: bcmgenet: keep RBUF EEE/PM disabled
https://git.kernel.org/netdev/net/c/9a1730245e41
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:[~2026-05-21 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 18:43 [PATCH net] net: bcmgenet: keep RBUF EEE/PM disabled Nicolai Buchwitz
2026-05-20 18:45 ` Florian Fainelli
2026-05-21 15: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=177937861789.394984.10118621842029368003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=phil@raspberrypi.com \
--cc=stable@vger.kernel.org \
/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