Hello, My upload speed has reduced to about 50Mbps when I upgraded my kernel to 5.9.1. When I boot with 5.8.16 kernel, my upload speed is back to ~450Mbps. Download speed is the same in both cases ~940Mbps Hardware environment : Intel ax200 connected to a 802.11ax network. Distribution : Latest Manjaro
The bug is still present in 5.10rc1 Someone else have the same exact bug with an Intel Corporation Wireless-AC 9560 [Jefferson Peak ] (rev 10)
Facing this issue on 5.9.4. I'm using the Intel 9260 Wireless card.
The issue is still present on 5.9.6 No problem on 5.8.18 but unfortunately it's EOL now.
Same issue on 5.9.y (Arch Linux) using an Intel AX200 card. Managed to narrow down the problem to the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3d5b459ba0e3788ab471e8cb98eee89964a9c5e8 Full upload speed is restored after doing a revert. Consequently, I also found that disabling TSO on my wireless card on a clean 5.9.6 kernel also works: ethtool -K wlp3s0 tso off My other PC with a Realtek RT8812BU USB wireless adapter has no such regression in 5.9, so it seems it might actually be an Intel driver issue.
I confirm that disabling TSO restores full upload speed on 5.9.6 hardware : Intel AX200
*** Bug 210157 has been marked as a duplicate of this bug. ***
Disabling TSO also fixes this issue on 5.9.9 for: Intel Corporation Wireless-AC 9560 [Jefferson Peak ] (rev 10)
As Arvin mentionned, reverting that commit or just disabling TSO works. Tested on 5.9.y and 5.10rc
I am new to bugzilla and arch in general. Just here to report that I had this same problem. Fixed by downgrading to 5.8.14. https://bbs.archlinux.org/viewtopic.php?pid=1935313#p1935313 Will try turning TSO off, but am a hobbyist with no understanding of what TSO is/does. lspci -vv output: http://ix.io/2Fac
can confirm update to 5.9.10 then disable tso -> return to 57MB/s upload speed to home server
Same here on Kernel 5.9.12 with Intel Corporation Wi-Fi 6 AX200 (rev 1a). The workaround in Comment #4 (turning DSO off) works for me too.
I can also confirm this, disabling TSO works. Intel(R) Wireless-AC 9560, REV=0x318 $ uname -a Linux ntb 5.9.9-arch1-1 #1 SMP PREEMPT Wed, 18 Nov 2020 19:52:04 +0000 x86_64 GNU/Linux $ iperf -c x.x.x.253 -d -t 30 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to x.x.x.253, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 4] local x.x.x.x.232 port 59330 connected with x.x.x.253 port 5001 [ 5] local x.x.x.x.232 port 5001 connected with x.x.x.253 port 53598 [ ID] Interval Transfer Bandwidth [ 5] 0.0-30.0 sec 843 MBytes 236 Mbits/sec [ 4] 0.0-30.6 sec 16.2 MBytes 4.45 Mbits/sec $ $ sudo ethtool -K wlo1 tso off $ $ iperf -c cubie2 -d -t 30 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ ------------------------------------------------------------ Client connecting to x.x.x.253, TCP port 5001 TCP window size: 136 KByte (default) ------------------------------------------------------------ [ 4] local x.x.x.232 port 59376 connected with x.x.x.253 port 5001 [ 5] local x.x.x.232 port 5001 connected with x.x.x.253 port 53602 [ ID] Interval Transfer Bandwidth [ 4] 0.0-30.0 sec 114 MBytes 32.0 Mbits/sec [ 5] 0.0-30.0 sec 688 MBytes 192 Mbits/sec
I have the same problem, kernel 5.9.16, ax200 upload speed only 10MB/S kernel 5.8.18, ax200 upload speed can 80MB/S
Following up, this seems to be fixed in 5.10.3+ and possibly a few revisions before that. Fairly sure that all of the 5.9.x kernels exhibited the issue reported.
Spoke too soon - 5.10.4 again needs TSO disabled for full upload performance.
Created attachment 294475 [details] adds regression for ax200 upload https://www.mail-archive.com/netdev@vger.kernel.org/msg379947.html
The issue seems to be fixed in 5.10.5 Can someone please confirm ? Thanks
(In reply to Fibonacci from comment #17) > The issue seems to be fixed in 5.10.5 > Can someone please confirm ? Thanks No, for me it persists on 5.10.5 with AX200.
On Mon, 04 January 2021, you wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=209913 > > youling257@gmail.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Attachment #294475 [details]|0 |1 > is patch| | > Applied this patch on vanilla 5.10.5 sources and can confirm that this patch fixes the regression. Robert
Robert, you mean *reverting* the patch fixed it, right?
Hi, I don't know if archlinux or manjaro team applied a patch or something but I'm not facing this issue anymore since 5.10.5 https://i.imgur.com/UGGh0Wx.png
(In reply to Jo from comment #20) > Robert, you mean *reverting* the patch fixed it, right? No, I included the attached patch (see comment #16) and the changes solved the Problem. Robert
What's the status of this fix? I am seeing this regression on any 5.9+ kernels on Intel 9260 as well unless TSO is turned off. I don't see any commit in mainline currently that appears to reference this.
I think the Intel I225-V controller is having similar issues. Changing to different kernels and disabling TSO doesn't seem to fix download speeds.
(In reply to Robert Hancock from comment #23) > What's the status of this fix? I am seeing this regression on any 5.9+ > kernels on Intel 9260 as well unless TSO is turned off. I don't see any > commit in mainline currently that appears to reference this. The issue is still present, even on vanilla 5.11-rc3 Manjaro team applied the patch in comment #16 for 5.10.y release which fixed the issue on their distro.
The patch is now on its way to mainline/stable: https://patchwork.kernel.org/project/netdevbpf/patch/20210125150949.619309-1-eric.dumazet@gmail.com/
*** Bug 210789 has been marked as a duplicate of this bug. ***
The issue is fixed in 5.11-rc6. The patch in Attachment #294475 [details] made its way to mainline.
The patch is also in the stable queue and should hopefully make it into 5.10.13.
The issue is totally fixed since 5.11-rc6. Changed status to resolved, Thanks everybody.