Comment 7 for bug 1847892

Any specific params you want for iperf BTW?

I ran some basic tests against a VM after all: it might have lost a few %, but wireless is so slow that it's not going to make any meaningful difference.

[ ID] Interval Transfer Bandwidth Reads Dist(bin=16.0K)
[ 4] 0.0000-11.4354 sec 45.8 MBytes 33.6 Mbits/sec 22348 22341:6:0:1:0:0:0:0
[ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45314
[ 4] 0.0000-10.3068 sec 68.6 MBytes 55.9 Mbits/sec 35906 35901:2:3:0:0:0:0:0
[ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45316
[ 4] 0.0000-10.3491 sec 71.6 MBytes 58.1 Mbits/sec 35522 35512:2:4:4:0:0:0:0
[ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45324
[ 4] 0.0000-10.3927 sec 75.1 MBytes 60.6 Mbits/sec 35410 35397:7:3:2:1:0:0:0
[ 4] local 192.168.1.34 port 5001 connected with 192.168.1.33 port 45326
[ 4] 0.0000-10.3910 sec 59.8 MBytes 48.2 Mbits/sec 30683 30675:3:4:1:0:0:0:0

The first run may well have had the wifi at low power: the client had just been woken up a couple of minutes earlier, but it tends to dial that back quite quickly. I left it in for completeness.

An rsync right after the last run was 6,906,424.15 bytes/sec, so ~58.65 Mb/s. I think that's a good indicator of being able to trust the historical data from it.

I may have the machine in here at some point in the next few days, and will test that too if so. For 1795116, the performance in that scenario (~6' and LOS) was fine: it wasn't that the driver was broken across the board, it just wasn't managing power properly so it fell apart if conditions weren't perfect.
(Not saying this is the same bug, just reminding myself what a result like that means).

I still need to boot into 16.04 / etc to try and find a working kernel. AFAICT 16.04.6 shipped with one that has the post-1795116 fix in it, so it should be okay off a USB. If not though I'll have to get creative, as there isn't a spare partition on that machine to install to.

My notes show 4.15.0-55 as the first version with the old bug fixed. It would be helpful if there was a reasonable way for me to just install that, since there are multiple dist-upgrade's worth of other changes since then.
While that specific kernel would be ideal from a testing standpoint, isn't there somewhere I can just grab the current Bionic kernel from, as a dpkg, and just install the damn thing without having to jump through any hoops? Surely there must be a better system in place already than randomly guessing at versions or doing builds on a system that is totally unsuitable for such tasks. :(