FS#69475 - [Linux 5.10.11.arch1-1] Flow regression
Attached to Project:
Arch Linux
Opened by Torus (T0t0) - Saturday, 30 January 2021, 20:20 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 10:11 GMT
Opened by Torus (T0t0) - Saturday, 30 January 2021, 20:20 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 10:11 GMT
|
Details
Description:
Flow regression with the fiber (divided by about 50%). I made a test with the lts core and I found a normal flow rate. I've noticed that since version 5.10 Additional info: * package version(s) > 5.10.11.arch1-1 * lspci > Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) Steps to reproduce: Using the last kernel. |
This task depends upon
Edit: I had done the flow test on a Sunday during rush hour. After several tests, it is a flow rate divided by 10.
[1] https://wiki.archlinux.org/index.php/Unofficial_user_repositories#miffe
Bad new linux-mainline is also bugged.
If so [1] should help to solve this problem.
[1] https://git.archlinux.org/svntogit/packages.git/commit/?h=packages/linux&id=282c90d1e14ef7dd0f56f8c8192ba1c830e906ad
If that does not have the issue the instructions then build 5.10 again without any patches. If that does have the issue you would then bisect to locate what upstream commit causes the issue.
If you build 5.10 and it does not have the issue then it may be a packaging issue.
I have no idea how to compile a kernel without PKGBUILD.
It's amazing that there are no other users with this problem.
You could use linux-git, you would need to change the config to that for 5.9 or 5.10 and it uses scripts/setlocalversion --save-scmversion so the uname output will not be updated during the bisection.
(link removed)
The bug only appears from version 5.10 onwards
That is why you have to test the built 5.9 and confirm it is good and test the built 5.10 and confirm it is bad. Otherwise you can get a false result due to a broken build system.
You were building on /tmp and ran out of disk space?
Edit:
Updated PKGBUILD to produce smaller packages. You should still copy linux-git off /tmp to avoid the build failure.
Please email me using the address for the file owner to keep this thread from growing very long while bisecting the issue.
[](https://lore.kernel.org/r/20200709132344.760-5-john.ogness@linutronix.de).
Is there a lot of output in dmesg that could make printk the limit on network flowrate?
Edit: With linux-lts, I have only one entry with dmesg -Hk: 'kauditd_printk_skb: 5 callbacks suppressed'. With the test, I have no more entries (except the ufw lines).
printk_skb.txt (3.1 KiB)
I do not know what your flow tester involves so this may not be viable but if you disable ufw and or firejail does that fix the flow rate issue?
Do you have an explanation?
I do not know what ufw is logging but try and reduce it. There is also ulogd [1] which I believe would avoid logging to dmesg.
[1] https://www.netfilter.org/projects/ulogd/
Otherwise, do you think you should keep this ticket open?