| 2023-10-06 18:41:54 |
Andres |
bug |
|
|
added bug |
| 2023-10-06 18:41:54 |
Andres |
attachment added |
|
cat /proc/version_signature https://bugs.launchpad.net/bugs/2038685/+attachment/5707462/+files/version.log |
|
| 2023-10-06 19:00:07 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2023-10-06 19:18:24 |
Andres |
tags |
|
apport-collected bionic |
|
| 2023-10-06 19:18:25 |
Andres |
description |
This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu-kernels/27664/142
Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it.
However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file.
P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel. |
This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu-kernels/27664/142
Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it.
However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file.
P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248
RelatedPackageVersions:
linux-restricted-modules-5.4.0-164-generic N/A
linux-backports-modules-5.4.0-164-generic N/A
linux-firmware 1.173.21
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: bionic
Uname: Linux 5.4.0-164-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc. |
|
| 2023-10-06 19:18:26 |
Andres |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707463/+files/AlsaInfo.txt |
|
| 2023-10-06 19:18:27 |
Andres |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707464/+files/CRDA.txt |
|
| 2023-10-06 19:18:28 |
Andres |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707465/+files/CurrentDmesg.txt |
|
| 2023-10-06 19:18:29 |
Andres |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707466/+files/IwConfig.txt |
|
| 2023-10-06 19:18:30 |
Andres |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707467/+files/Lspci.txt |
|
| 2023-10-06 19:18:32 |
Andres |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707468/+files/ProcCpuinfo.txt |
|
| 2023-10-06 19:18:33 |
Andres |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707469/+files/ProcCpuinfoMinimal.txt |
|
| 2023-10-06 19:18:34 |
Andres |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707470/+files/ProcInterrupts.txt |
|
| 2023-10-06 19:18:35 |
Andres |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707471/+files/ProcModules.txt |
|
| 2023-10-06 19:18:36 |
Andres |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707472/+files/PulseList.txt |
|
| 2023-10-06 19:18:38 |
Andres |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707473/+files/UdevDb.txt |
|
| 2023-10-06 19:18:39 |
Andres |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707474/+files/WifiSyslog.txt |
|
| 2023-10-06 19:20:01 |
Andres |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2023-10-06 19:33:41 |
Andres |
description |
This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu-kernels/27664/142
Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it.
However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file.
P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248
RelatedPackageVersions:
linux-restricted-modules-5.4.0-164-generic N/A
linux-backports-modules-5.4.0-164-generic N/A
linux-firmware 1.173.21
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: bionic
Uname: Linux 5.4.0-164-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc. |
This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu-kernels/27664/142
Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it.
However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file.
P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248
RelatedPackageVersions:
linux-restricted-modules-5.4.0-164-generic N/A
linux-backports-modules-5.4.0-164-generic N/A
linux-firmware 1.173.21
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: bionic
Uname: Linux 5.4.0-164-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-218-generic N/A
linux-backports-modules-4.15.0-218-generic N/A
linux-firmware 1.173.21
RfKill:
Tags: bionic
Uname: Linux 4.15.0-218-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc. |
|
| 2023-10-06 19:33:41 |
Andres |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707475/+files/AlsaInfo.txt |
|
| 2023-10-06 19:33:43 |
Andres |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707476/+files/CurrentDmesg.txt |
|
| 2023-10-06 19:33:44 |
Andres |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707477/+files/IwConfig.txt |
|
| 2023-10-06 19:33:46 |
Andres |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707478/+files/Lspci.txt |
|
| 2023-10-06 19:33:46 |
Andres |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707479/+files/ProcCpuinfo.txt |
|
| 2023-10-06 19:33:47 |
Andres |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707480/+files/ProcCpuinfoMinimal.txt |
|
| 2023-10-06 19:33:48 |
Andres |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707481/+files/ProcInterrupts.txt |
|
| 2023-10-06 19:33:49 |
Andres |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707482/+files/ProcModules.txt |
|
| 2023-10-06 19:33:50 |
Andres |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707483/+files/PulseList.txt |
|
| 2023-10-06 19:33:52 |
Andres |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707484/+files/UdevDb.txt |
|
| 2023-10-06 19:33:54 |
Andres |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/2038685/+attachment/5707485/+files/WifiSyslog.txt |
|
| 2023-10-06 19:36:06 |
Andres |
description |
This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu-kernels/27664/142
Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it.
However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file.
P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-5.4.0-164-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
ProcVersionSignature: Ubuntu 5.4.0-164.181~18.04.1-generic 5.4.248
RelatedPackageVersions:
linux-restricted-modules-5.4.0-164-generic N/A
linux-backports-modules-5.4.0-164-generic N/A
linux-firmware 1.173.21
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: bionic
Uname: Linux 5.4.0-164-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-218-generic N/A
linux-backports-modules-4.15.0-218-generic N/A
linux-firmware 1.173.21
RfKill:
Tags: bionic
Uname: Linux 4.15.0-218-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc. |
This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu-kernels/27664/142
Older Ubuntu distributions come with a kernel image that support eBPF but are not built with a BTF file published (/sys/kernel/btf/vmlinux). This BTF file is crucial when trying to run eBPF programs that were built with CO-RE in mind such that a program can be compiled once and run in any kernel (with some caveats) because the BPF loaders can use the BTF file to relocate addresses of kernel fields at load time for the currently running kernel. In the past I've used the debug symbols that Ubuntu publishes to create BTF files using `pahole` for these older kernels and then re-using that BTF file for any machine running that kernel. This is not ideal but I had managed to work around it.
However, on distributions that are under ESM (Ubuntu 16 + Ubuntu 18) there isn't a debug symbols repository from where to pull the debug symbols packages to build their respective BTF file and no BTF file is generated when the kernel is built. This essentially makes these ESM kernels incompatible with eBPF programs that run using CO-RE (which is more or less the norm nowadays). Based on my conversation on the discourse link above it seems like ideally these ESM kernels should be published with a BTF file.
P.S. I wasn't able to submit this through `ubuntu-bug linux` as it gave me an error saying `Problem in linux-image-4.15.0-218-generic This is not an official Ubuntu package. Please remove any third party package and try again`. I am not sure why it says that as this is a Ubuntu VM downloaded from the Ubuntu site, upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-218-generic root=UUID=c6dbf1d0-3a95-4d98-a0f8-fdea28a5ffc9 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
ProcVersionSignature: Ubuntu 4.15.0-218.229-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-218-generic N/A
linux-backports-modules-4.15.0-218-generic N/A
linux-firmware 1.173.21
RfKill:
Tags: bionic
Uname: Linux 4.15.0-218-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc. |
|
| 2023-10-06 19:51:33 |
Andres |
attachment added |
|
/proc/version_signature https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707486/+files/version.log |
|
| 2023-10-06 19:52:14 |
Andres |
attachment removed |
cat /proc/version_signature https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707462/+files/version.log |
|
|
| 2023-10-06 19:52:54 |
Andres |
attachment removed |
AlsaInfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707463/+files/AlsaInfo.txt |
|
|
| 2023-10-06 19:53:02 |
Andres |
attachment removed |
CRDA.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707464/+files/CRDA.txt |
|
|
| 2023-10-06 19:53:18 |
Andres |
attachment removed |
CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707465/+files/CurrentDmesg.txt |
|
|
| 2023-10-06 19:53:27 |
Andres |
attachment removed |
IwConfig.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707466/+files/IwConfig.txt |
|
|
| 2023-10-06 19:53:35 |
Andres |
attachment removed |
Lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707467/+files/Lspci.txt |
|
|
| 2023-10-06 19:53:45 |
Andres |
attachment removed |
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707469/+files/ProcCpuinfoMinimal.txt |
|
|
| 2023-10-06 19:54:02 |
Andres |
attachment removed |
ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707468/+files/ProcCpuinfo.txt |
|
|
| 2023-10-06 19:54:10 |
Andres |
attachment removed |
ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707470/+files/ProcInterrupts.txt |
|
|
| 2023-10-06 19:54:16 |
Andres |
attachment removed |
ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707471/+files/ProcModules.txt |
|
|
| 2023-10-06 19:54:25 |
Andres |
attachment removed |
PulseList.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707472/+files/PulseList.txt |
|
|
| 2023-10-06 19:54:34 |
Andres |
attachment removed |
UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707473/+files/UdevDb.txt |
|
|
| 2023-10-06 19:54:43 |
Andres |
attachment removed |
WifiSyslog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707474/+files/WifiSyslog.txt |
|
|
| 2023-10-09 14:12:31 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Trusty |
|
| 2023-10-09 14:12:31 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Trusty) |
|
| 2023-10-09 14:12:31 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
| 2023-10-09 14:12:31 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2023-10-09 14:12:31 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Xenial |
|
| 2023-10-09 14:12:31 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Xenial) |
|
