** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
Title:
Kernel 4.15.0-36 network performance regression
To
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
Title:
Kernel 4.15.0-36 network performance regression
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => Fix Committed
** Description changed:
Hardware:
HP DL380 Gen 7 server with Gigabit interface.
Ubuntu release: 18.04.1
Since upgrading from 4.15.0-33 to 4.15.0-36, I have noticed a dramatic
slowdown in TCP over
Sorry for the accidental status change. I can't revert. Not sure why I
was able to do that. Verified fix in -37.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
Title:
Kernel 4.15.0-36
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
Title:
Kernel 4.15.0-36 network performance regression
To
For the record:
I've tracked this down to a pair of commmits, the first of which landed
in -35 (released in -36) the second in -37.
The first:
https://lkml.org/lkml/2018/6/5/765
The second:
https://lkml.org/lkml/2018/6/24/161
In the interim state, it was casting a u64 to a u32, which truncates
Ok - for anyone that isn't used to installing kernels from proposed. It
helps to install linux-image-generic and not linux-image-X-generic
in order to pull in the modules package.
Tested and verified - network speeds are back to normal in -37.
--
You received this bug notification because
For whatever reason, after installing linux-image-4.15.0-37-generic the
system boots up fine but doesn't appear to initialize the motherboard's
built in realtek network adapter so there is no network connectivity to
test.
Is there a missing dependency in the package that needs to be installed
to
I installed the proposed kernel on a remote host and rebooted but of
course the host didn't come back online for who only knows what reason.
I'll post an update in a few hours once I have a chance to get my hands
on it.
--
You received this bug notification because you are a member of Ubuntu
Thanks for all the testing. If this bug is fixed in -proposed, then the
fix is already applied to the Ubuntu kernel and will be released in the
next round of updates on November 12th.
The fix will be in the 4.15.0-37 or newer kernel.
Can others affected by this bug confirm that the proposed
Tested the first bisected version, on commit
003ae88ae88d48643e71dc69c18d4eda598339d5, problem still present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
Title:
Kernel 4.15.0-36 network
Just tested with the proposed build, the problem is fixed with the
proposed kernel 4.15.0-37 on my server.
Does this mean the problem is Ubuntu specific? When will the proposed
version be released? Do you still think it's necessary to test against
the mainline?
--
You received this bug
I started a kernel bisect between 4.15.0-34 and 4.15.0-36. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
003ae88ae88d48643e71dc69c18d4eda598339d5
The test kernel can be downloaded from:
I'm seeing similar behavior on multiple physical hosts running
4.15.0-36-generic. The TCP window size only appears to grow very
slightly (from initial of 224 to around 1400) during the entire length
of the transfer.
Downgrading to 4.15.0-34-generic fixes the issue for me - TCP window
size
I can perform a kernel bisect to identify the commit that introduced
this regression. Before starting the bisect, can you test the -proposed
kernel:
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
** Also affects: linux (Ubuntu Bionic)
It might also be good to test the latest mainline kernel to see if this
issue also exists upstream, if it is fixed upstream and/or if this
regression is Ubuntu specific.
The mainline kernel is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7
Some documentation regarding
Also want to add that once we downgraded back to 4.15.0-33 the problem
went away. Rebooting back to 4.15.0-36 the problem reappears.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
Title:
I can't use apport-collect since it requires IPv4 connection to
internet.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
We had a similar issue with our MySQL server farm (seven dedicated MySQL
servers). Replication was very slow, falling behind for no apparent
reason. We were reaching 24 hours of lag! We never had that kind of lag
before. A couple of minutes at the most.
Long story short, we rebooted to 4.15.0.34
19 matches
Mail list logo
