[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA+QEuRZXkPjN+=mgeLL8znYsMEpsk8a5omJ+eC1y-0SFnSrCg@mail.gmail.com>
Date: Fri, 27 Jun 2025 15:31:23 +0100
From: Zak Kemble <zakkemble@...il.com>
To: Doug Berger <opendmb@...il.com>, Florian Fainelli <florian.fainelli@...adcom.com>
Cc: netdev@...r.kernel.org
Subject: BUG: bcmgenet transmit queue timeout lockup 6.15+
Hi, I have a Raspberry Pi CM4 setup as a NAT router with the bcmgenet
ethernet on the LAN side and an RTL8111 on the WAN (although any
adapter will work fine for this). I've found that downloading
something from the internet to a PC on the LAN while also running
iperf3 from the Pi to the same or another PC at the same time will
cause transmit queue timeouts and queue 1 locks up. Network
connectivity is lost and a reboot is needed to fix it. Doing only one
at a time is fine.
6.14.11-v8+ bcm2711_build
https://github.com/raspberrypi/linux/actions/runs/15676052461 is fine,
no timeouts.
6.15.3-v8+ bcm2711_build
https://github.com/raspberrypi/linux/actions/runs/15845884292 is
affected.
The same occurs when I backport the latest driver code (just
bcmgenet.c and bcmgenet.h IIRC) from kernel 6.16 to 6.12.
Jun 26 14:32:06 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 1: transmit queue 0 timed out 2004 ms
Jun 26 14:32:08 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 1: transmit queue 4 timed out 2004 ms
Jun 26 14:32:09 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 3 timed out 2004 ms
Jun 26 14:32:10 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 1: transmit queue 3 timed out 2892 ms
Jun 26 14:32:11 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 3 timed out 3884 ms
Jun 26 14:32:12 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 0: transmit queue 1 timed out 2208 ms
Jun 26 14:32:13 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 1: transmit queue 1 timed out 3232 ms
Jun 26 14:32:14 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 1: transmit queue 1 timed out 4224 ms
Jun 26 14:32:15 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 5216 ms
Jun 26 14:32:16 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 6208 ms
Jun 26 14:32:17 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 7200 ms
Jun 26 14:32:18 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 8224 ms
Jun 26 14:32:19 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 9216 ms
Jun 26 14:32:20 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 10208 ms
Jun 26 14:32:21 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 11200 ms
Jun 26 14:32:22 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 12224 ms
Jun 26 14:32:23 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 13216 ms
Jun 26 14:32:24 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 3: transmit queue 1 timed out 14208 ms
Jun 26 14:32:25 router.localnet kernel: bcmgenet fd580000.ethernet
lan0: NETDEV WATCHDOG: CPU: 1: transmit queue 1 timed out 15200 ms
Thanks,
Zak
Powered by blists - more mailing lists