[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
@Stefan: I haven't reproduced the issue on Artful and I don't have an
environment to do so. The original issue is for the HWE kernel on Xenial
and only for that I can perform verification.
--
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/1748408
Title:
Servers going OOM after updating kernel from 4.10 to 4.13
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
We are seeing this on multiple servers after upgrading from previous 4.10
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory
is continously decreasing at a high rate and the servers start swapping and
finally OOMing services within days. With the 4.10 kernel, decrease of free
memory is slower and stabilizes after a while.
Latest kernel tested is linux-image-4.13.0-32-generic but the issue
also affects older kernels from that series, tested back to linux-
image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.
The servers are running as OpenStack controller nodes using either
Ocata or Pike UCA plus ceph. See attached graph for the memory
behaviour.
== Fix ==
2b9478ffc550("i40e: Fix memory leak related filter programming status")
62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")
== Regression Potential ==
Low. Limited to i40e and fix existing regression.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 9 09:45:50 2018
ProcEnviron:
LANGUAGE=en_US:
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Running the -proposed kernel on two machines now, will provide the
results in a couple of days.
--
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/1748408
Title:
Servers going OOM after updating kernel from 4.10 to 4.13
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
We are seeing this on multiple servers after upgrading from previous 4.10
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory
is continously decreasing at a high rate and the servers start swapping and
finally OOMing services within days. With the 4.10 kernel, decrease of free
memory is slower and stabilizes after a while.
Latest kernel tested is linux-image-4.13.0-32-generic but the issue
also affects older kernels from that series, tested back to linux-
image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.
The servers are running as OpenStack controller nodes using either
Ocata or Pike UCA plus ceph. See attached graph for the memory
behaviour.
== Fix ==
2b9478ffc550("i40e: Fix memory leak related filter programming status")
62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")
== Regression Potential ==
Low. Limited to i40e and fix existing regression.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 9 09:45:50 2018
ProcEnviron:
LANGUAGE=en_US:
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Proposed kernels show the same improved behaviour as the earlier test
kernels.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1748408
Title:
Servers going OOM after updating kernel from 4.10 to 4.13
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
We are seeing this on multiple servers after upgrading from previous 4.10
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory
is continously decreasing at a high rate and the servers start swapping and
finally OOMing services within days. With the 4.10 kernel, decrease of free
memory is slower and stabilizes after a while.
Latest kernel tested is linux-image-4.13.0-32-generic but the issue
also affects older kernels from that series, tested back to linux-
image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.
The servers are running as OpenStack controller nodes using either
Ocata or Pike UCA plus ceph. See attached graph for the memory
behaviour.
== Fix ==
2b9478ffc550("i40e: Fix memory leak related filter programming status")
62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")
== Regression Potential ==
Low. Limited to i40e and fix existing regression.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 9 09:45:50 2018
ProcEnviron:
LANGUAGE=en_US:
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
@Joseph: I did test 4.15.2, but some things are failing, in particular docker because of lacking AUFS support, so I need to build a kernel myself I guess, which will take a bit. Also note that I'm seeing this on Xenial machines, didn't test with Artful. We used to run them with the 4.10 HWE kernels because they offer improved performance in some areas compared to the stock 4.4. kernel. Started seeing these issue after HWE switched to 4.13 a couple of weeks ago. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Ok, nevermind the aufs issue, I got that resolved. Should have some results with mainline kernels in a couple of days. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
So here are the first results: 4.11.0-041100-generic #201705041534 - not affected 4.12.0-041200-generic #201707022031 - affected 4.13.0-041300-generic #201709031731 - affected 4.13.16-041316-generic #201711240901 - affected Results for newer kernels are not so clear, they do not fail as fast as previous ones, but they do still fill up memory and - later - swap slowly. The rate is so slow however, that it will probably take weeks to come to some definitive results here. Thus my next step, unless there is a better proposal, will be starting to bisect from 4.11 to 4.12, git expects 13 steps for that. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
** Tags added: kernel-bug-exists-upstream -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Sorry for the delay, bisecting took longer than planned, but I now have the result: 6964e53f55837b0c49ed60d36656d2e0ee4fc27b is the first bad commit commit 6964e53f55837b0c49ed60d36656d2e0ee4fc27b Author: Jacob Keller Date: Mon Jun 12 15:38:36 2017 -0700 i40e: fix handling of HW ATR eviction The bad news is that this patch pretty certainly isn't directly the culprit, as it only fixes (and re-enables) features that seem to have been messed up earlier. So not sure how to proceed now, probably need to discuss this with upstream developers? -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
A colleague found that this seems to be a known issue: https://www.spinics.net/lists/netdev/msg458258.html and the fix should be https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/drivers/net/ethernet/intel/i40e/i40e_txrx.c?id=2b9478ffc550f17c6cd8c69057234e91150f5972 I will try cherry-picking this onto 4.13, not sure why it never seems to have been pulled into the stable branch. Also not sure why we are still seeing issues with >= 4.14, very likely a completely different issue there, but I think we'll be fine if we get 4.13 fixed for now. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Reading the thread further, we seem to need two patches, see https://www.spinics.net/lists/netdev/msg462051.html, so I'm going to add bc6d6fd2f916a0794ae4c44b28e14e2d172e05e0 into the build, too. Will try that on top of b32038eb34ee42fd8056f99f88652270f6667996 (tag: Ubuntu-4.13.0-32.35). I also tested the "ethtool --set-priv-flags flow-director-atr off" option and it seems to slow down the leak similar to >= 4.14 kernels. So either that fixes only part of the issue or we have a different one that only got masked up to now. Third option would be using the upstream i40e driver instead, testing with 2.3.4 currently and that also seems to resolve the issue. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
O.k., confirming that this series of patches fixes the issue: ~/linux$ git log --oneline|head -3 bc6d6fd2f916 i40e: Add programming descriptors to cleaned_count 69949b3bd674 i40e: Fix memory leak related filter programming status b32038eb34ee UBUNTU: Ubuntu-4.13.0-32.35 Can you build the same thing on top of the latest 4.13 set? Seems some special gcc foo is needed to make the retpoline stuff working there -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
After running for a couple of days, it seems that we are still seeing the slow memory leak similar to what was noticed in >= 4.14 earlier with the patched kernel. But it won't be possible for me to bisect at that rate. @Joseph: Getting a patched current 4.13 still would be nice, getting instructions for how to build such a kernel would be even nicer. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
The test kernel solves the issue in the same way as my own kernel earlier, i.e. we still seem to have a very slow running memory leak with this kernel. I'm also seeing this slow leak when I replace the in-tree i40e driver by an upstream version (2.3.4), so either it is unrelated or contained in both. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
The slow leak will probably be tolerable for the time being, having those two patches added to the kernel would surely be a pretty valuable step that I think should be done now. My target still is Xenial with the hwe kernel, though. If you need to go via Artful to fix that, well, go ahead. -- 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/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049195] [NEW] Wifi missing after upgrade to 6.5 kernel
Public bug reported: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "kernel-log.txt" https://bugs.launchpad.net/bugs/2049195/+attachment/5738725/+files/kernel-log.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049195 Title: Wifi missing after upgrade to 6.5 kernel Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077159] [NEW] i40e interfaces renamed after upgrade from hwe-6.5
Public bug reported: Server running Ubuntu 22.04.4 LTS Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1: 3: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 4: eno5: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6: mtu 1500 qdisc mq master mgmt state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3 Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3: 3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0np0 4: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 5: enp101s0f1np1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1np1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2np2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8np3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3np3 Expected result: Static network configuration via netplan keeps working after the upgrade. Actual result: Static network configuration is no longer applied for the interface that changed their name. ** Affects: linux-meta-hwe-6.8 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - i40e interfaces renamed after upgrade from hwe-6.8 + i40e interfaces renamed after upgrade from hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2077159 Title: i40e interfaces renamed after upgrade from hwe-6.5 Status in linux-meta-hwe-6.8 package in Ubuntu: New Bug description: Server running Ubuntu 22.04.4 LTS Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1: 3: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 4: eno5: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6: mtu 1500 qdisc mq master mgmt state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3 Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3: 3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0np0
[Kernel-packages] [Bug 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5
This does not seem to work as expected: user@rtr001:~$ sudo apport-collect 2077159 Please open this authorization page: (https://launchpad.net/+authorize-token?oauth_token=XXX&allow_permission=DESKTOP_INTEGRATION) in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press Enter after authorizing in your browser. Package linux-meta-hwe-6.8 not installed and no hook available, ignoring *** Updating problem report No additional information collected. Press any key to continue... No pending crash reports. Try --help for more information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2077159 Title: i40e interfaces renamed after upgrade from hwe-6.5 Status in linux-meta-hwe-6.8 package in Ubuntu: Incomplete Bug description: Server running Ubuntu 22.04.4 LTS Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1: 3: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 4: eno5: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6: mtu 1500 qdisc mq master mgmt state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3 Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3: 3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0np0 4: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 5: enp101s0f1np1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1np1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2np2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8np3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3np3 Expected result: Static network configuration via netplan keeps working after the upgrade. Actual result: Static network configuration is no longer applied for the interface that changed their name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.8/+bug/2077159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5
** Changed in: linux-meta-hwe-6.8 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2077159 Title: i40e interfaces renamed after upgrade from hwe-6.5 Status in linux-meta-hwe-6.8 package in Ubuntu: New Bug description: Server running Ubuntu 22.04.4 LTS Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1: 3: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 4: eno5: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6: mtu 1500 qdisc mq master mgmt state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3 Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3: 3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0np0 4: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 5: enp101s0f1np1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1np1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2np2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8np3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3np3 Expected result: Static network configuration via netplan keeps working after the upgrade. Actual result: Static network configuration is no longer applied for the interface that changed their name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.8/+bug/2077159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5
apport information
** Tags added: apport-collected jammy uec-images
** Description changed:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps working
after the upgrade.
- Actual result: Static network configuration is no longer applied for the
- interface that changed their name.
+ Actual result: Static network configuration is no longer applied for the
interface that changed their name.
+ ---
+ ProblemType: Bug
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
+ crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu82.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5json:
+ {
+"result": "skip"
+ }
+ CloudArchitecture: x86_64
+ CloudID: none
+ CloudName: none
+ CloudPlatform: none
+ CloudSubPlatform: config
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2023-12-04 (260 days ago)
+ InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ MachineType: Supermicro SYS-5019D-FN8TP
+ Package: linux (not installed)
+ PciMultimedia:
+
+ ProcEnviron:
+ TERM=screen
+ PATH=(custom, no user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcFB: 0 astdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
+ ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
+ RebootRequiredPkgs: Error: path contained symlinks.
+ RelatedPackageVersions:
+ linux-restricted-modules-6.5.0-21-generic N/A
+ linux-backports-modules-6.5.0-21-generic N/A
+ linux-firmware20220329.git681281e4-0ubuntu3.31
+ RfKill: Error: [Errno 2] No such file
[Kernel-packages] [Bug 2077159] HookError_ubuntu.txt
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807773/+files/HookError_ubuntu.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVer
[Kernel-packages] [Bug 2077159] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807774/+files/Lspci.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restric
[Kernel-packages] [Bug 2077159] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807775/+files/Lspci-vt.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-
[Kernel-packages] [Bug 2077159] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807776/+files/Lsusb.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restric
[Kernel-packages] [Bug 2077159] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/580/+files/Lsusb-t.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-re
[Kernel-packages] [Bug 2077159] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807778/+files/Lsusb-v.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-re
[Kernel-packages] [Bug 2077159] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807779/+files/ProcCpuinfo.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
[Kernel-packages] [Bug 2077159] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807780/+files/ProcCpuinfoMinimal.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackag
[Kernel-packages] [Bug 2077159] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807782/+files/ProcModules.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
[Kernel-packages] [Bug 2077159] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807781/+files/ProcInterrupts.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersion
[Kernel-packages] [Bug 2077159] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807784/+files/WifiSyslog.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
li
[Kernel-packages] [Bug 2077159] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807783/+files/UdevDb.txt
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restr
[Kernel-packages] [Bug 2049195] Re: Wifi missing after upgrade to 6.5 kernel
I can confirm that with 6.5.0.17.17~22.04.9 the issue no longer appears for me, too. ** Changed in: linux-meta-hwe-6.5 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049195 Title: Wifi missing after upgrade to 6.5 kernel Status in linux-meta-hwe-6.5 package in Ubuntu: Fix Released Bug description: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2085835] Re: "Predictable Network Interface Naming" suddenly changed the name from enp96s0f0 to enp96s0f0np0 causing outage
The 6.8.0 kernel likely has been installed via the linux-generic- hwe-22.04 package, can you show apt policy for that one, too? -- 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/2085835 Title: "Predictable Network Interface Naming" suddenly changed the name from enp96s0f0 to enp96s0f0np0 causing outage Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: On three identical servers - sleds in a blade chassis. the NIC name of one of the servers suddenly changed, causing an outage. The netplan config could not assign IP to the interface due to the name change. enp96s0f0 to enp96s0f0np0 The two other servers still have the enp96s0f0 name. No BIOS or other configuration change is detectable between the three systems. Firmware, software - all the same I tried to debug this issue myself, but it turned out to be a very niche and complicated topic. I went to submit an issue on https://github.com/systemd/systemd/issues, but they only accept issues for newer versions. System info: dundts@mongodb-rs2:~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 dundts@mongodb-rs2:~$ apt-cache policy systemd system: Installiert: 249.11-0ubuntu3.11 Installationskandidat: 249.11-0ubuntu3.12 Versionstabelle: 249.11-0ubuntu3.12 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages *** 249.11-0ubuntu3.11 100 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages dundts@mongodb-rs2:~$ sudo dmesg | grep i40e [sudo] password for dundts: [3.657531] i40e: Intel(R) Ethernet Connection XL710 Network Driver [3.658208] i40e: Copyright (c) 2013 - 2019 Intel Corporation. [3.715866] i40e :60:00.0: fw 3.1.54559 api 1.5 nvm 3.2d 0x8b4b 1.1767.0 [8086:37d3] [152d:8a40] [3.720222] i40e :60:00.0: MAC address: d8:c4:97:4c:66:ae [3.720558] i40e :60:00.0: FW LLDP is enabled [3.732613] i40e :60:00.0: Added LAN device PF0 bus=0x60 dev=0x00 func=0x00 [3.733075] i40e :60:00.0: Features: PF-id[0] VFs: 32 VSIs: 66 QP: 32 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA [3.788671] i40e :60:00.1: fw 3.1.54559 api 1.5 nvm 3.2d 0x8b4b 1.1767.0 [8086:37d3] [152d:8a40] [3.804478] i40e :60:00.1: MAC address: d8:c4:97:4c:66:af [3.804964] i40e :60:00.1: FW LLDP is enabled [3.839982] i40e :60:00.1 eth1: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: None [3.851939] i40e :60:00.1: Added LAN device PF1 bus=0x60 dev=0x00 func=0x01 [3.877994] i40e :60:00.1: Features: PF-id[1] VFs: 32 VSIs: 66 QP: 32 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA [4.065330] i40e :60:00.0 enp96s0f0np0: renamed from eth0 [4.096320] i40e :60:00.1 enp96s0f1np1: renamed from eth1 dundts@mongodb-rs2:~$ sudo udevadm info /sys/class/net/enp96s0f0np0 P: /devices/pci:5d/:5d:00.0/:5e:00.0/:5f:03.0/:60:00.0/net/enp96s0f0np0 L: 0 E: DEVPATH=/devices/pci:5d/:5d:00.0/:5e:00.0/:5f:03.0/:60:00.0/net/enp96s0f0np0 E: INTERFACE=enp96s0f0np0 E: IFINDEX=2 E: SUBSYSTEM=net E: USEC_INITIALIZED=4079509 E: ID_MM_CANDIDATE=1 E: ID_NET_NAMING_SCHEME=v249 E: ID_NET_NAME_MAC=enxd8c4974c66ae E: ID_OUI_FROM_DATABASE=Quanta Computer Inc. E: ID_NET_NAME_PATH=enp96s0f0np0 E: ID_BUS=pci E: ID_VENDOR_ID=0x8086 E: ID_MODEL_ID=0x37d3 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Intel Corporation E: ID_MODEL_FROM_DATABASE=Ethernet Connection X722 for 10GbE SFP+ E: ID_PATH=pci-:60:00.0 E: ID_PATH_TAG=pci-_60_00_0 E: ID_NET_DRIVER=i40e E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=enp96s0f0np0 E: NM_UNMANAGED=1 E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp96s0f0np0 E: TAGS=:systemd: E: CURRENT_TAGS=:system: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2104134] Re: ovs/linuxbridge jobs running on ubuntu noble broken with latest kernel 6.8.0-56.58
Note that doing a reboot in a CI job is not an easy task. Our current workaround is to use images that were built before the new pkg was released. -- 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/2104134 Title: ovs/linuxbridge jobs running on ubuntu noble broken with latest kernel 6.8.0-56.58 Status in neutron: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: A commit[1] got backported to ubuntu noble kernel[2] which had an issue, Fix is already available[3] in build[4] but not yet released. So all our ovs/linuxbridge/fullstack/functional jobs running on ubuntu noble are impacted. Master, 2025.1 or any releases running ovs jobs on noble are impacted. Errors like below can be seen in these jobs Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR neutron.agent.l3.agent # Completed by iptables_manager Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR neutron.agent.l3.agent ; Stdout: ; Stderr: Warning: Extension MARK revision 0 not supported, missing kernel module? Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR neutron.agent.l3.agent ip6tables-restore v1.8.10 (nf_tables): unknown option "--set-xmark" Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR neutron.agent.l3.agent Error occurred at line: 28 Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR neutron.agent.l3.agent Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. example failures:- https://c00e7c7cf4b62bf664e8-ab9cdbb0aa9d61bf3167c27c9fa17003.ssl.cf1.rackcdn.com/openstack/fca5ab13dc674574953941a6e09eb935/testr_results.html https://cf3ed66a65616b206bcc-d1906ed32ef7c4deba2ba4dd3d406176.ssl.cf1.rackcdn.com/openstack/071c7b51c1d448348e6e5dd4da8f4c9c/testr_results.html https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_f60/openstack/f607cb89924e40019d37a617c6b009e8/testr_results.html Until the new kernel with fix is released we need to remove the broken noble images and pause new builds like it was done in past for same issue in jammy https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091990/comments/3 [1] https://github.com/torvalds/linux/commit/0bfcb7b71e735560077a42847f69597ec7dcc326 [2] https://bugs.launchpad.net/kernel-sru-workflow/+bug/2098244 [3] https://github.com/torvalds/linux/commit/306ed1728e8438caed30332e1ab46b28c25fe3d8 [4] https://bugs.launchpad.net/kernel-sru-workflow/+bug/2102529 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2104134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
