This bug is awaiting verification that the linux-nvidia-
tegra/6.8.0-1001.1 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to
'verification-done-noble-linux-
** Changed in: linux (Ubuntu)
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/2045560
Title:
TCP memory leak, slow network (arm64)
To manage notification
This bug is awaiting verification that the linux-
riscv-6.5/6.5.0-45.45.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
riscv-6.5' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-fips/6.8.0-38.38+fips1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If t
@nklya
> you mentioned here that jammy 6.5 kernel will be backported as well.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045560/comments/17
>
> However, in list of updates coming to this ticket I see only
> “jammy-linux-aws-6.8”. Will it be added later?
Funnily enough, I looked thi
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1023.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.5' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-44.44.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.5' to 'verifica
This bug is awaiting verification that the linux-
oracle-6.5/6.5.0-1026.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
oracle-6.5' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-38.38.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
riscv-6.8' to 'verification-done-jammy-li
@philcox you mentioned here that jammy 6.5 kernel will be backported as well.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045560/comments/17
However, in list of updates coming to this ticket I see only “jammy-
linux-aws-6.8”. Will it be added later?
--
You received this bug notificati
This bug is awaiting verification that the linux-oracle/6.8.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oracle' to 'verification-done-
noble-linux-oracle'. If
This bug is awaiting verification that the linux-riscv/6.8.0-38.38.1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-riscv' to 'verification-done-noble-
linux-riscv'. If th
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1009.9~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
nvidia-6.8' to 'verification-done-jammy-l
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.1
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-
lowlatency/6.5.0-44.44.1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-mantic-linux-lowlatency' to
'verification-done-mantic-linux-l
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1008.8~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-i
This bug is awaiting verification that the linux-
gcp-6.5/6.5.0-1024.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
gcp-6.5' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2006.6 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-38.38.1~22.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-
azure-6.8/6.8.0-1010.10~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
azure-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-44.44~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.5' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1026.27
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'.
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1023.24 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to
'verification-done-jammy-linux-nvi
This bug is awaiting verification that the linux-oracle/6.5.0-1026.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-oracle' to 'verification-done-
mantic-linux-oracle'.
This bug is awaiting verification that the linux-laptop/6.5.0-1019.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-laptop' to 'verification-done-
mantic-linux-laptop'.
This bug is awaiting verification that the linux-aws/6.5.0-1023.23
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the pr
This bug is awaiting verification that the linux-aws/6.5.0-1023.23
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the pr
This bug is awaiting verification that the linux-azure/6.5.0-1024.25
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-
hwe-6.8/6.8.0-38.38~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.8' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-ibm/6.8.0-1008.8 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-noble-linux-ibm' to 'verification-done-noble-linux-
ibm'. If the probl
This bug is awaiting verification that the linux-nvidia/6.8.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-nvidia' to 'verification-done-
noble-linux-nvidia'. If
This bug is awaiting verification that the linux-gke/6.8.0-1006.9 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-noble-linux-gke' to 'verification-done-noble-linux-
gke'. If the probl
This bug was fixed in the package linux - 6.8.0-38.38
---
linux (6.8.0-38.38) noble; urgency=medium
* noble/linux: 6.8.0-38.38 -proposed tracker (LP: #2068318)
* race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with
Azure Standard_A2_v2 instance (LP: #206
This bug was fixed in the package linux - 6.5.0-44.44
---
linux (6.5.0-44.44) mantic; urgency=medium
* mantic/linux: 6.5.0-44.44 -proposed tracker (LP: #2068341)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(
This bug is awaiting verification that the linux-nvidia-
lowlatency/6.8.0-1009.9.1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-nvidia-
lowlatency' to 'verification-done
Cool, thank you for details, all clear now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560
Title:
TCP memory leak, slow network (arm64)
To manage notifications about this bug go to:
https:/
@nklya
The 6.5 and 6.8 based jammy kernels have received this patch as well.
The 6.2 based jammy kernel is no longer supported so it will not be
receiving these patches.
The way that the jammy 6.5/6.8 kernels work are, they are backports of
the newer series kernels. So, for noble (24.04) for exa
Hi,
I’m wondering if this bugfix will be backported for Jammy / 22.04?
Right now as I see only Mantic/Noble is planned in status.
Jammy has 6.2/6.5 kernels and they’re affected by this.
P.S. Also, it feels that priority might be higher. In some cases it
creates pretty serious network related pr
This bug is awaiting verification that the linux/6.8.0-38.38 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.5.0-44.44 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.8.0-38.38 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exist
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560
Title:
TCP memory leak, slow network (arm64)
To manage notifica
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
B
The review for this change has been sent out. It is:
https://lists.ubuntu.com/archives/kernel-team/2024-May/151087.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560
Title:
TCP memory leak
Two patches are actually needed for this fix. From the 6.8.y stable
branch, the following two patches cherry-pick and build clean on the
generic ubuntu mantic (6.5), and noble (6.8) kernels. I will perform
some more testing and send these out for review.
The two patches are:
d2fa3493811ecd49f15
I've looked at this issue in some detail now. The initial memory leak
was introduced in linux kernel version v6.0, and the fix was introduced
in the v6.9 kernel version. This means that the 6.5, and 6.8 based
ubuntu kernels will contain this memory leak.
I will submit a fix for the generic 6.8,
** Changed in: linux-signed-aws-6.2 (Ubuntu)
Assignee: (unassigned) => Philip Cox (philcox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560
Title:
TCP memory leak, slow network (arm64)
The bug report can be found here:
https://lore.kernel.org/netdev/vi1pr01mb42407d7947b2ea448f1e04efd1...@vi1pr01mb4240.eurprd01.prod.exchangelabs.com/
The subsequently produced patch (not by me!) to fix this can be found
here:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/
Hi Jonathan,
Thanks for all the information and the deep dive into this issue! Please
post the link to the kernel bug report here when it's ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560
I've been digging into this and this appears to be a regression
introduced by the following patch
https://github.com/torvalds/linux/commit/3cd3399dd7a84 which was first
released in Linux 6.0.0.
The bug is not a memory leak but rather a bug in how memory usage is
counted. Excess memory is not actua
As another "me too" situation, I'm seeing the same phenomenon, though on
Rocky 9 rather than Ubuntu and on older kernels (5.14). Reporting
details here on the off chance this provides some insight.
Hardware: Ampere Altra Max 128 cores (aarch64), ConnectX6-DX NICs (2 x dual
100G port)
Kernel versi
53 matches
Mail list logo
