From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Tao Wang <tao03.wang@horizon.auto>
Cc: alexandre.torgue@foss.st.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v2] net: stmmac: fix transmit queue timed out after resume
Date: Thu, 15 Jan 2026 22:04:39 +0100 [thread overview]
Message-ID: <6a946edc-297e-469a-8d91-80430d88f3e5@bootlin.com> (raw)
In-Reply-To: <aWlCs5lksxfgL6Gi@shell.armlinux.org.uk>
Hi,
>
> I've just run iperf3 in both directions with the kernel I had on the
> board (based on 6.18.0-rc7-net-next+), and stmmac really isn't looking
> particularly great - by that I mean, iperf3 *failed* spectacularly.
>
> First, running in normal mode (stmmac transmitting, x86 receiving)
> it's only capable of 210Mbps, which is nowhere near line rate.
>
> However, when running iperf3 in reverse mode, it filled the stmmac's
> receive queue, which then started spewing PAUSE frames at a rate of
> knots, flooding the network, and causing the entire network to stop.
> It never recovered without rebooting.
>
> Trying again on 6.19.0-rc4-net-next+,
>
> stmmac transmitting shows the same dire performance:
>
> [ ID] Interval Transfer Bitrate Retr Cwnd
> [ 5] 0.00-1.00 sec 24.2 MBytes 203 Mbits/sec 0 230 KBytes
> [ 5] 1.00-2.00 sec 25.5 MBytes 214 Mbits/sec 0 230 KBytes
> [ 5] 2.00-3.00 sec 25.0 MBytes 210 Mbits/sec 0 230 KBytes
> [ 5] 3.00-4.00 sec 25.5 MBytes 214 Mbits/sec 0 230 KBytes
> [ 5] 4.00-5.00 sec 25.1 MBytes 211 Mbits/sec 0 230 KBytes
> [ 5] 5.00-6.00 sec 25.1 MBytes 211 Mbits/sec 0 230 KBytes
> [ 5] 6.00-7.00 sec 25.7 MBytes 215 Mbits/sec 0 230 KBytes
> [ 5] 7.00-8.00 sec 25.2 MBytes 212 Mbits/sec 0 230 KBytes
> [ 5] 8.00-9.00 sec 25.3 MBytes 212 Mbits/sec 0 346 KBytes
> [ 5] 9.00-10.00 sec 25.4 MBytes 213 Mbits/sec 0 346 KBytes
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-10.00 sec 252 MBytes 211 Mbits/sec 0 sender
> [ 5] 0.00-10.02 sec 250 MBytes 210 Mbits/sec receiver
>
> stmmac receiving shows the same problem:
>
> [ ID] Interval Transfer Bitrate
> [ 5] 0.00-1.00 sec 64.1 MBytes 537 Mbits/sec
> [ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec
> [ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec
> [ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec
> [ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec
> [ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec
> [ 5] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec
> [ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec
> [ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec
> ^C[ 5] 9.00-9.43 sec 0.00 Bytes 0.00 bits/sec
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval Transfer Bitrate
> [ 5] 0.00-9.43 sec 0.00 Bytes 0.00 bits/sec sender
> [ 5] 0.00-9.43 sec 64.1 MBytes 57.0 Mbits/sec receiver
> iperf3: interrupt - the client has terminated
Heh, I was able to reproduce something similar on imx8mp, that has an
imx-dwmac (dwmac 4/5 according to dmesg) :
DUT to x86
Connecting to host 192.168.2.1, port 5201
[ 5] local 192.168.2.13 port 54744 connected to 192.168.2.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 0.00 Bytes 0.00 bits/sec 2 1.41 KBytes
[ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 1 1.41 KBytes
x86 to DUT :
Reverse mode, remote host 192.168.2.1 is sending
[ 5] local 192.168.2.13 port 47050 connected to 192.168.2.1 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 112 MBytes 935 Mbits/sec
[ 5] 1.00-2.00 sec 112 MBytes 936 Mbits/sec
[ 5] 2.00-3.00 sec 112 MBytes 936 Mbits/sec
Nothing as bas as what you face, but there's defintely something going
on there. "good" news is that it worked in v6.19-rc1, I have a bisect
ongoing.
I'll update once I have homed-in on something.
Maxime
next prev parent reply other threads:[~2026-01-15 21:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 7:02 [PATCH net Resend] " Tao Wang
2026-01-13 4:05 ` Jakub Kicinski
2026-01-14 11:00 ` [PATCH net v2] " Tao Wang
2026-01-14 11:26 ` Russell King (Oracle)
2026-01-15 7:08 ` Tao Wang
2026-01-15 12:09 ` Russell King (Oracle)
2026-01-15 19:40 ` Russell King (Oracle)
2026-01-15 21:04 ` Maxime Chevallier [this message]
2026-01-15 21:35 ` Maxime Chevallier
2026-01-16 0:50 ` Russell King (Oracle)
2026-01-16 13:37 ` Russell King (Oracle)
2026-01-16 18:08 ` Russell King (Oracle)
2026-01-16 18:27 ` Maxime Chevallier
2026-01-16 19:22 ` Russell King (Oracle)
2026-01-16 20:57 ` Russell King (Oracle)
2026-01-17 17:06 ` Jakub Kicinski
2026-01-17 20:50 ` Russell King (Oracle)
2026-01-16 7:29 ` Tao Wang
2026-01-15 3:16 ` Jakub Kicinski
2026-01-15 7:19 ` Tao Wang
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=6a946edc-297e-469a-8d91-80430d88f3e5@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tao03.wang@horizon.auto \
/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
all inboxes | Powered by JetHome®