[Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels
Nick Rosbrook
2037667 at bugs.launchpad.net
Fri Feb 28 20:40:48 UTC 2025
I re-verified the fix using systemd 249.11-0ubuntu3.15 from jammy-
proposed:
First, I confirmed that the bug was present without systemd from jammy-
proposed:
ubuntu at ubuntu:~$ uname -a
Linux ubuntu 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15 19:18:46 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
ubuntu at ubuntu:~$ apt policy systemd
systemd:
Installed: 249.11-0ubuntu3.12
Candidate: 249.11-0ubuntu3.12
Version table:
*** 249.11-0ubuntu3.12 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
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://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ubuntu at ubuntu:~$ sudo su
[sudo] password for ubuntu:
root at ubuntu:/home/ubuntu# cat > /etc/netplan/10-tun.yaml <<EOF
network:
renderer: networkd
version: 2
tunnels:
tun0:
mode: ip6gre
local: fe80::1
remote: 2001:dead:beef::2
tun1:
mode: vti6
local: fe80::2
remote: 2001:dead:beef::3
EOF
root at ubuntu:/home/ubuntu# netplan apply
** (generate:1790): WARNING **: 15:36:41.563: Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan
configuration should NOT be accessible by others.
** (generate:1790): WARNING **: 15:36:41.563: Permissions for /etc/netplan/10-tun.yaml are too open. Netplan configuration should NOT be accessible by others.
WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not running.
** (process:1788): WARNING **: 15:36:41.813: Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan
configuration should NOT be accessible by others.
** (process:1788): WARNING **: 15:36:41.813: Permissions for
/etc/netplan/10-tun.yaml are too open. Netplan configuration should NOT
be accessible by others.
** (process:1788): WARNING **: 15:36:41.923: Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan
configuration should NOT be accessible by others.
** (process:1788): WARNING **: 15:36:41.923: Permissions for
/etc/netplan/10-tun.yaml are too open. Netplan configuration should NOT
be accessible by others.
** (process:1788): WARNING **: 15:36:41.923: Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan
configuration should NOT be accessible by others.
** (process:1788): WARNING **: 15:36:41.923: Permissions for /etc/netplan/10-tun.yaml are too open. Netplan configuration should NOT be accessible by others.
root at ubuntu:/home/ubuntu# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 00:16:3e:15:fd:6c brd ff:ff:ff:ff:ff:ff
3: ip6tnl0 at NONE: <NOARP> mtu 1452 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/tunnel6 :: brd :: permaddr c69b:b23a:35a9::
4: ip6gre0 at NONE: <NOARP> mtu 1448 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/gre6 :: brd :: permaddr 3e04:7898:c320::
5: ip6_vti0 at NONE: <NOARP> mtu 1332 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/tunnel6 :: brd :: permaddr 42d0:b07b:13ce::
root at ubuntu:/home/ubuntu# journalctl -u systemd-networkd -b --since "1 min ago" --no-pager
Feb 28 15:36:41 ubuntu systemd-networkd[441]: tun0: netdev could not be created: Invalid argument
Feb 28 15:36:41 ubuntu systemd-networkd[441]: tun1: netdev could not be created: Invalid argument
Feb 28 15:36:41 ubuntu systemd-networkd[441]: enp5s0: Re-configuring with /etc/systemd/network/10-enp5s0.network
Feb 28 15:36:41 ubuntu systemd-networkd[441]: enp5s0: DHCP lease lost
Feb 28 15:36:41 ubuntu systemd-networkd[441]: enp5s0: DHCPv6 lease lost
Feb 28 15:36:42 ubuntu systemd-networkd[441]: enp5s0: DHCPv4 address 10.19.111.16/24 via 10.19.111.1
Then, I installed systemd from jammy-proposed:
root at ubuntu:/home/ubuntu# cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF
root at ubuntu:/home/ubuntu# apt update && apt install -t jammy-proposed systemd
Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:2 http://archive.ubuntu.com/ubuntu jammy-proposed InRelease [279 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted i386 Packages [4,732 B]
Get:4 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted amd64 Packages [559 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted Translation-en [107 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted amd64 DEP-11 Metadata [212 B]
Get:7 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted DEP-11 48x48 Icons [29 B]
Get:8 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted DEP-11 64x64 Icons [29 B]
Get:9 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted DEP-11 64x64 at 2 Icons [29 B]
Get:10 http://archive.ubuntu.com/ubuntu jammy-proposed/restricted amd64 c-n-f Metadata [420 B]
Get:11 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages [98.8 kB]
Get:12 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages [364 kB]
Hit:13 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:14 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:15 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:16 http://archive.ubuntu.com/ubuntu jammy-proposed/main Translation-en [75.1 kB]
Get:17 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 DEP-11 Metadata [5,720 B]
Get:18 http://archive.ubuntu.com/ubuntu jammy-proposed/main DEP-11 48x48 Icons [1,625 B]
Get:19 http://archive.ubuntu.com/ubuntu jammy-proposed/main DEP-11 64x64 Icons [2,436 B]
Get:20 http://archive.ubuntu.com/ubuntu jammy-proposed/main DEP-11 64x64 at 2 Icons [29 B]
Get:21 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 c-n-f Metadata [1,740 B]
Get:22 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse amd64 Packages [9,488 B]
Get:23 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse i386 Packages [2,464 B]
Get:24 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse Translation-en [2,720 B]
Get:25 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse amd64 DEP-11 Metadata [212 B]
Get:26 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse DEP-11 48x48 Icons [29 B]
Get:27 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse DEP-11 64x64 Icons [29 B]
Get:28 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse DEP-11 64x64 at 2 Icons [29 B]
Get:29 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse amd64 c-n-f Metadata [208 B]
Get:30 http://archive.ubuntu.com/ubuntu jammy-proposed/universe i386 Packages [32.4 kB]
Get:31 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages [85.1 kB]
Get:32 http://archive.ubuntu.com/ubuntu jammy-proposed/universe Translation-en [30.0 kB]
Get:33 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 DEP-11 Metadata [1,448 B]
Get:34 http://archive.ubuntu.com/ubuntu jammy-proposed/universe DEP-11 48x48 Icons [4,982 B]
Get:35 http://archive.ubuntu.com/ubuntu jammy-proposed/universe DEP-11 64x64 Icons [8,742 B]
Get:36 http://archive.ubuntu.com/ubuntu jammy-proposed/universe DEP-11 64x64 at 2 Icons [29 B]
Get:37 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 c-n-f Metadata [1,344 B]
Fetched 1,679 kB in 2s (951 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
36 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libnss-systemd libpam-systemd libsystemd0 systemd-oomd systemd-sysv systemd-timesyncd
Suggested packages:
systemd-container libtss2-rc0
The following packages will be upgraded:
libnss-systemd libpam-systemd libsystemd0 systemd systemd-oomd systemd-sysv systemd-timesyncd
7 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Need to get 5,310 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 libnss-systemd amd64 249.11-0ubuntu3.15 [133 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 systemd-timesyncd amd64 249.11-0ubuntu3.15 [31.2 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 systemd-sysv amd64 249.11-0ubuntu3.15 [10.5 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 systemd-oomd amd64 249.11-0ubuntu3.15 [34.8 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 libpam-systemd amd64 249.11-0ubuntu3.15 [203 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 systemd amd64 249.11-0ubuntu3.15 [4,581 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 libsystemd0 amd64 249.11-0ubuntu3.15 [317 kB]
Fetched 5,310 kB in 0s (14.0 MB/s)
(Reading database ... 182844 files and directories currently installed.)
Preparing to unpack .../0-libnss-systemd_249.11-0ubuntu3.15_amd64.deb ...
Unpacking libnss-systemd:amd64 (249.11-0ubuntu3.15) over (249.11-0ubuntu3.12) ...
Preparing to unpack .../1-systemd-timesyncd_249.11-0ubuntu3.15_amd64.deb ...
Unpacking systemd-timesyncd (249.11-0ubuntu3.15) over (249.11-0ubuntu3.12) ...
Preparing to unpack .../2-systemd-sysv_249.11-0ubuntu3.15_amd64.deb ...
Unpacking systemd-sysv (249.11-0ubuntu3.15) over (249.11-0ubuntu3.12) ...
Preparing to unpack .../3-systemd-oomd_249.11-0ubuntu3.15_amd64.deb ...
Unpacking systemd-oomd (249.11-0ubuntu3.15) over (249.11-0ubuntu3.12) ...
Preparing to unpack .../4-libpam-systemd_249.11-0ubuntu3.15_amd64.deb ...
Unpacking libpam-systemd:amd64 (249.11-0ubuntu3.15) over (249.11-0ubuntu3.12) ...
Preparing to unpack .../5-systemd_249.11-0ubuntu3.15_amd64.deb ...
Unpacking systemd (249.11-0ubuntu3.15) over (249.11-0ubuntu3.12) ...
Preparing to unpack .../6-libsystemd0_249.11-0ubuntu3.15_amd64.deb ...
Unpacking libsystemd0:amd64 (249.11-0ubuntu3.15) over (249.11-0ubuntu3.12) ...
Setting up libsystemd0:amd64 (249.11-0ubuntu3.15) ...
Setting up systemd (249.11-0ubuntu3.15) ...
Setting up systemd-timesyncd (249.11-0ubuntu3.15) ...
Setting up systemd-oomd (249.11-0ubuntu3.15) ...
Setting up systemd-sysv (249.11-0ubuntu3.15) ...
Setting up libnss-systemd:amd64 (249.11-0ubuntu3.15) ...
Setting up libpam-systemd:amd64 (249.11-0ubuntu3.15) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.9) ...
root at ubuntu:/home/ubuntu# apt policy systemd
systemd:
Installed: 249.11-0ubuntu3.15
Candidate: 249.11-0ubuntu3.15
Version table:
*** 249.11-0ubuntu3.15 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
249.11-0ubuntu3.12 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
249.11-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Finally, I confirmed the fix:
root at ubuntu:/home/ubuntu# journalctl -u systemd-networkd -b --since "1 min ago" --no-pager
Feb 28 15:37:44 ubuntu systemd[1]: Stopping Network Configuration...
Feb 28 15:37:44 ubuntu systemd-networkd[441]: enp5s0: DHCPv6 lease lost
Feb 28 15:37:44 ubuntu systemd[1]: systemd-networkd.service: Deactivated successfully.
Feb 28 15:37:44 ubuntu systemd[1]: Stopped Network Configuration.
Feb 28 15:37:44 ubuntu systemd[1]: Starting Network Configuration...
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun1: netdev ready
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun0: netdev ready
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: enp5s0: Link UP
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: enp5s0: Gained carrier
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: lo: Link UP
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: lo: Gained carrier
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: enp5s0: Gained IPv6LL
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: Enumeration completed
Feb 28 15:37:44 ubuntu systemd[1]: Started Network Configuration.
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: enp5s0: DHCPv4 address 10.19.111.16/24 via 10.19.111.1
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun0: Link UP
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun0: Gained carrier
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun0: Gained IPv6LL
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun1: Link UP
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun1: Gained carrier
Feb 28 15:37:44 ubuntu systemd-networkd[2654]: tun1: Gained IPv6LL
root at ubuntu:/home/ubuntu# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 00:16:3e:15:fd:6c brd ff:ff:ff:ff:ff:ff
3: ip6tnl0 at NONE: <NOARP> mtu 1452 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/tunnel6 :: brd :: permaddr c69b:b23a:35a9::
4: ip6gre0 at NONE: <NOARP> mtu 1448 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/gre6 :: brd :: permaddr 3e04:7898:c320::
5: ip6_vti0 at NONE: <NOARP> mtu 1332 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/tunnel6 :: brd :: permaddr 42d0:b07b:13ce::
6: tun0 at NONE: <NOARP,UP,LOWER_UP> mtu 1448 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/gre6 fe80::1 brd 2001:dead:beef::2 permaddr eac5:7286:349b::
7: tun1 at NONE: <NOARP,UP,LOWER_UP> mtu 1332 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/tunnel6 fe80::2 brd 2001:dead:beef::3 permaddr d208:fd4a:4abc::
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2037667
Title:
Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
tunnels
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Triaged
Status in systemd source package in Jammy:
Fix Committed
Bug description:
[Impact]
We noticed that some of Netplan's integration tests started to fail on
Jammy. These tests will try to create ip6gre and vti6 virtual
interfaces and systemd-networkd is failing to create them starting on
kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
last revision where it works. So, some change between 5.15.0-82.91 and
5.15.0-83.92 is causing this regression.
[Test Plan]
This test can be done on any Jammy machine. It is best to test in a
VM.
# Create a netplan file that creates 2 tunnels:
$ cat > /etc/netplan/10-tun.yaml <<EOF
network:
renderer: networkd
version: 2
tunnels:
tun0:
mode: ip6gre
local: fe80::1
remote: 2001:dead:beef::2
tun1:
mode: vti6
local: fe80::2
remote: 2001:dead:beef::3
EOF
$ netplan apply
# Check with "ip link" that both tun0 and tun1 *were not created* and
check networkd for errors:
$ ip link
$ journalctl -u systemd-networkd
On an affected system, we would see logs like:
Sep 28 17:04:40 jammy systemd-networkd[360]: tun0: netdev could not be created: Invalid argument
Sep 28 17:04:40 jammy systemd-networkd[360]: tun1: netdev could not be created: Invalid argument
On a patched system, we should see the tun0 and tun1 devices, and the
above logs should not be present.
[Where problems could occur]
The proposed patch is a minimized version of an upstream patch. The
result is a patch that disables the "generate_mac" flag for non-ether
devices. Hence, any problems related to this patch would be related to
systemd-networkd creating certain types of net devices.
[Original Description]
We noticed that some of Netplan's integration tests started to fail on
Jammy. These tests will try to create ip6gre and vti6 virtual
interfaces and systemd-networkd is failing to create them starting on
kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
last revision where it works. So, some change between 5.15.0-82.91 and
5.15.0-83.92 is causing this regression.
How to reproduce the issue:
# Launch a jammy cloud VM:
lxc launch images:ubuntu/jammy/cloud jammy --vm
lxc shell jammy
# Create a netplan file that creates 2 tunnels:
cat > /etc/netplan/10-tun.yaml <<EOF
network:
renderer: networkd
version: 2
tunnels:
tun0:
mode: ip6gre
local: fe80::1
remote: 2001:dead:beef::2
tun1:
mode: vti6
local: fe80::2
remote: 2001:dead:beef::3
EOF
# Apply the configuration
netplan apply
# Check with "ip link" that both tun0 and tun1 *were not created* and
check networkd for errors:
journalctl -u systemd-networkd
Sep 28 17:04:40 jammy systemd-networkd[360]: tun0: netdev could not be created: Invalid argument
Sep 28 17:04:40 jammy systemd-networkd[360]: tun1: netdev could not be created: Invalid argument
# Download, install and boot on kernel 5.15.0-82.91
wget http://ie.archive.ubuntu.com/ubuntu/pool/main/l/linux-
signed/linux-image-5.15.0-82-generic_5.15.0-82.91_amd64.deb
http://ie.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-
modules-5.15.0-82-generic_5.15.0-82.91_amd64.deb
dpkg -i *.deb
grub-reboot '1>2' && reboot
# Check with "ip link" again that both tun0 and tun1 were created
# Reboot again to go back to the most recent kernel and check with "ip link" that both tun0 and tun1 were not created.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Sep 29 12:52 seq
crw-rw---- 1 root audio 116, 33 Sep 29 12:52 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: lxd
CloudName: lxd
CloudPlatform: lxd
CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
DistroRelease: Ubuntu 22.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci: Error: [Errno 2] No such file or directory: 'lspci'
Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
RelatedPackageVersions:
linux-restricted-modules-5.15.0-84-generic N/A
linux-backports-modules-5.15.0-84-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.15.0-84-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 2/2/2022
dmi.bios.release: 0.0
dmi.bios.vendor: EDK II
dmi.bios.version: unknown
dmi.board.name: LXD
dmi.board.vendor: Canonical Ltd.
dmi.board.version: pc-q35-8.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-8.0
dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-8.0
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+subscriptions
More information about the foundations-bugs
mailing list