From: patchwork-bot+netdevbpf@kernel.org
To: Justin Chen <justin.chen@broadcom.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net, andrew+netdev@lunn.ch,
bcm-kernel-feedback-list@broadcom.com,
florian.fainelli@broadcom.com, opendmb@gmail.com, nb@tipi-net.de
Subject: Re: [PATCH net v3 0/3] net: bcmgenet: fix queue lock up
Date: Fri, 10 Apr 2026 03:40:13 +0000 [thread overview]
Message-ID: <177579241354.1854480.4016027802423644177.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260406175756.134567-1-justin.chen@broadcom.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 6 Apr 2026 10:57:53 -0700 you wrote:
> We have been seeing reports of logs like this.
> # [ 39.713199] bcmgenet 1001300000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 2 timed out 7991 ms
> [ 41.761198] bcmgenet 1001300000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 2 timed out 10039 ms
> [ 43.745198] bcmgenet 1001300000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 2 timed out 12023 ms
> [ 45.729198] bcmgenet 1001300000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 2 timed out 14007 ms
>
> We have two issues. The persistent queue timeouts and the eventual lock up of the entire transmit.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] net: bcmgenet: fix off-by-one in bcmgenet_put_txcb
https://git.kernel.org/netdev/net/c/57f3f53d2c9c
- [net,v3,2/3] net: bcmgenet: fix leaking free_bds
https://git.kernel.org/netdev/net/c/3f3168300efb
- [net,v3,3/3] net: bcmgenet: fix racing timeout handler
https://git.kernel.org/netdev/net/c/5393b2b5bee2
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-04-10 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 17:57 [PATCH net v3 0/3] net: bcmgenet: fix queue lock up Justin Chen
2026-04-06 17:57 ` [PATCH net v3 1/3] net: bcmgenet: fix off-by-one in bcmgenet_put_txcb Justin Chen
2026-04-06 17:57 ` [PATCH net v3 2/3] net: bcmgenet: fix leaking free_bds Justin Chen
2026-04-06 17:57 ` [PATCH net v3 3/3] net: bcmgenet: fix racing timeout handler Justin Chen
2026-04-10 3:40 ` 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=177579241354.1854480.4016027802423644177.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=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.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