Sorry Kai - I got swamped by real-life issues.
I finally got the time to look into this a few days ago, and when I went
to check on it then in case a kernel update had fixed things already, it
looks like it has (or at least, mostly so) - peaks are back to 80+, so
that's within wifi variance
Thanks Kai.
Yes, I really want to use Ubuntu kernel to bisect: or at least, I need
the option to be able to - because if the problem is coming from the
Ubuntu patchset, I could spend weeks bisecting mainline and never find
it, whereas if I bisect the Ubuntu tree I'm guaranteed to find it and
that
If you really want to use Ubuntu kernel to bisect, here's the tree:
https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please use mainline kernel tree do do bisection:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847892
Title:
large
Had the affected machine in here (i.e. "where the router is") for other
reasons, so I was able to check those conditions too. As expected, it's
a power / antenna / etc issue:
Linux 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64
Fri 08-Nov-19 03:29
sent 459,277,171 bytes
Okay - the 18.04.3 release I tested in September, which was fine, has
5.0.0-23.
-29 is broken, as mentioned above. That's a pretty narrow window to work with.
I'd prefer it if someone from Canonical took it from here.
(Heck, there are probably few enough commits to that driver in that timeframe
16.04.6 turned out to have 4.15.0-45, which is one of the known-broken
releases. Unsurprisingly, it delivered the same poor results as 5.3.
I'm running low on sensible options here.
I no longer have the bootable 18.04 stick I used before, but I can
create a new one easily enough (as long as I
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] IntervalTransferBandwidth Reads Dist(bin=16.0K)
[ 4] 0.-11.4354
I expect so. I don't usually have a machine available to run as a server
though, hence the preference for rsync.
If you're concerned that the NAS might be the bottleneck, don't be.
That's a sensible point to raise, but it's GbE and saturates it wired.
(To say nothing of the months during which
Is this reproducible via iperf?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847892
Title:
large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel
Status in linux
The dist-upgrades have wiped out all the previous kernels, of course.
The only one left on the machine at all was the 5.0 from 19.04, and that's no
good either. :(
Linux 5.0.0-29-generic #31-Ubuntu SMP Thu Sep 12 13:05:32 UTC 2019 x86_64
Wed 23-Oct-19 04:47
sent 459,277,171 bytes received 35
That machine doesn't have access to launchpad, so until someone fixes
the bugs (referenced out in the other thread) so that "ubuntu-bug -c"
works, I can't provide that info.
Kai - this is a low-power HTPC, with very little disk space. Assuming it
can even clone the kernel, it will likely take
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847892
Title:
large performance regression (~30-40%) in wifi with
Would it be possible for you to do a kernel bisection?
First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$
14 matches
Mail list logo
