[Kernel-packages] [Bug 1922406]
(In reply to Raymond from comment #31) > Renaming/deleting .pvnm file solution stopped working for me after updating > to 20.04. > > Does anyone know how to fix it now? Kernel 5.13.0-39-generic -- 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/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+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 1922406]
Renaming/deleting .pvnm file solution stopped working for me after updating to 20.04. Does anyone know how to fix it 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/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+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 1967593] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575996/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__
[Kernel-packages] [Bug 1967593] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576004/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
[Kernel-packages] [Bug 1967593] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575995/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If
[Kernel-packages] [Bug 1967593] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576008/+files/acpidump.txt ** Description changed: + EDIT: There are no accurate results in the package search, but it is for + the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low + latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not + kernel specific. It must be a problem with configuration, but + reinstalling doesnt fix it. + + This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: user 2189 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: - lono wireless extensions. - - enp1s0no wireless extensions. - - virbr0no wireless extensions. + lono wireless extensions. + + enp1s0no wireless extensions. + + virbr0no wireless extensions. Lsusb: - Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: - /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M - |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M + /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: - linux-restricted-modules-5.15.0-23-generic N/A - linux-backports-modules-5.15.0-23-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu1 + linux-restricted-modules-5.15.0-23-generic N/A + linux-backports-modules-5.15.0-23-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: - + Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: - + _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: user 2189 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 2189 F pulseaudio
[Kernel-packages] [Bug 1967593] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575998/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1:
[Kernel-packages] [Bug 1967593] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576001/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__
[Kernel-packages] [Bug 1967593] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576002/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
[Kernel-packages] [Bug 1967593] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576003/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__
[Kernel-packages] [Bug 1967593] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575999/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1:
[Kernel-packages] [Bug 1967593] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576007/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev
[Kernel-packages] [Bug 1967593] Re: kernel modules going missing after reboot
apport information ** Description changed: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True
[Kernel-packages] [Bug 1967593] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576006/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port
[Kernel-packages] [Bug 1967593] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576000/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev
[Kernel-packages] [Bug 1967593] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575997/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2,
[Kernel-packages] [Bug 1967593] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5576005/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__
[Kernel-packages] [Bug 1967593] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575980/+files/CRDA.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575979/+files/AlsaInfo.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575989/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575993/+files/acpidump.txt ** Also affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-lowlatency (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-hwe-5.15 (Ubuntu) => linux-kvm (Ubuntu) -- 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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
[Kernel-packages] [Bug 1967593] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575991/+files/PulseList.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575978/+files/ProcEnviron.txt ** Description changed: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu80 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 2189 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + IwConfig: + lono wireless extensions. + + enp1s0no wireless extensions. + + virbr0no wireless extensions. + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M + MachineType: QEMU Standard PC (Q35 + ICH9, 2009) + Package: linux (not installed) + ProcFB: 0 virtio_gpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-23-generic N/A + linux-backports-modules-5.15.0-23-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 + RfKill: + + Tags: jammy uec-images + Uname: Linux 5.15.0-23-generic x86_64 +
[Kernel-packages] [Bug 1967593] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575990/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575982/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575976/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575992/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575974/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575975/+files/PaInfo.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575970/+files/CRDA.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575988/+files/ProcEnviron.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575983/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575984/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575986/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575977/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic
[Kernel-packages] [Bug 1967593] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575981/+files/CurrentDmesg.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575973/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575972/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575987/+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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic
[Kernel-packages] [Bug 1967593] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575985/+files/PaInfo.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575971/+files/CurrentDmesg.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
[Kernel-packages] [Bug 1967593] Re: kernel modules going missing after reboot
apport information ** Tags added: apport-collected jammy uec-images ** Description changed: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. - My image was built on top of a cloud-init image, but removing the - recommeded package "cloud-initramfs-copymods" that mounts over modules - didnt work for me. Adding the snd_hda_intel module to the boot config - /etc/initramfs-tools/modules did fix my issue for this module. But how - many others will not be available? + My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu80 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 2189 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + IwConfig: + lono wireless extensions. + + enp1s0no wireless extensions. + + virbr0no wireless extensions. + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M + MachineType: QEMU Standard PC (Q35 + ICH9, 2009) + Package: linux (not installed) + ProcFB: 0 virtio_gpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-23-generic N/A + linux-backports-modules-5.15.0-23-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 + RfKill: + + Tags: jammy uec-images + Uname: Linux 5.15.0-23-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) + UserGroups: libvirt sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 04/01/2014 + dmi.bios.release: 0.0 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.13.0-1ubuntu1.1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-q35-4.2 + dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: + dmi.product.name: Standard PC (Q35 + ICH9, 2009) + dmi.product.version: pc-q35-4.2 + dmi.sys.vendor: QEMU ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1967593/+attachment/5575969/+files/AlsaInfo.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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Kernel-packages] [Bug 1967593] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1967593 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967593/+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 1967593] [NEW] kernel modules going missing after reboot
Public bug reported: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1967593 Title: kernel modules going missing after reboot Status in linux package in Ubuntu: Incomplete Bug description: This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967593/+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 1953674] Re: Screen does not wake up from suspend/does not wake up
*** This bug is a duplicate of bug 1946303 *** https://bugs.launchpad.net/bugs/1946303 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1953674 Title: Screen does not wake up from suspend/does not wake up Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: After upgrading to 21.10 from 21.04 this problem started happening. It does not happen every time I suspend, and it usually happens after suspending for a longer time. After suspending for a longer time, it tends to happen most of the time. I can SSH into the computer, so it is just the display that is not turning back on correctly. Lenovo Thinkpad P51 with an NVIDIA quadro Quadro M1200 journalctl -o short-precise -k -b -1 contained the following messages of interest, which I could not find in other reports: ``` nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x); continuing. [24307.640014] NVRM: GPU at PCI::01:00: GPU-18af74bb-7c72-ff70-e447-87d48378ea20 [24307.640018] NVRM: Xid (PCI::01:00): 79, pid=8828, GPU has fallen off the bus. [24307.640021] NVRM: GPU :01:00.0: GPU has fallen off the bus. [24328.054022] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [repeats several more times] [24328.056767] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [24328.056951] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:0:0:0x000f [24328.056955] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:1:0:0x000f [24328.056959] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:2:0:0x000f [24328.056962] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:3:0:0x000f [24328.056983] nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-0 [24328.056992] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x947d:0:0:0x000f ``` I also noticed a sudo cat /var/crash/_usr_sbin_gdm3.0.uploaded with: 5bed8a34-5852-11ec-b48c-fa163e102db1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1953674/+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 1967582] Re: Focal update: v5.4.181 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.181 upstream stable release + from git://git.kernel.org/ -v5.4.181 upstream stable release -from git://git.kernel.org/ + Makefile.extrawarn: Move -Wunaligned-access to W=1 + HID:Add support for UGTABLET WP5540 + Revert "svm: Add warning message for AVIC IPI invalid target" + serial: parisc: GSC: fix build when IOSAPIC is not set + parisc: Drop __init from map_pages declaration + parisc: Fix data TLB miss in sba_unmap_sg + parisc: Fix sglist access in ccio-dma.c + btrfs: send: in case of IO error log it + platform/x86: ISST: Fix possible circular locking dependency detected + selftests: rtc: Increase test timeout so that all tests run + net: ieee802154: at86rf230: Stop leaking skb's + selftests/zram: Skip max_comp_streams interface on newer kernel + selftests/zram01.sh: Fix compression ratio calculation + selftests/zram: Adapt the situation that /dev/zram0 is being used + ax25: improve the incomplete fix to avoid UAF and NPD bugs + vfs: make freeze_super abort when sync_filesystem returns error + quota: make dquot_quota_sync return errors from ->sync_fs + nvme: fix a possible use-after-free in controller reset during load + nvme-tcp: fix possible use-after-free in transport error_recovery work + nvme-rdma: fix possible use-after-free in transport error_recovery work + drm/amdgpu: fix logic inversion in check + Revert "module, async: async_synchronize_full() on module init iff async is used" + ftrace: add ftrace_init_nop() + module/ftrace: handle patchable-function-entry + arm64: module: rework special section handling + arm64: module/ftrace: intialize PLT at load time + iwlwifi: fix use-after-free + drm/radeon: Fix backlight control on iMac 12,1 + ext4: check for out-of-order index extents in ext4_valid_extent_entries() + ext4: check for inconsistent extents between index and leaf block + ext4: prevent partial update of the extent blocks + taskstats: Cleanup the use of task->exit_code + dmaengine: at_xdmac: Start transfer for cyclic channels in issue_pending + vsock: remove vsock from connected table when connect is interrupted by a signal + mmc: block: fix read single on recovery logic + iwlwifi: pcie: fix locking when "HW not ready" + iwlwifi: pcie: gen2: fix locking when "HW not ready" + netfilter: nft_synproxy: unregister hooks on init error path + net: dsa: lan9303: fix reset on probe + net: ieee802154: ca8210: Fix lifs/sifs periods + ping: fix the dif and sdif check in ping_lookup + bonding: force carrier update when releasing slave + drop_monitor: fix data-race in dropmon_net_event / trace_napi_poll_hit + bonding: fix data-races around agg_select_timer + libsubcmd: Fix use-after-free for realloc(..., 0) + ALSA: hda: Fix regression on forced probe mask option + ALSA: hda: Fix missing codec probe on Shenker Dock 15 + ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw() + ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw_range() + powerpc/lib/sstep: fix 'ptesync' build error + mtd: rawnand: gpmi: don't leak PM reference in error path + block/wbt: fix negative inflight counter when remove scsi device + NFS: LOOKUP_DIRECTORY is also ok with symlinks + NFS: Do not report writeback errors in nfs_getattr() + mtd: rawnand: qcom: Fix clock sequencing in qcom_nandc_probe() + mtd: rawnand: brcmnand: Fixed incorrect sub-page ECC status + scsi: lpfc: Fix pt2pt NVMe PRLI reject LOGO loop + EDAC: Fix calculation of returned address and next offset in edac_align_ptr() + net: sched: limit TC_ACT_REPEAT loops + dmaengine: sh: rcar-dmac: Check for error num after setting mask + copy_process(): Move fd_install() out of sighand->siglock critical section + i2c: brcmstb: fix support for DSL and CM variants +
[Kernel-packages] [Bug 1967582] [NEW] Focal update: v5.4.181 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.181 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- 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/1967582 Title: Focal update: v5.4.181 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.181 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967582/+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 1723948] Re: error -lock in zfs send
** Changed in: zfs Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1723948 Title: error -lock in zfs send Status in Native ZFS for Linux: Fix Released Status in zfs-linux package in Ubuntu: Won't Fix Bug description: zfs send stop working. the process did not produce output. checked by mbuffer log in kernel.log: Oct 15 07:25:53 zfs-cis kernel: [479439.151281] INFO: task zfs:8708 blocked for more than 120 seconds. Oct 15 07:25:53 zfs-cis kernel: [479439.156980] Tainted: P OE 4.4.0-96-generic #119-Ubuntu Oct 15 07:25:53 zfs-cis kernel: [479439.162688] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 15 07:25:53 zfs-cis kernel: [479439.173974] zfs D 88197bd77318 0 8708 8141 0x Oct 15 07:25:53 zfs-cis kernel: [479439.173981] 88197bd77318 810c3dc2 8820374cf000 881b645ff000 Oct 15 07:25:53 zfs-cis kernel: [479439.173985] 88197bd78000 00792c6d 882030aa4ac8 Oct 15 07:25:53 zfs-cis kernel: [479439.173989] 88101dac1840 88197bd77330 8183f165 882030aa4a00 Oct 15 07:25:53 zfs-cis kernel: [479439.173993] Call Trace: Oct 15 07:25:53 zfs-cis kernel: [479439.174006] [] ? __wake_up_common+0x52/0x90 Oct 15 07:25:53 zfs-cis kernel: [479439.174023] [] schedule+0x35/0x80 Oct 15 07:25:53 zfs-cis kernel: [479439.174045] [] taskq_wait_id+0x60/0xb0 [spl] Oct 15 07:25:53 zfs-cis kernel: [479439.174051] [] ? wake_atomic_t_function+0x60/0x60 Oct 15 07:25:53 zfs-cis kernel: [479439.174115] [] ? dump_write+0x230/0x230 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174178] [] spa_taskq_dispatch_sync+0x92/0xd0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174223] [] dump_bytes+0x51/0x70 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174267] [] dump_write+0x11e/0x230 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174311] [] backup_cb+0x633/0x850 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174356] [] traverse_visitbp+0x47a/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174365] [] ? spl_kmem_alloc+0xaf/0x190 [spl] Oct 15 07:25:53 zfs-cis kernel: [479439.174409] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174462] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174503] [] traverse_dnode+0x7f/0xe0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174542] [] traverse_visitbp+0x6cc/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174579] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174616] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174653] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174690] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174726] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174762] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174799] [] traverse_dnode+0x7f/0xe0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174835] [] traverse_visitbp+0x865/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174871] [] traverse_impl+0x1ae/0x410 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174908] [] ? dmu_recv_end_check+0x210/0x210 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174944] [] traverse_dataset+0x52/0x60 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174981] [] ? dmu_recv_end_check+0x210/0x210 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175017] [] dmu_send_impl+0x409/0x560 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175060] [] dmu_send_obj+0x172/0x1e0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175129] [] zfs_ioc_send+0xe9/0x2c0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175143] [] ? strdup+0x3b/0x60 [spl] Oct 15 07:25:53 zfs-cis kernel: [479439.175207] [] zfsdev_ioctl+0x44b/0x4e0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175218] [] do_vfs_ioctl+0x29f/0x490 Oct 15 07:25:53 zfs-cis kernel: [479439.175225] [] ? _do_fork+0xec/0x360 Oct 15 07:25:53 zfs-cis kernel: [479439.175232] [] SyS_ioctl+0x79/0x90 Oct 15 07:25:53 zfs-cis kernel: [479439.175242] [] entry_SYSCALL_64_fastpath+0x16/0x71 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1723948/+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 1615405] Re: zfs share doesn't work
** Changed in: zfs Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1615405 Title: zfs share doesn't work Status in Native ZFS for Linux: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Bug description: I'm testing on Ubuntu 16.04 with the included zol 0.6.5. I have also reported this bug here: https://github.com/zfsonlinux/zfs/issues/4999 zfs share and zfs share -a just don't work. zfs set sharesmb=on pool/dataset works fine. I discovered that the shares are listed in /etc/dfs/sharetab but don't work. If I reboot or anything and try to share them again with zfs share, it will not work. net usershare list displays nothing. And of course because of this all shares are lost on every reboot. Despite a dataset having the sharesmb=on value set, it will not share with zfs share -a and if I use zfs share pool/dataset it says: cannot share 'pool/dataset': filesystem already shared, when net usershare list shows nothing**. Samba is running and the shares appear in /etc/dfs/sharetab, not that that is helping me. I've detailed a bunch of stuff at serverfault... if that's not good enough, I can bring some of it over here: http://serverfault.com/questions/797938/ubuntu-xenial-16-04-zfs-share- command-doesnt-work-for-smb-shares System/package informatiom zfsutils-linux: Installed: 0.6.5.6-0ubuntu12 Candidate: 0.6.5.6-0ubuntu12 Version table: *** 0.6.5.6-0ubuntu12 500 500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages Description:Ubuntu 16.04.1 LTS Release:16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu12 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Aug 21 12:11:47 2016 InstallationDate: Installed on 2016-05-26 (87 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.zfs: [modified] mtime.conffile..etc.default.zfs: 2016-07-12T22:45:19.830513 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1615405/+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 1847105] Re: very slow disk creation, snapshotting
** Changed in: zfs Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: Fix Released Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Won't Fix Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in virt-manager source package in Focal: Fix Released Status in libvirt source package in Groovy: Triaged Bug description: [Impact] * The defaults of virt-manager for disk allocation always worked fine when qcow2 had nothing but sparse support. So sparse=True vs sparse=False made no difference. So it always set sparse=False. Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it, which is not the intention. * For upgraders from pre-Focal this was a regression in two ways: a) allocation of qcow changed to non-sparse (fallocate based) potentially consuming more space b) depending on the underlying FS this made the allocation much slower * Fix by applying the upstream change that Defaults to sparse when requested format isn't raw (for raw the assumption ill stay that users do that for runtime performance, so non-sparse on those stays as-is) [Test Case] * open virt-manager and create a new guest which includes creating a new image for it * when clicking "finish" the image will be created (which e.g. on ZFS will take quite some time) * In the background grep ps output if the qemu-img call for qcow (the default) is using "preallocation=fallocate" (wrong) or "preallocation=metadata" (correct) [Regression Potential] * For upgraders from pre-focal it actually ensures behavior stays as is (no change/regression there) * For users of ZFS where the allocation was slow it fixes this slowness. * But for people using Focal all the time and on non-ZFS there will be a behavior change in no more doing falloc pre-allocating the qemu image. To be cleear there are four modes: 1. no allocation 2. metadata allocation - is initially larger but can improve performance when the image needs to grow 3. falloc - preallocates space for image by calling posix_fallocate 4. full - writes data to the underlying storage The fix changes the default from 3->2 which it always was and should be. As the patch says: "If users want to override it, they can do it via custom created storage." (To be clear, upstream changed this as we fixed it here, so on further upgrades what we apply here will be the behavior anyway, it seems wrong to keep Focal the only one in between kept different) * [racb] The code path being added special cases the 'raw' format and in handling of the default sparse setting. Areas of potential regression are therefore in the handling of the default and override of the default in the cases of both 'raw' and not 'raw'. [Other Info] * The slowness effect might be further mitigated by ZFS implementing more falloc options (thanks Richard for that hint) but that won't be in Focal. This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.13/5.13.0.1025.30~20.04.1)
All autopkgtests for the newly accepted linux-meta-oracle-5.13 (5.13.0.1025.30~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) snapd/2.54.3+20.04.1ubuntu0.2 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oracle-5.13 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1966066] Re: audio from external sound card is distorted
I confirm having the issue
Ubuntu 20.04
External soundcard Behringer UM2
Workaround fixed the issue with most app BUT Ardour (going through
ALSA).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1967579] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1967579 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1967579 Title: harden indirect calls against BHI attacks Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Branch History Injection is made easier when all indirect calls are funneled through very few points where the retpolines were. By replacing the retpoline jumps by indirect calls whenever retpolines are disabled, BHI attacks are more difficult to execute as the BTB is not as fixed as before. [Fixes] Though there are fixes that allow retpoline,lfence to be directly replaced in the indirect calls, given that mitigation is not recommended for most of the situations, that hardening is not as important as the one that works for the spectre_v2=off option (the default one for systems with eIBRS). This latter one is present starting with 5.13, but backporting to 5.4 might be a good measure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967579/+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 1958727] Re: bluetooth adaptor unable to find any devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958727 Title: bluetooth adaptor unable to find any devices Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: david@Kubuntu-desktop-2021:~$ dmesg |grep -i bluetooth [4.734771] Bluetooth: Core ver 2.22 [4.734788] Bluetooth: HCI device and connection manager initialized [4.734791] Bluetooth: HCI socket layer initialized [4.734793] Bluetooth: L2CAP socket layer initialized [4.734795] Bluetooth: SCO socket layer initialized [8.307343] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [8.307347] Bluetooth: BNEP filters: protocol multicast [8.307350] Bluetooth: BNEP socket layer initialized [ 12.295520] Bluetooth: RFCOMM TTY layer initialized [ 12.295527] Bluetooth: RFCOMM socket layer initialized [ 12.295531] Bluetooth: RFCOMM ver 1.11 david@Kubuntu-desktop-2021:~$ hciconfig -a hci0: Type: Primary Bus: USB BD Address: E8:48:B8:C8:20:00 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN RX bytes:3179 acl:0 sco:0 events:327 errors:0 TX bytes:9486 acl:0 sco:0 commands:305 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'Kubuntu-desktop-2021' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 22 18:25:42 2022 InstallationDate: Installed on 2021-03-28 (300 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958727/+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 1967579] [NEW] harden indirect calls against BHI attacks
*** This bug is a security vulnerability *** Public security bug reported: [Impact] Branch History Injection is made easier when all indirect calls are funneled through very few points where the retpolines were. By replacing the retpoline jumps by indirect calls whenever retpolines are disabled, BHI attacks are more difficult to execute as the BTB is not as fixed as before. [Fixes] Though there are fixes that allow retpoline,lfence to be directly replaced in the indirect calls, given that mitigation is not recommended for most of the situations, that hardening is not as important as the one that works for the spectre_v2=off option (the default one for systems with eIBRS). This latter one is present starting with 5.13, but backporting to 5.4 might be a good measure. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1967579 Title: harden indirect calls against BHI attacks Status in linux package in Ubuntu: New Bug description: [Impact] Branch History Injection is made easier when all indirect calls are funneled through very few points where the retpolines were. By replacing the retpoline jumps by indirect calls whenever retpolines are disabled, BHI attacks are more difficult to execute as the BTB is not as fixed as before. [Fixes] Though there are fixes that allow retpoline,lfence to be directly replaced in the indirect calls, given that mitigation is not recommended for most of the situations, that hardening is not as important as the one that works for the spectre_v2=off option (the default one for systems with eIBRS). This latter one is present starting with 5.13, but backporting to 5.4 might be a good measure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967579/+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 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
also fwiw, confirmed that starting from tag Ubuntu-5.15.0-25.25 (commit f4a9abe17854fc753c84a0ba4ac275e715a008f3), reverting commit 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0 applies cleanly and fixes the bug. -- 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/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+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 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
** Description changed: [Impact] vmx_ldtr_test in ubuntu_kvm_unit_tests will fail with: FAIL: Expected 0 for L1 LDTR selector (got 50) It's a test for commit afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" According to Intel 64 and IA-32 Architectures Software Developer’s Manual, L1's LDTR should be 0 after an emulated VM-exit from L2. [Fix] * afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" We already have this patch in Jammy. This patch can be cherry-picked into F/F-OEM-5.14/I. But some straightforward backport work is required for Bionic, as the code snippet for nested KVM haven't been split out to vmx/nested.c (55d2375e KVM: nVMX: Move nested code to dedicated files). [Test] Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1956315-vmx-ldtr/ Tested with: * B (bare-metal) * F (KVM instance) - * I (bare-metal) + * I (KVM instance / bare-metal) With this patched kernel, this test will pass: PASS: Expected 0 for L1 LDTR selector (got 0) Also tested with ubuntu_kvm_unit_tests and ubuntu_kvm_smoke_test to make sure this is not causing any other regressions. [Where problem could occur] If the patch is incorrect it might affect the nested KVM functionality while existing from L2 to L1. [Original bug description] Issue found on Bionic 4.15.0-166.174 with node rizzo Running 'kvm-ok' INFO: /dev/kvm exists KVM acceleration can be used '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=8a30588c timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Lnfifekq7r -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.i9y5hdMh49 enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP filter = vmx_ldtr_test, test = int3 filter = vmx_ldtr_test, test = into filter = vmx_ldtr_test, test = exit_monitor_from_l2_test filter = vmx_ldtr_test, test = invalid_msr filter = vmx_ldtr_test, test = v2_null_test filter = vmx_ldtr_test, test = v2_multiple_entries_test filter = vmx_ldtr_test, test = fixture_test_case1 filter = vmx_ldtr_test, test = fixture_test_case2 filter = vmx_ldtr_test, test = invvpid_test filter = vmx_ldtr_test, test = vmx_controls_test filter = vmx_ldtr_test, test = vmx_host_state_area_test filter = vmx_ldtr_test, test = vmx_guest_state_area_test filter = vmx_ldtr_test, test = vmentry_movss_shadow_test filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test filter = vmx_ldtr_test, test = apic_reg_virt_test filter = vmx_ldtr_test, test = virt_x2apic_mode_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test filter = vmx_ldtr_test, test = vmx_init_signal_test filter = vmx_ldtr_test, test = vmx_sipi_signal_test filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test filter = vmx_ldtr_test, test = vmx_ldtr_test Test suite: vmx_ldtr_test PASS: Expected 18 for L2 LDTR selector (got 18) FAIL: Expected 0 for L1 LDTR selector (got 50) filter = vmx_ldtr_test,
[Kernel-packages] [Bug 1967562] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1967562 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
Attached bizzy-debug.log, which is the console log of the Mt. Jade server (bizzy) with the kernel parameter "debug" enabled. ** Attachment added: "bizzy-debug.log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967562/+attachment/5575779/+files/bizzy-debug.log -- 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/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
** Description changed: = Description = - Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s + Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. -- 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/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
bizzy.log is the console log of the Mt. Jade server. The last entry is the kernel panic because of the pxe boot. The last successful deployment in bizzy.log is performed by MAAS. ** Attachment added: "bizzy.log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1967562/+attachment/5575772/+files/bizzy.log -- 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/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+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 1967562] [NEW] jammy beta (220330) arm iso kernel panic during pxe boot
Public bug reported: = Description = Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New -- 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/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra, Cavium thunderX crb2s Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
[Kernel-packages] [Bug 1967559] [NEW] llvm-13-dev missing zlib1g-dev dependency
Public bug reported: The llvm-13-dev package appears to be missing a declared dependency on zlib1g-dev. The cmake configuration in /usr/lib/llvm-13/cmake/LLVMConfig.cmake is looking for ZLIB, but failing to find it due to the missing dependency. (Just below that it also looks for and successfully finds libxml2, as the dependency for that has been declared.) What I expected: using "find_package(LLVM REQUIRED CONFIG)" in CMakeLists.txt to work. What happened: it failed; -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.12") -- Found LLVM 13.0.0 -- Using LLVMConfig.cmake in: /usr/lib/llvm-13/cmake -- Configuring done CMake Error at CMakeLists.txt:20 (add_executable): Target "demo" links to target "ZLIB::ZLIB" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Fixed the build failure by running: apt-get install zlib1g-dev $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 $ apt-cache policy llvm-13-dev llvm-13-dev: Installed: 1:13.0.0-2 Candidate: 1:13.0.0-2 Version table: *** 1:13.0.0-2 500 500 http://jp.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: llvm-toolchain-13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-13 in Ubuntu. https://bugs.launchpad.net/bugs/1967559 Title: llvm-13-dev missing zlib1g-dev dependency Status in llvm-toolchain-13 package in Ubuntu: New Bug description: The llvm-13-dev package appears to be missing a declared dependency on zlib1g-dev. The cmake configuration in /usr/lib/llvm-13/cmake/LLVMConfig.cmake is looking for ZLIB, but failing to find it due to the missing dependency. (Just below that it also looks for and successfully finds libxml2, as the dependency for that has been declared.) What I expected: using "find_package(LLVM REQUIRED CONFIG)" in CMakeLists.txt to work. What happened: it failed; -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.12") -- Found LLVM 13.0.0 -- Using LLVMConfig.cmake in: /usr/lib/llvm-13/cmake -- Configuring done CMake Error at CMakeLists.txt:20 (add_executable): Target "demo" links to target "ZLIB::ZLIB" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Fixed the build failure by running: apt-get install zlib1g-dev $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 $ apt-cache policy llvm-13-dev llvm-13-dev: Installed: 1:13.0.0-2 Candidate: 1:13.0.0-2 Version table: *** 1:13.0.0-2 500 500 http://jp.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1967559/+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 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume
Same problem on the same machine on ubuntu-derived Pop!_OS 21.10. Also persists in Windows after reboot. Problem is temporarily fixable by switching the trackpad off in bios, saving, and switching it on again. -- 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/1959728 Title: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with haptic response to clicks), the trackpad stops working after a suspend/resume cycle, although the red trackpoint continues to work fine for controlling the pointer. I believe this system is using S0i3 for suspend, in case that's relevant. If I boot from power off, then the trackpad works fine in both the pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic response to clicks. After a suspend/resume cycle, the trackpad stops responding, although a lot of swiping/pressing will occasionally produce a button press event. This state persists even if I reboot out of Linux (without a power cycle) - for example the trackpad no longer works for the pre-boot BIOS configuration screen, until a full power cycle (which fixes the trackpad). Possibly relevant, the trackpad seems to be this device to the kernel: [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6 [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7 [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00 and the last kernel messages before suspend are: [ 305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 305.217435] printk: Suspending console(s) (use no_console_suspend to debug) [ 305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost arbitration [ 306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device. [ 306.616463] ACPI: EC: interrupt blocked [ 331.551118] ACPI: EC: interrupt unblocked ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bina 1543 F pipewire bina 1544 F pipewire-media- bina 1545 F pulseaudio /dev/snd/seq:bina 1543 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 1 14:54:14 2022 InstallationDate: Installed on 2022-02-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) MachineType: LENOVO 20QA000EUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2021 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: N2MET53W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QA000EUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1: dmi.product.family: ThinkPad X1 Titanium Gen 1 dmi.product.name: 20QA000EUS dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1 dmi.product.version: ThinkPad X1 Titanium Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959728/+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 1956509] Re: Support AMD P-State cpufreq control mechanism
The major patchset has been available in v5.17 or above, but we still need to enable AMD P-State as built-in in linux-unstable/jammy and linux-oem-5.17/jammy, so that it will take precedence over acpi-cpufreq. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956509 Title: Support AMD P-State cpufreq control mechanism Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=linux- next=40181d67f1e9f1ac87af9c0c194e40ab2a081974 $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 3.10 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.59 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3100MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956509/+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 1956509] Re: Support AMD P-State cpufreq control mechanism
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956509 Title: Support AMD P-State cpufreq control mechanism Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux- pm.git/commit/?h=linux- next=40181d67f1e9f1ac87af9c0c194e40ab2a081974 $ sudo cpupower frequency-info analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us hardware limits: 400 MHz - 3.10 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.60 GHz and 3.10 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.59 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3100MHz Pstate-P1: 1800MHz Pstate-P2: 1600MHz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956509/+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 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
I've reproduced the original problem then been running proposed kernels in bionic and focal now for at least 2 hours, and problem seems fixed: root@machine-1:~# uname -r 4.15.0-176-generic root@machine-1:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS" root@machine-1:~# 5.4.0-108-generic root@machine-2:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS" root@machine-2:~# Marking as verified in bionic - should we be doing so in focal too? ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification [Impact] When an admin enables audit at early boot via the "audit=1" kernel command line the audit queue behavior is slightly different; the audit subsystem goes to greater lengths to avoid dropping records, which unfortunately can result in problems when the audit daemon is forcibly stopped for an extended period of time. [Fix] upstream discussion: https://lore.kernel.org/all/cahc9vhqgx070poxzk_pusawgzppdqvpezvfybse2dnryrbw...@mail.gmail.com/T/ upstream commit: f26d04331360d42dbd6b58448bd98e4edbfbe1c5 [Test] configurations: auditctl -b 64 auditctl --backlog_wait_time 6 auditctl -r 0 auditctl -w /root/aaa -p wrx shell scripts： #!/bin/bash i=0 while [ $i -le 66 ] do touch /root/aaa let i++ done mandatory conditions: add "audit=1" to the cmdline, and kill -19 pid_number(for /sbin/auditd). As long as we keep the audit_hold_queue non-empty, flush the hold queue will fall into an infinite loop. This could also trigger soft lockup when it drops into a infinite loop, e.g. kernel: [ 94.186433] watchdog: BUG: soft lockup - CPU#2 stuck for 11s! [kauditd:34] kernel: [ 94.187736] Modules linked in: xfs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_ conntrack libcrc32c iptable_filter isofs xt_cgroup xt_tcpudp iptable_mangle ip_tables x_tables sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 pp dev crypto_simd glue_helper joydev vmwgfx ttm cryptd vmw_balloon drm_kms_helper intel_rapl_perf input_leds psmouse drm fb_sys_fops syscopyarea vmxnet3 sysfillrect parport_pc parport m ac_hid shpchp i2c_piix4 vmw_vsock_vmci_transport vsock sysimgblt vmw_vmci serio_raw mptspi mptscsih mptbase scsi_transport_spi pata_acpi floppy autofs4 kernel: [ 94.187757] CPU: 2 PID: 34 Comm: kauditd Not tainted 4.15.0-171-generic #180~16.04.1-Ubuntu kernel: [ 94.187757] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 kernel: [ 94.187800] skb_queue_head+0x47/0x50 kernel: [ 94.187803] kauditd_rehold_skb+0x18/0x20 kernel: [ 94.187805] kauditd_send_queue+0xcd/0x100 kernel: [ 94.187806] ? kauditd_retry_skb+0x20/0x20 kernel: [ 94.187808] ? kauditd_send_multicast_skb+0x80/0x80 kernel: [ 94.187809] kauditd_thread+0xa7/0x240 kernel: [ 94.187812] ? wait_woken+0x80/0x80 kernel: [ 94.187815] kthread+0x105/0x140 kernel: [ 94.187817] ? auditd_reset+0x90/0x90 kernel: [ 94.187818] ? kthread_bind+0x40/0x40 kernel: [ 94.187820] ret_from_fork+0x35/0x40 [Other Info] SF: #00330803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+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 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
PR made for the Focal part of this
--
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/1917471
Title:
[SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
causes Bus Fatal Error when rebooting system with BCM5720 NIC
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their
logs and thus it is generating an unusualy high volume of support
calls from the field.
In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
Upstream, these errors were discovered and that patch was reverted
(see Fix Below). We carry the revert commit in all subsequent Focal
HWE kernels starting at 5.12, but the fix was never pulled back into
Focal 5.4.
according to the hardware partner:
the following error messages are observed when rebooting a machine
that uses the BCM5720 chipset, which is a widely used 1GbE controller
found on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
[FIX]
The fix is to apply this patch from upstream:
commit 9d3fcb28f9b9750b474811a2964ce022df56336e
Author: Josef Bacik
Date: Tue Mar 16 22:17:48 2021 -0400
Revert "PM: ACPI: reboot: Use S5 for reboot"
This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
This patch causes a panic when rebooting my Dell Poweredge r440. I do
not have the full panic log as it's lost at that stage of the reboot and
I do not have a serial console. Reverting this patch makes my system
able to reboot again.
Example:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471
The hardware partner has preemptively pulled our 5.4 tree, applied the
fix and tested it in their labs and determined that this does resolve
the issue.
[TEST CASE]
Install the patched kernel on a machine that uses a BCM5720 LOM and reboot
the machine and see that the errors no longer appear.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Description changed: + SRU Justification: + Impact: + Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. - Target kernels: 5.15 + Fix: + These are some of the DPC fixes which help in handling some of the + failure cases of DownPort Containment events. - - - - These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Without these, recovery from DPC event fails and NVMe endpoint is not accessible for some of the scenarios. - - Upstream kernel patches to be included into Ubuntu 22.04 SRU and into - Ubuntu 20.04.5: + Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu + 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 + + Test Case: -- 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/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. Fix: These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 Test Case: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241/+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 1964591] Re: Move cdc-acm from modules-extra for embedded serial support
This bug was fixed in the package linux-raspi - 5.15.0-1004.4 --- linux-raspi (5.15.0-1004.4) jammy; urgency=medium * jammy/linux-raspi: 5.15.0-1004.4 -proposed tracker (LP: #1965283) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-16) (LP: #1965308) - ARM: dts: bcm2711-rpi-ds: Disable the BCM2835 STC - Revert "drm/tc358762: Set the DRM_BRIDGE_OP_UPSTREAM_FIRST flag to configure DSI host" - Revert "drm: Introduce DRM_BRIDGE_OP_UPSTREAM_FIRST to alter bridge init order" - drm/bridge: Introduce pre_enable_upstream_first to alter bridge init order - drm/panel: Add prepare_upstream_first flag to drm_panel - drm: Include drm_connector.h from drm_panel.h - drm/tc358762: Set the pre_enable_upstream_first flag to configure DSI host * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-08) (LP: #1964144) - drm/vc4: hdmi: Make sure the device is powered with CEC - overlays: rpi-poe(-plus): Fix parameters - dtoverlays: fix overrides in vc4-kms-dpi-generic - dtoverlays: add rgb565-padhi output to vc4-kms-dpi-generic - media: i2c: imx219: Scale the pixel clock rate for the 640x480 mode - drm/vc4: For DPI, MEDIA_BUS_FMT_RGB565_1X16 is mode 1, not 3. - dtoverlays: Add additional mappings to vc4-kms-dpi-generic - drm: Introduce DRM_BRIDGE_OP_UPSTREAM_FIRST to alter bridge init order - drm/dsi: Document the meaning and spec references for MIPI_DSI_MODE_* - drm/bridge: tc358762: Ignore EPROBE_DEFER when logging errors - drm/tc358762: Set the DRM_BRIDGE_OP_UPSTREAM_FIRST flag to configure DSI host - drm/vc4: Rename bridge to out_bridge - drm/vc4: Move DSI initialisation to encoder_mode_set. - drm/vc4: Remove splitting the bridge chain from the driver. - drm/vc4: Convert vc4_dsi to use atomic enable/disable/mode_set. - drm/vc4: Convert vc4_dsi to using a bridge instead of encoder. - drm/vc4: Remove entry to ULPS from vc4_dsi post_disable - usb: xhci: add a quirk for Superspeed bulk OUT transfers on VL805 - dtoverlays: Correct link frequency for ov7251 - media: i2c: Add acpi support to ov7251 - media: i2c: Provide ov7251_check_hwcfg() - media: i2c: Add ov7251_pll_configure() - media: i2c: Add support for 19.2MHz clock to ov7251 - media: i2c: Add ov7251_detect_chip() - media: i2c: Add pm_runtime support to ov7251 - media: i2c: Remove .s_power() from ov7251 - media: i2c: ov7251: Reinstate setting ov7251_global_init_setting - media: i2c: ov7251: V4L2_CID_PIXEL_RATE is fixed - media: i2c: ov7251: V4L2_CID_LINK_FREQUENCY is fixed - media: i2c: ov7251: Initialise current_mode during probe - media: i2c: ov7251: Add V4L2_CID_HBLANK control - media: i2c: ov7251: Do not reset gain on mode change - media: i2c: ov7251: Fix link_freq validation loop - media: i2c: ov7251: Add get_selection for NATIVE_SIZE, CROP_BOUNDS, CROP_DEFAULT - media: i2c: ov7251: Set VTS instead of having full tables for FPS. - media: i2c: ov7251: Limit exposure based on VTS - media: i2c: ov7251: Separate modes from frame intervals - media: i2c: ov7251: Add V4L2_CID_VBLANK - media: i2c: ov7251: Switch from V4L2_CID_GAIN to V4L2_CID_ANALOGUE_GAIN - dtoverlays: Switch ov7251 to using Media Controller by default - Revert "drm/vc4: Fix interrupt masking for HVS5." - Revert "drm/vc4: Correct interrupt enable bits on hvs4" - Revert "drm/vc4: hvs: Create a shadow dlist" - Revert "drm/vc4: plane: Use dlist offset instead of pointer" - ARM: boot: dts: bcm2711: Fix HVS register range - drm/vc4: hvs: Fix frame count register readout - drm/vc4: hvs: Use pointer to HVS in HVS_READ and HVS_WRITE macros - drm/vc4: hvs: Defer dlist slots deallocation - ARM: dts: Add GPIO line names for downstream RPis - overlays:fixes probing of Hifiberry DAC2 HD - overlays: Overlays for WaveShare 2-Chan CAN FD HAT - overlays: Add "drm" parameter to pitft35-resistive - configs: Add CONFIG_TINYDRM_HX8357D=m - usb: xhci: rework XHCI_VLI_SS_BULK_OUT_BUG quirk - usb: xhci: expand the scope of XHCI_VLI_SS_BULK_OUT_BUG - media/i2c: Add driver for Omnivision OV2311 - dtoverlays: Add overlay for Omnivision OV2311 image sensor - defconfigs: Add OV2311 image sensor to Pi defconfigs - staging/vc-sm-cma: Avoid log spamming on Pi0/1 over cache alias. - staging: vc04_services: isp: Permit all sRGB colour spaces on ISP outputs - drivers: staging: bcm2835-isp: Do not cleanup mmal vcsm buffer on stop_streaming - drm/vc4: Fix out of order frames during asynchronous page flips - staging: vc04_services: codec: Add support for V4L2_PIX_FMT_RGBA32 format - drm/vc4: hvs: Reset muxes at probe time - drm/vc4: kms: Store channel in local variable - drm/vc4: kms:
[Kernel-packages] [Bug 1964144] Re: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-08)
This bug was fixed in the package linux-raspi - 5.15.0-1004.4 --- linux-raspi (5.15.0-1004.4) jammy; urgency=medium * jammy/linux-raspi: 5.15.0-1004.4 -proposed tracker (LP: #1965283) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-16) (LP: #1965308) - ARM: dts: bcm2711-rpi-ds: Disable the BCM2835 STC - Revert "drm/tc358762: Set the DRM_BRIDGE_OP_UPSTREAM_FIRST flag to configure DSI host" - Revert "drm: Introduce DRM_BRIDGE_OP_UPSTREAM_FIRST to alter bridge init order" - drm/bridge: Introduce pre_enable_upstream_first to alter bridge init order - drm/panel: Add prepare_upstream_first flag to drm_panel - drm: Include drm_connector.h from drm_panel.h - drm/tc358762: Set the pre_enable_upstream_first flag to configure DSI host * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-08) (LP: #1964144) - drm/vc4: hdmi: Make sure the device is powered with CEC - overlays: rpi-poe(-plus): Fix parameters - dtoverlays: fix overrides in vc4-kms-dpi-generic - dtoverlays: add rgb565-padhi output to vc4-kms-dpi-generic - media: i2c: imx219: Scale the pixel clock rate for the 640x480 mode - drm/vc4: For DPI, MEDIA_BUS_FMT_RGB565_1X16 is mode 1, not 3. - dtoverlays: Add additional mappings to vc4-kms-dpi-generic - drm: Introduce DRM_BRIDGE_OP_UPSTREAM_FIRST to alter bridge init order - drm/dsi: Document the meaning and spec references for MIPI_DSI_MODE_* - drm/bridge: tc358762: Ignore EPROBE_DEFER when logging errors - drm/tc358762: Set the DRM_BRIDGE_OP_UPSTREAM_FIRST flag to configure DSI host - drm/vc4: Rename bridge to out_bridge - drm/vc4: Move DSI initialisation to encoder_mode_set. - drm/vc4: Remove splitting the bridge chain from the driver. - drm/vc4: Convert vc4_dsi to use atomic enable/disable/mode_set. - drm/vc4: Convert vc4_dsi to using a bridge instead of encoder. - drm/vc4: Remove entry to ULPS from vc4_dsi post_disable - usb: xhci: add a quirk for Superspeed bulk OUT transfers on VL805 - dtoverlays: Correct link frequency for ov7251 - media: i2c: Add acpi support to ov7251 - media: i2c: Provide ov7251_check_hwcfg() - media: i2c: Add ov7251_pll_configure() - media: i2c: Add support for 19.2MHz clock to ov7251 - media: i2c: Add ov7251_detect_chip() - media: i2c: Add pm_runtime support to ov7251 - media: i2c: Remove .s_power() from ov7251 - media: i2c: ov7251: Reinstate setting ov7251_global_init_setting - media: i2c: ov7251: V4L2_CID_PIXEL_RATE is fixed - media: i2c: ov7251: V4L2_CID_LINK_FREQUENCY is fixed - media: i2c: ov7251: Initialise current_mode during probe - media: i2c: ov7251: Add V4L2_CID_HBLANK control - media: i2c: ov7251: Do not reset gain on mode change - media: i2c: ov7251: Fix link_freq validation loop - media: i2c: ov7251: Add get_selection for NATIVE_SIZE, CROP_BOUNDS, CROP_DEFAULT - media: i2c: ov7251: Set VTS instead of having full tables for FPS. - media: i2c: ov7251: Limit exposure based on VTS - media: i2c: ov7251: Separate modes from frame intervals - media: i2c: ov7251: Add V4L2_CID_VBLANK - media: i2c: ov7251: Switch from V4L2_CID_GAIN to V4L2_CID_ANALOGUE_GAIN - dtoverlays: Switch ov7251 to using Media Controller by default - Revert "drm/vc4: Fix interrupt masking for HVS5." - Revert "drm/vc4: Correct interrupt enable bits on hvs4" - Revert "drm/vc4: hvs: Create a shadow dlist" - Revert "drm/vc4: plane: Use dlist offset instead of pointer" - ARM: boot: dts: bcm2711: Fix HVS register range - drm/vc4: hvs: Fix frame count register readout - drm/vc4: hvs: Use pointer to HVS in HVS_READ and HVS_WRITE macros - drm/vc4: hvs: Defer dlist slots deallocation - ARM: dts: Add GPIO line names for downstream RPis - overlays:fixes probing of Hifiberry DAC2 HD - overlays: Overlays for WaveShare 2-Chan CAN FD HAT - overlays: Add "drm" parameter to pitft35-resistive - configs: Add CONFIG_TINYDRM_HX8357D=m - usb: xhci: rework XHCI_VLI_SS_BULK_OUT_BUG quirk - usb: xhci: expand the scope of XHCI_VLI_SS_BULK_OUT_BUG - media/i2c: Add driver for Omnivision OV2311 - dtoverlays: Add overlay for Omnivision OV2311 image sensor - defconfigs: Add OV2311 image sensor to Pi defconfigs - staging/vc-sm-cma: Avoid log spamming on Pi0/1 over cache alias. - staging: vc04_services: isp: Permit all sRGB colour spaces on ISP outputs - drivers: staging: bcm2835-isp: Do not cleanup mmal vcsm buffer on stop_streaming - drm/vc4: Fix out of order frames during asynchronous page flips - staging: vc04_services: codec: Add support for V4L2_PIX_FMT_RGBA32 format - drm/vc4: hvs: Reset muxes at probe time - drm/vc4: kms: Store channel in local variable - drm/vc4: kms:
[Kernel-packages] [Bug 1965308] Re: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-16)
This bug was fixed in the package linux-raspi - 5.15.0-1004.4 --- linux-raspi (5.15.0-1004.4) jammy; urgency=medium * jammy/linux-raspi: 5.15.0-1004.4 -proposed tracker (LP: #1965283) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-16) (LP: #1965308) - ARM: dts: bcm2711-rpi-ds: Disable the BCM2835 STC - Revert "drm/tc358762: Set the DRM_BRIDGE_OP_UPSTREAM_FIRST flag to configure DSI host" - Revert "drm: Introduce DRM_BRIDGE_OP_UPSTREAM_FIRST to alter bridge init order" - drm/bridge: Introduce pre_enable_upstream_first to alter bridge init order - drm/panel: Add prepare_upstream_first flag to drm_panel - drm: Include drm_connector.h from drm_panel.h - drm/tc358762: Set the pre_enable_upstream_first flag to configure DSI host * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-08) (LP: #1964144) - drm/vc4: hdmi: Make sure the device is powered with CEC - overlays: rpi-poe(-plus): Fix parameters - dtoverlays: fix overrides in vc4-kms-dpi-generic - dtoverlays: add rgb565-padhi output to vc4-kms-dpi-generic - media: i2c: imx219: Scale the pixel clock rate for the 640x480 mode - drm/vc4: For DPI, MEDIA_BUS_FMT_RGB565_1X16 is mode 1, not 3. - dtoverlays: Add additional mappings to vc4-kms-dpi-generic - drm: Introduce DRM_BRIDGE_OP_UPSTREAM_FIRST to alter bridge init order - drm/dsi: Document the meaning and spec references for MIPI_DSI_MODE_* - drm/bridge: tc358762: Ignore EPROBE_DEFER when logging errors - drm/tc358762: Set the DRM_BRIDGE_OP_UPSTREAM_FIRST flag to configure DSI host - drm/vc4: Rename bridge to out_bridge - drm/vc4: Move DSI initialisation to encoder_mode_set. - drm/vc4: Remove splitting the bridge chain from the driver. - drm/vc4: Convert vc4_dsi to use atomic enable/disable/mode_set. - drm/vc4: Convert vc4_dsi to using a bridge instead of encoder. - drm/vc4: Remove entry to ULPS from vc4_dsi post_disable - usb: xhci: add a quirk for Superspeed bulk OUT transfers on VL805 - dtoverlays: Correct link frequency for ov7251 - media: i2c: Add acpi support to ov7251 - media: i2c: Provide ov7251_check_hwcfg() - media: i2c: Add ov7251_pll_configure() - media: i2c: Add support for 19.2MHz clock to ov7251 - media: i2c: Add ov7251_detect_chip() - media: i2c: Add pm_runtime support to ov7251 - media: i2c: Remove .s_power() from ov7251 - media: i2c: ov7251: Reinstate setting ov7251_global_init_setting - media: i2c: ov7251: V4L2_CID_PIXEL_RATE is fixed - media: i2c: ov7251: V4L2_CID_LINK_FREQUENCY is fixed - media: i2c: ov7251: Initialise current_mode during probe - media: i2c: ov7251: Add V4L2_CID_HBLANK control - media: i2c: ov7251: Do not reset gain on mode change - media: i2c: ov7251: Fix link_freq validation loop - media: i2c: ov7251: Add get_selection for NATIVE_SIZE, CROP_BOUNDS, CROP_DEFAULT - media: i2c: ov7251: Set VTS instead of having full tables for FPS. - media: i2c: ov7251: Limit exposure based on VTS - media: i2c: ov7251: Separate modes from frame intervals - media: i2c: ov7251: Add V4L2_CID_VBLANK - media: i2c: ov7251: Switch from V4L2_CID_GAIN to V4L2_CID_ANALOGUE_GAIN - dtoverlays: Switch ov7251 to using Media Controller by default - Revert "drm/vc4: Fix interrupt masking for HVS5." - Revert "drm/vc4: Correct interrupt enable bits on hvs4" - Revert "drm/vc4: hvs: Create a shadow dlist" - Revert "drm/vc4: plane: Use dlist offset instead of pointer" - ARM: boot: dts: bcm2711: Fix HVS register range - drm/vc4: hvs: Fix frame count register readout - drm/vc4: hvs: Use pointer to HVS in HVS_READ and HVS_WRITE macros - drm/vc4: hvs: Defer dlist slots deallocation - ARM: dts: Add GPIO line names for downstream RPis - overlays:fixes probing of Hifiberry DAC2 HD - overlays: Overlays for WaveShare 2-Chan CAN FD HAT - overlays: Add "drm" parameter to pitft35-resistive - configs: Add CONFIG_TINYDRM_HX8357D=m - usb: xhci: rework XHCI_VLI_SS_BULK_OUT_BUG quirk - usb: xhci: expand the scope of XHCI_VLI_SS_BULK_OUT_BUG - media/i2c: Add driver for Omnivision OV2311 - dtoverlays: Add overlay for Omnivision OV2311 image sensor - defconfigs: Add OV2311 image sensor to Pi defconfigs - staging/vc-sm-cma: Avoid log spamming on Pi0/1 over cache alias. - staging: vc04_services: isp: Permit all sRGB colour spaces on ISP outputs - drivers: staging: bcm2835-isp: Do not cleanup mmal vcsm buffer on stop_streaming - drm/vc4: Fix out of order frames during asynchronous page flips - staging: vc04_services: codec: Add support for V4L2_PIX_FMT_RGBA32 format - drm/vc4: hvs: Reset muxes at probe time - drm/vc4: kms: Store channel in local variable - drm/vc4: kms:
[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
I have this issue on my Dell XPS 9380. I can boot 5.13.0.35, but 0.37 and 0.39 simply show the error: out of memory. I have tried changing my GFXMODE to 800x600x24, which hwinfo lists as a supported resolution, but grub just ignores it? Same with timeout? It just shows in the 4K native res every time, almost as if it's taunting me. Eventually the 0.35 kernel will be deleted by a system update, and my system will be bricked. I guess I'm going to need to reinstall, aren't I? -- 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/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2QH38EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1964984] Re: Fix OOB handling RX packets in heavy traffic
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1964984 Title: Fix OOB handling RX packets in heavy traffic Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] This is reproducible on systems which already have heavy background traffic. On top of that, the user issues one of the 2 docker pulls below: docker pull nvcr.io/ea-doca-hbn/hbn/hbn:latest OR docker pull gitlab-master.nvidia.com:5005/dl/dgx/tritonserver:22.02-py3-qa The second one is a very large container (17GB) When they run docker pull, the OOB interface stops being pingable, the docker pull is interrupted for a very long time (>3mn) or times out. [Fix] * Update the RX_CQE_CI before updating the RX_PI to avoid a race condition where we wrongly inform HW that there is space for the WQE. * disable the RX DMA while we are handling incoming packets to avoid overflow. [Test Case] * Created a script which loops 200 times and does a docker pull in each loop: docker pull nvcr.io/ea-doca-hbn/hbn/hbn:latest OR docker pull gitlab-master.nvidia.com:5005/dl/dgx/tritonserver:22.02-py3-qa [Regression Potential] * This could result in slower handling since we are disabling/enabling the DMA periodically. * Although this fix has been tested by the people who opened the bug, QA needs to thoroughly test it to make sure it is not reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1964984/+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 1960575] Re: Pass originating device to drivers offloading ct connection so devices will filter the tuples and offload them more efficiently
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1960575 Title: Pass originating device to drivers offloading ct connection so devices will filter the tuples and offload them more efficiently Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Currently, drivers register to a ct zone that can be shared by multiple devices. This can be inefficient for the driver to offload, as it needs to handle all the cases where the tuple can come from, instead of where it's most likely will arive from. For example, consider the following tc rules: tc filter add dev dev1 ... flower action ct commit zone 5 \ action mirred egress redirect dev dev2 tc filter add dev dev2 ... flower action ct zone 5 \ action goto chain chain 2 tc filter add dev dev2 ... flower ct_state +trk+est ... \ action mirred egress redirect dev dev1 Both dev2 and dev1 register to the zone 5 flow table (created by act_ct). A tuple originating on dev1, going to dev2, will be offloaded to both devices, and both will need to offload both directions, resulting in 4 total rules. The traffic will only hit originiating tuple on dev1, and reply tuple on dev2. By passing the originating device that created the connection with the tuple, dev1 can choose to offload only the originating tuple, and dev2 only the reply tuple. Resulting in a more efficient offload. The first patch adds an act_ct nf conntrack extension, to temporarily store the originiating device from the skb before offloading the connection once the connection is established. Once sent to offload, it fills the tuple originating device. The second patch get this information from tuples which pass in openvswitch. The third patch is Mellanox driver ct offload implementation using this information to provide a hint to firmware of where this offloaded tuple packets will arrive from (LOCAL or UPLINK port), and thus increase insertion rate. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" With SW steering enabled and the above commits (and up to date ofed) tuple insertion rate should be about twice as fast. This can be seen via procfs hw offloaded count while running high traffic: while true; do res=`sudo cat /proc/net/nf_conntrack | grep -i offload` && echo "$res" && echo "$res" | wc -l; done * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960575/+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 1963948] Re: Fix flow table lookup after ct clear or switching zones
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1963948 Title: Fix flow table lookup after ct clear or switching zones Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug Flow table lookup is skipped if packet either went through ct clear action (which set the IP_CT_UNTRACKED flag on the packet), or while switching zones and there is already a connection associated with the packet. This will result in no SW offload of the connection, and the and connection not being removed from flow table with TCP teardown (fin/rst packet). * How to test Create OVS bridge with 2 veth pairs, put each veth peer device in a different namespace - ns0, ns1, and add the other side veth devices (named ns[01]_veth below) to OVS bridge. Configure the namespace devices with an ip, and bring all devices up. Enable HW offload in ovs and configure connection tracking OpenFlow rules that pass via two zones (but drop the FIN packets on the reply side or they will still teardown the connection in second zone from the reply side as it happens first): ovs-ofctl add-flow br-ovs "arp actions=NORMAL" ovs-ofctl add-flow br-ovs "ct_state=-trk,ip,in_port=ns0_veth actions=ct(table=5,zone=5)" ovs-ofctl add-flow br-ovs "ct_state=-trk,tcp,in_port=ns1_veth,tcp_flags=-fin actions=ct(table=8,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+new+trk,ip,in_port=ns0_veth actions=ct(commit,zone=5),ct(table=7,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,ip,in_port=ns0_veth actions=ct(table=7,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+new+trk,ip,in_port=ns0_veth actions=ct(commit,zone=7),output:ns1_veth" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,ip,in_port=ns0_veth actions=output:ns1_veth" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,tcp,in_port=ns1_veth actions=ct(table=9,zone=5)" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,tcp,in_port=ns1_veth actions=output:ns0_veth" Run TCP iperf from ns0 namespace to an iperf server on ns1 namepsace with the given ip. After traffic ends, check cat /proc/net/nf_conntrack | grep -i offload If bug occurs, connections will remain offloaded till timeout, otherwise, they will be in teardown state. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1963948/+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 1961819] Re: CT: Offload only ASSURED connections
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1961819 Title: CT: Offload only ASSURED connections Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Assured connections are those connections which deemed of "higher quality" and less like to expire than non-assured connections, as they passed some stricter rule (e.g in udp reply + connection lasting more than 2 seconds). This feature offloads only those connections. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a short UDP connection (< 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 1 -u Run longer UDP connection (> 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 10 -u With the above commit quick lived UDP connections (< 2 seconds) will not be offloaded to the flow table as can be checked by cat /proc/net/nf_conntrack | grep -i offload while connections lasting more than 2 seconds (and of course double sided) will be offloaded. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1961819/+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 1965017] Re: Sync up gpio interrupt handling with upstreamed version
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Asmaa Mnebhi (asmaam) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1965017 Title: Sync up gpio interrupt handling with upstreamed version Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] Although the gpio-mlxbf2.c driver has already been upstreamed, it did not include gpio interrupt handling. We recently upstreamed the latter and as requested by maintainers, moved all gpio interrupt code from the mlxbf-gige driver to the gpio-mlxbf2.c to be conform with linux standards. IMPORTANT: during testing, make sure the latest UEFI (bootloader) is loaded on top of these changes, otherwise both the gpio driver and mlxbf-gige driver will fail to load. [Fix] * reverted 6 commits related to the gpio-mlxbf2 driver so that the canonical changes are in sync with what is upstreamed. * Cherry-picked 11 gpio-mlxbf2.c commits from the linux master branch. 10 commits are minor commits added by other maintainers. The 11th cherry-picked commit is the one adding proper interrupt support in the gpio-mlxbf2.c driver. The upstreamed version of the GPIO driver added back the dependency between the mlxbf-gige driver and gpio-mlxbf2 driver. * Added one commit on top of the above to add the driver version and fix the SPDX Licence identifier. * updated the UEFI ACPI table to reflect the above changes (so the bootloader and the linux drivers need to be in sync) * Following the generic way of writing a linux gpio driver, we created a separate driver for power handling (low power and reboot) called pwr-mlxbf.c. This driver has not been upstreamed yet but will take care of the GPIO7 software reset and the OCP3.0 GPIO low power mode. Previously all this code was integrated within the gpio-mlxbf2.c driver. [Test Case] * oob_net0 coming up after several SW_RESET or reboot * oob_net0 coming up after several powercycles * oob_net0 coming up after pushing a new Ubuntu/CentOS/Yocto * rmmod/modprobe mlxbf_gige several times * Test that GPIO7 reset still works on BlueSphere like boards [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1965017/+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 1896350] Re: nbd locks system?
** Tags added: sts -- 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/1896350 Title: nbd locks system? Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use nbd on ubuntu 20.04 like so: qemu-img create -f qcow2 foo.img 500M sudo modprobe nbd sudo qemu-nbd --disconnect /dev/nbd15 || true sudo qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img sudo mkfs.ext4 -L root -O "^64bit" -E nodiscard /dev/nbd15 sudo qemu-nbd --disconnect /dev/nbd15 It seems to work on some systems, but even on those systems, strange things show up in syslog, e.g. Sep 19 15:46:02 thinky kernel: [27042.757768] block nbd15: Possible stuck request dd2d7f93: control (read@135168,126976B). Runtime 450 seconds Sep 19 15:46:26 thinky kernel: [27067.333867] INFO: task systemd-udevd:17364 blocked for more than 241 seconds. and in kern.log, e.g. ... Sep 19 16:17:27 thinky kernel: [ 71.676026] Buffer I/O error on dev nbd15, logical block 7, async page read Sep 19 16:17:27 thinky kernel: [ 71.676049] blk_update_request: I/O error, dev nbd15, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676051] Buffer I/O error on dev nbd15, logical block 0, async page read Sep 19 16:17:27 thinky kernel: [ 71.676061] blk_update_request: I/O error, dev nbd15, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676063] Buffer I/O error on dev nbd15, logical block 1, async page read Sep 19 16:17:27 thinky kernel: [ 71.676147] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.676324] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.676473] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.678340] nbd15: detected capacity change from 0 to 524288000 Sep 19 16:17:27 thinky kernel: [ 71.678536] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.678719] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.678947] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.679985] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.680172] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.680366] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.680647] block nbd15: Attempted send on invalid socket and the system seems to hang on reboot. Also, on another system (an up to date mac, running ubuntu 20.04 in virtualbox), the mkfs.ext4 fails, complaining the device is zero size. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2948 F pulseaudio /dev/snd/controlC2: dank 2948 F pulseaudio /dev/snd/controlC0: dank 2948 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 16:28:43 2020 HibernationDevice: RESUME=UUID=7aecd5d3-2f5b-4c07-8867-801e63868a0f InstallationDate: Installed on 2017-04-29 (1239 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO ThinkServer TS140 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=ff9a24e4-277d-4baf-819b-826a33d5bb5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-01 (141 days ago) dmi.bios.date: 09/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT99AUS dmi.board.name: ThinkServer TS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT99AUS:bd09/19/2014:svnLENOVO:pnThinkServerTS140:pvr70A4000HUX:rvnLENOVO:rnThinkServerTS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: ThinkServer TS140 dmi.product.sku: LENOVO_PN_ThinkServer TS140 dmi.product.version: 70A4000HUX dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1966010] Re: Fix audio on Zbook Studio G9
Both speaker and udio LEDs are working now. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+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 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
** Changed in: dkms (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: In Progress Status in dkms package in Debian: Confirmed Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1963835/+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 1962490] Re: Support VF groups rate limit
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1962490 Title: Support VF groups rate limit Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Managing TX rate of VFs becomes non-trivial task when a big number of VFs are used. This issue can be handled with some grouping mechanism. Currently driver provide two ways to limit TX rate of the VF: TC police action and NDO API callback. Implementation of grouping within this two infrastructures problematic, due to the following: NDO API rate limiting is legacy feature, even though it's available in switchdev mode, and extending it with new abstraction is not good anyway; TC police action is flow based and requires net device with Qdisc on it and implementing this will bring unwanted complications. According to aforesaid devlink is the most appropriate place. * How to test Set tx_max value on the devlink port with a command. For ex.: $ devlink port function rate set pci/:82:00.0/1 tx_max 10gbit or if grouping is required, create rate group with configured tx_max value in a single command and assign port to this group: $ devlink port function rate add pci/:82:00.0/1st_group tx_max 8gbit $ devlink port function rate set pci/:82:00.0/1 tx_max 10gbit parent 1st_group Configuration is done. Run traffic and do measurement. * What it could break. As this pull request backported 130 patches from devlink/netlink, it may break some functionalities from net core layer. Also, the network drivers which are not used by BF are disabled to avoid the fix of conflicts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1962490/+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 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
** Bug watch added: Debian Bug tracker #996104 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996104 ** Also affects: dkms (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996104 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: In Progress Status in dkms package in Debian: Unknown Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1963835/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
** Merge proposal linked: https://code.launchpad.net/~racb/ubuntu/+source/dkms/+git/dkms/+merge/418225 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: In Progress Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1963835/+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 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
I just hit this. The problem is in /etc/kernel/prerm.d/dkms:
Lines 16 and 17:
name=`echo "$line" | awk '{print $1}' | sed 's/,$//'` | cut -d'/' -f1
vers=`echo "$line" | awk '{print $1}' | sed 's/,$//'` | cut -d'/' -f2
In my case, $line is:
v4l2loopback/0.12.5, 5.13.0-30-generic, x86_64: installed
And so it's clear to me that those parsing lines are incorrect and the
backticks should be at the end.
Looking upstream, I then found:
https://github.com/dell/dkms/commit/64a882a32fdf126ef20e6b6403b5cb158dad21f4
So this just needs cherry-picking.
** Changed in: dkms (Ubuntu)
Status: Confirmed => In Progress
** Changed in: dkms (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1963835
Title:
Message: "Error! Arguments and are not
specified." when upgrading
Status in dkms package in Ubuntu:
In Progress
Bug description:
Running pre-release Xubuntu 22.04.
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
Codename: jammy
Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan
21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
After upgrading from 21.04 tot 22.04 I did:
sudo apt update && sudo apt full-upgrade
I saw this message in the output:
dkms: removing: (5.13.0-30-generic) (x86_64)
Error! Arguments and are not specified.
Usage: remove / or
remove -m / or
remove -m -v
All the output:
willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade
[sudo] wachtwoord voor willem:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar
Opwaardering wordt doorgerekend... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer
nodig:
libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl
libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common
libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0
libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30
linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic
linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic
perl-modules-5.32 pkg-config python3-certifi python3-requests
python3-simplejson
Gebruik 'sudo apt autoremove' om ze te verwijderen.
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet
opgewaardeerd.
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar
Opwaardering wordt doorgerekend... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer
nodig:
libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl
libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common
libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0
libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30
perl-modules-5.32 pkg-config python3-certifi python3-requests
python3-simplejson
Gebruik 'sudo apt autoremove' om ze te verwijderen.
De volgende pakketten zullen VERWIJDERD worden:
linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic
linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic
0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet
opgewaardeerd.
Na deze bewerking zal er 428 MB schijfruimte vrijkomen.
Wilt u doorgaan? [J/n]
(Database wordt ingelezen ... 402831 bestanden en mappen momenteel
geïnstalleerd
.)
linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ...
linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ...
linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ...
linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..]
/etc/kernel/prerm.d/dkms:
dkms: removing: (5.13.0-30-generic) (x86_64)
Error! Arguments and are not specified.
Usage: remove / or
remove -m / or
remove -m -v
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic
/etc/kernel/postrm.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.0-18-generic
Found initrd image: /boot/initrd.img-5.15.0-18-generic
Found linux image: /boot/vmlinuz-5.13.0-32-generic
Found initrd image: /boot/initrd.img-5.13.0-32-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will be executed to detect other
[Kernel-packages] [Bug 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: Confirmed Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1963835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1967510] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1967510 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1967510 Title: IPU6: 2022-04-01 Andrews MLK PV release Status in linux package in Ubuntu: Incomplete Bug description: See https://github.com/intel/ipu6-drivers/commit/8d3d4b24973354d7a522debe1b18f21f825092dc This should be a follow-up to bug 1964983, whose SRU has been accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967510/+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 1967510] [NEW] IPU6: 2022-04-01 Andrews MLK PV release
Public bug reported: See https://github.com/intel/ipu6-drivers/commit/8d3d4b24973354d7a522debe1b18f21f825092dc This should be a follow-up to bug 1964983, whose SRU has been accepted. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1967510 Title: IPU6: 2022-04-01 Andrews MLK PV release Status in linux package in Ubuntu: New Bug description: See https://github.com/intel/ipu6-drivers/commit/8d3d4b24973354d7a522debe1b18f21f825092dc This should be a follow-up to bug 1964983, whose SRU has been accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967510/+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 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-April/129095.html (oem-5.14, oem-5.17, jammy, unstable)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ WCN6856 BT keep in OFF state after coldboot system.
+
+ [Fix]
+
+ Mainline commit 599ece4f8f07 ("Bluetooth: btusb: Improve stability for
+ QCA devices") added a 100ms delay for the underlying hw to apply
+ downloaded firmware.
+
+ [Test Case]
+
+ This can be reproduced and therefore verified by checkbox poweroff
+ stress test:
+
+ $ checkbox-cli run com.canonical.certification::stress/poweroff
+
+ [Where problems could occur]
+
+ Unlikely to have side effect so far except slowing down boot process for
+ a tiny moment.
+
+ [Other Info]
+
+ While this is only in the v5.18 merge window, all the kernels in use are
+ affected and nominated here.
+
+ == original bug report ==
+
[Reproduce Steps]
1.Insert WCN6856 card to SUT.
2.Press power button to power on SUT.
3.Clean install Ubuntu 20.04.
4.Check BT function after installation is complete.
5.Coldboot system and check the BT function.
6.Repeat step5, Issue occur.
7.Only found with CB, can't reproduce on WB.
[Results]
- Expected Result
- BT function work normally.
- Actual Result
- BT has no function. Can't turn ON BT function. Need CB to recover BT
function.
- "WB" and "swicth tab" cannot restore the BT function.
+ Expected Result
+ BT function work normally.
+ Actual Result
+ BT has no function. Can't turn ON BT function. Need CB to recover BT
function.
+ "WB" and "swicth tab" cannot restore the BT function.
[Others]
Wifi function work normally.
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1967067
Title:
WCN6856 BT keep in OFF state after coldboot system
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
In Progress
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
In Progress
Bug description:
[SRU Justification]
[Impact]
WCN6856 BT keep in OFF state after coldboot system.
[Fix]
Mainline commit 599ece4f8f07 ("Bluetooth: btusb: Improve stability for
QCA devices") added a 100ms delay for the underlying hw to apply
downloaded firmware.
[Test Case]
This can be reproduced and therefore verified by checkbox poweroff
stress test:
$ checkbox-cli run com.canonical.certification::stress/poweroff
[Where problems could occur]
Unlikely to have side effect so far except slowing down boot process for
a tiny moment.
[Other Info]
While this is only in the v5.18 merge window, all the kernels in use are
affected and nominated here.
== original bug report ==
[Reproduce Steps]
1.Insert WCN6856 card to SUT.
2.Press power button to power on SUT.
3.Clean install Ubuntu 20.04.
4.Check BT function after installation is complete.
5.Coldboot system and check the BT function.
6.Repeat step5, Issue occur.
7.Only found with CB, can't reproduce on WB.
[Results]
Expected Result
BT function work normally.
Actual Result
BT has no function. Can't turn ON BT function. Need CB to recover BT
function.
"WB" and "swicth tab" cannot restore the BT function.
[Others]
Wifi function work normally.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1967067/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs
** Changed in: cloud-init (Ubuntu) Status: Incomplete => Confirmed ** Changed in: cloud-init Assignee: (unassigned) => Arthit Kosachunhanun (richshops) ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Arthit Kosachunhanun (richshops) ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Arthit Kosachunhanun (richshops) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Arthit Kosachunhanun (richshops) -- 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/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Won't Fix Status in apparmor package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud- init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. Related bugs: * bug 1645644: cloud-init ntp not using expected servers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1966093] Autopkgtest regression report (nvidia-graphics-drivers-510/510.60.02-0ubuntu0.21.10.2)
All autopkgtests for the newly accepted nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.2) for impish have finished running. The following regressions have been reported in tests triggered by the package: pyopencl/2021.1.2-1build2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#nvidia-graphics-drivers-510 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1966093 Title: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Committed Status in linux-restricted-modules source package in Bionic: Triaged Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Focal: Triaged Status in nvidia-graphics-drivers-390 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-510 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Impish: Triaged Status in nvidia-graphics-drivers-390 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-510 source package in Impish: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] === 510 impish/focal/bionic === * New upstream release (LP: #1966093): - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. === 390 impish/focal/bionic === * New upstream release (LP: #1966093): - Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided. - Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory". [ Dimitri John Ledkov ] * debian/dkms_nvidia/patches/buildfix_kernel_5.13_armhf.patch: - Fix armhf builds. * debian/dkms_nvidia/patches/buildfix_kernel_5.17.patch: - Fix build failure with Linux 5.17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+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 1965737] Re: Focal update: upstream stable patchset 2022-03-21
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965737 Title: Focal update: upstream stable patchset 2022-03-21 Status in linux-oem-5.14 package in Ubuntu: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-03-21 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1965737/+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 1967474] Re: Thinkpad X1 Carbon Gen 9 waking up during sleep
*** This bug is a duplicate of bug 1965737 *** https://bugs.launchpad.net/bugs/1965737 this is queued via stable backports ** This bug has been marked a duplicate of bug 1965737 Focal update: upstream stable patchset 2022-03-21 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967474 Title: Thinkpad X1 Carbon Gen 9 waking up during sleep Status in linux-oem-5.14 package in Ubuntu: New Bug description: This is apparently caused by "ACPI: PM: s2idle: Cancel wakeup before dispatching EC GPE" which has been reverted in recent kernels (https://www.spinics.net/lists/kernel/msg4274673.html) would be nice to have it reverted here too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1967474/+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 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
** Description changed: [Impact] vmx_ldtr_test in ubuntu_kvm_unit_tests will fail with: - FAIL: Expected 0 for L1 LDTR selector (got 50) + FAIL: Expected 0 for L1 LDTR selector (got 50) It's a test for commit afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" According to Intel 64 and IA-32 Architectures Software Developer’s Manual, L1's LDTR should be 0 after an emulated VM-exit from L2. [Fix] - * afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" + * afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value + on nested VM-Exit" We already have this patch in Jammy. - This patch can be cherry-picked into F/F-OEM-5.14/I. But backport is required for - Bionic, as the code snippet for nested KVM haven't been split out to - vmx/nested.c (55d2375e KVM: nVMX: Move nested code to dedicated files). + This patch can be cherry-picked into F/F-OEM-5.14/I. But backport is + required for Bionic, as the code snippet for nested KVM haven't been + split out to vmx/nested.c (55d2375e KVM: nVMX: Move nested code to + dedicated files). [Test] Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1956315-vmx-ldtr/ Tested with: - * B (bare-metal) - * F (KVM instance) - * I (bare-metal) + * B (bare-metal) + * F (KVM instance) + * I (bare-metal) With this patched kernel, this test will pass: - PASS: Expected 0 for L1 LDTR selector (got 0) + PASS: Expected 0 for L1 LDTR selector (got 0) Also tested with ubuntu_kvm_unit_tests and ubuntu_kvm_smoke_test to make sure this is not causing any other regressions. [Where problem could occur] If the patch is incorrect it might affect the nested KVM functionality while existing from L2 to L1. - [Original bug description] Issue found on Bionic 4.15.0-166.174 with node rizzo Running 'kvm-ok' INFO: /dev/kvm exists KVM acceleration can be used '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=8a30588c timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Lnfifekq7r -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.i9y5hdMh49 enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP filter = vmx_ldtr_test, test = int3 filter = vmx_ldtr_test, test = into filter = vmx_ldtr_test, test = exit_monitor_from_l2_test filter = vmx_ldtr_test, test = invalid_msr filter = vmx_ldtr_test, test = v2_null_test filter = vmx_ldtr_test, test = v2_multiple_entries_test filter = vmx_ldtr_test, test = fixture_test_case1 filter = vmx_ldtr_test, test = fixture_test_case2 filter = vmx_ldtr_test, test = invvpid_test filter = vmx_ldtr_test, test = vmx_controls_test filter = vmx_ldtr_test, test = vmx_host_state_area_test filter = vmx_ldtr_test, test = vmx_guest_state_area_test filter = vmx_ldtr_test, test = vmentry_movss_shadow_test filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test filter = vmx_ldtr_test, test = apic_reg_virt_test filter = vmx_ldtr_test, test = virt_x2apic_mode_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test filter =
[Kernel-packages] [Bug 1956315] Re: vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR selector (got 50))
** Description changed: + [Impact] + vmx_ldtr_test in ubuntu_kvm_unit_tests will fail with: + FAIL: Expected 0 for L1 LDTR selector (got 50) + + It's a test for commit afc8de01 "KVM: nVMX: Set LDTR to its + architecturally defined value on nested VM-Exit" + + According to Intel 64 and IA-32 Architectures Software Developer’s + Manual, L1's LDTR should be 0 after an emulated VM-exit from L2. + + [Fix] + * afc8de01 "KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit" + + We already have this patch in Jammy. + This patch can be cherry-picked into F/F-OEM-5.14/I. But backport is required for + Bionic, as the code snippet for nested KVM haven't been split out to + vmx/nested.c (55d2375e KVM: nVMX: Move nested code to dedicated files). + + [Test] + Test kernels can be found here: + https://people.canonical.com/~phlin/kernel/lp-1956315-vmx-ldtr/ + + Tested with: + * B (bare-metal) + * F (KVM instance) + * I (bare-metal) + + With this patched kernel, this test will pass: + PASS: Expected 0 for L1 LDTR selector (got 0) + + Also tested with ubuntu_kvm_unit_tests and ubuntu_kvm_smoke_test to + make sure this is not causing any other regressions. + + [Where problem could occur] + If the patch is incorrect it might affect the nested KVM functionality + while existing from L2 to L1. + + + [Original bug description] Issue found on Bionic 4.15.0-166.174 with node rizzo Running 'kvm-ok' INFO: /dev/kvm exists KVM acceleration can be used '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test' BUILD_HEAD=8a30588c timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Lnfifekq7r -smp 1 -cpu max,+vmx -append vmx_ldtr_test # -initrd /tmp/tmp.i9y5hdMh49 enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 filter = vmx_ldtr_test, test = test_vmx_feature_control filter = vmx_ldtr_test, test = test_vmxon filter = vmx_ldtr_test, test = test_vmptrld filter = vmx_ldtr_test, test = test_vmclear filter = vmx_ldtr_test, test = test_vmptrst filter = vmx_ldtr_test, test = test_vmwrite_vmread filter = vmx_ldtr_test, test = test_vmcs_high filter = vmx_ldtr_test, test = test_vmcs_lifecycle filter = vmx_ldtr_test, test = test_vmx_caps filter = vmx_ldtr_test, test = test_vmread_flags_touch filter = vmx_ldtr_test, test = test_vmwrite_flags_touch filter = vmx_ldtr_test, test = null filter = vmx_ldtr_test, test = vmenter filter = vmx_ldtr_test, test = preemption timer filter = vmx_ldtr_test, test = control field PAT filter = vmx_ldtr_test, test = control field EFER filter = vmx_ldtr_test, test = CR shadowing filter = vmx_ldtr_test, test = I/O bitmap filter = vmx_ldtr_test, test = instruction intercept filter = vmx_ldtr_test, test = EPT A/D disabled filter = vmx_ldtr_test, test = EPT A/D enabled filter = vmx_ldtr_test, test = PML filter = vmx_ldtr_test, test = interrupt filter = vmx_ldtr_test, test = nmi_hlt filter = vmx_ldtr_test, test = debug controls filter = vmx_ldtr_test, test = MSR switch filter = vmx_ldtr_test, test = vmmcall filter = vmx_ldtr_test, test = disable RDTSCP filter = vmx_ldtr_test, test = int3 filter = vmx_ldtr_test, test = into filter = vmx_ldtr_test, test = exit_monitor_from_l2_test filter = vmx_ldtr_test, test = invalid_msr filter = vmx_ldtr_test, test = v2_null_test filter = vmx_ldtr_test, test = v2_multiple_entries_test filter = vmx_ldtr_test, test = fixture_test_case1 filter = vmx_ldtr_test, test = fixture_test_case2 filter = vmx_ldtr_test, test = invvpid_test filter = vmx_ldtr_test, test = vmx_controls_test filter = vmx_ldtr_test, test = vmx_host_state_area_test filter = vmx_ldtr_test, test = vmx_guest_state_area_test filter = vmx_ldtr_test, test = vmentry_movss_shadow_test filter = vmx_ldtr_test, test = vmentry_unrestricted_guest_test filter = vmx_ldtr_test, test = vmx_eoi_bitmap_ioapic_scan_test filter = vmx_ldtr_test, test = vmx_hlt_with_rvi_test filter = vmx_ldtr_test, test = apic_reg_virt_test filter = vmx_ldtr_test, test = virt_x2apic_mode_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_thread_test filter = vmx_ldtr_test, test = vmx_apic_passthrough_tpr_threshold_test filter = vmx_ldtr_test, test = vmx_init_signal_test filter = vmx_ldtr_test, test = vmx_sipi_signal_test filter = vmx_ldtr_test, test = vmx_vmcs_shadow_test filter = vmx_ldtr_test, test = vmx_ldtr_test Test suite: vmx_ldtr_test PASS: Expected 18 for L2 LDTR selector (got 18) FAIL: Expected 0 for L1 LDTR selector (got 50) filter = vmx_ldtr_test, test = vmx_cr_load_test filter = vmx_ldtr_test, test =
[Kernel-packages] [Bug 1965002] Re: AWS: Hibernate resume crashes when platform changes
This bug was fixed in the package linux-aws - 5.15.0-1003.5
---
linux-aws (5.15.0-1003.5) jammy; urgency=medium
* jammy/linux-aws: 5.15.0-1003.5 -proposed tracker (LP: #1965768)
* AWS: Hibernate resume crashes when platform changes (LP: #1965002)
- PM: hibernate: Allow ACPI hardware signature to be honoured
- PM: hibernate: Honour ACPI hardware signature by default for virtual
guests
* dependency on crda obsolete according to Debian (LP: #1958918)
- [Packaging] switch dependency from crda to wireless-regdb
* tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
- [Packaging] aws: Include tcm_loop.ko
* Miscellaneous Ubuntu changes
- [Config] aws: Sync configs with master
[ Ubuntu: 5.15.0-23.23 ]
* jammy/linux: 5.15.0-23.23 -proposed tracker (LP: #1964573)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/master)
* [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests
(LP: #1959977)
- KVM: s390: pv: make use of ultravisor AIV support
* intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
(LP: #1958004)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs
* CVE-2022-23960
- ARM: report Spectre v2 status through sysfs
- ARM: early traps initialisation
- ARM: use LOADADDR() to get load address of sections
- ARM: Spectre-BHB workaround
- ARM: include unprivileged BPF status in Spectre V2 reporting
- arm64: Add Neoverse-N2, Cortex-A710 CPU part definition
- arm64: Add HWCAP for self-synchronising virtual counter
- arm64: Add Cortex-X2 CPU part definition
- arm64: add ID_AA64ISAR2_EL1 sys register
- arm64: cpufeature: add HWCAP for FEAT_AFP
- arm64: cpufeature: add HWCAP for FEAT_RPRES
- arm64: entry.S: Add ventry overflow sanity checks
- arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
- KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
- arm64: entry: Make the trampoline cleanup optional
- arm64: entry: Free up another register on kpti's tramp_exit path
- arm64: entry: Move the trampoline data page before the text page
- arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
- arm64: entry: Don't assume tramp_vectors is the start of the vectors
- arm64: entry: Move trampoline macros out of ifdef'd section
- arm64: entry: Make the kpti trampoline's kpti sequence optional
- arm64: entry: Allow the trampoline text to occupy multiple pages
- arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
- arm64: entry: Add vectors that have the bhb mitigation sequences
- arm64: entry: Add macro for reading symbol addresses from the trampoline
- arm64: Add percpu vectors for EL1
- arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of
Spectre-v2
- arm64: Mitigate spectre style branch history side channels
- KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
- arm64: Use the clearbhb instruction in mitigations
- arm64: proton-pack: Include unprivileged eBPF status in Spectre v2
mitigation reporting
- ARM: fix build error when BPF_SYSCALL is disabled
* CVE-2021-26401
- x86/speculation: Use generic retpoline by default on AMD
- x86/speculation: Update link to AMD speculation whitepaper
- x86/speculation: Warn about Spectre v2 LFENCE mitigation
- x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
* CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- x86/speculation: Add eIBRS + Retpoline options
- Documentation/hw-vuln: Update spectre doc
- x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation
reporting
* Jammy update: v5.15.27 upstream stable release (LP: #1964361)
- mac80211_hwsim: report NOACK frames in tx_status
- mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work
- i2c: bcm2835: Avoid clock stretching timeouts
- ASoC: rt5668: do not block workqueue if card is unbound
- ASoC: rt5682: do not block workqueue if card is unbound
- regulator: core: fix false positive in regulator_late_cleanup()
- Input: clear BTN_RIGHT/MIDDLE on buttonpads
- btrfs: get rid of warning on transaction commit when using flushoncommit
- KVM: arm64: vgic: Read HW interrupt pending state from the HW
- block: loop:use kstatfs.f_bsize of backing file to set discard granularity
- tipc: fix a bit overflow in tipc_crypto_key_rcv()
- cifs: do not use uninitialized data in the owner/group sid
- cifs: fix double free race when mount fails in cifs_get_root()
- cifs: modefromsids must add an ACE for authenticated users
- selftests/seccomp: Fix seccomp failure by
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
This bug was fixed in the package linux-aws - 5.15.0-1003.5
---
linux-aws (5.15.0-1003.5) jammy; urgency=medium
* jammy/linux-aws: 5.15.0-1003.5 -proposed tracker (LP: #1965768)
* AWS: Hibernate resume crashes when platform changes (LP: #1965002)
- PM: hibernate: Allow ACPI hardware signature to be honoured
- PM: hibernate: Honour ACPI hardware signature by default for virtual
guests
* dependency on crda obsolete according to Debian (LP: #1958918)
- [Packaging] switch dependency from crda to wireless-regdb
* tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
- [Packaging] aws: Include tcm_loop.ko
* Miscellaneous Ubuntu changes
- [Config] aws: Sync configs with master
[ Ubuntu: 5.15.0-23.23 ]
* jammy/linux: 5.15.0-23.23 -proposed tracker (LP: #1964573)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/master)
* [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests
(LP: #1959977)
- KVM: s390: pv: make use of ultravisor AIV support
* intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
(LP: #1958004)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs
* CVE-2022-23960
- ARM: report Spectre v2 status through sysfs
- ARM: early traps initialisation
- ARM: use LOADADDR() to get load address of sections
- ARM: Spectre-BHB workaround
- ARM: include unprivileged BPF status in Spectre V2 reporting
- arm64: Add Neoverse-N2, Cortex-A710 CPU part definition
- arm64: Add HWCAP for self-synchronising virtual counter
- arm64: Add Cortex-X2 CPU part definition
- arm64: add ID_AA64ISAR2_EL1 sys register
- arm64: cpufeature: add HWCAP for FEAT_AFP
- arm64: cpufeature: add HWCAP for FEAT_RPRES
- arm64: entry.S: Add ventry overflow sanity checks
- arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
- KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
- arm64: entry: Make the trampoline cleanup optional
- arm64: entry: Free up another register on kpti's tramp_exit path
- arm64: entry: Move the trampoline data page before the text page
- arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
- arm64: entry: Don't assume tramp_vectors is the start of the vectors
- arm64: entry: Move trampoline macros out of ifdef'd section
- arm64: entry: Make the kpti trampoline's kpti sequence optional
- arm64: entry: Allow the trampoline text to occupy multiple pages
- arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
- arm64: entry: Add vectors that have the bhb mitigation sequences
- arm64: entry: Add macro for reading symbol addresses from the trampoline
- arm64: Add percpu vectors for EL1
- arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of
Spectre-v2
- arm64: Mitigate spectre style branch history side channels
- KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
- arm64: Use the clearbhb instruction in mitigations
- arm64: proton-pack: Include unprivileged eBPF status in Spectre v2
mitigation reporting
- ARM: fix build error when BPF_SYSCALL is disabled
* CVE-2021-26401
- x86/speculation: Use generic retpoline by default on AMD
- x86/speculation: Update link to AMD speculation whitepaper
- x86/speculation: Warn about Spectre v2 LFENCE mitigation
- x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
* CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- x86/speculation: Add eIBRS + Retpoline options
- Documentation/hw-vuln: Update spectre doc
- x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation
reporting
* Jammy update: v5.15.27 upstream stable release (LP: #1964361)
- mac80211_hwsim: report NOACK frames in tx_status
- mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work
- i2c: bcm2835: Avoid clock stretching timeouts
- ASoC: rt5668: do not block workqueue if card is unbound
- ASoC: rt5682: do not block workqueue if card is unbound
- regulator: core: fix false positive in regulator_late_cleanup()
- Input: clear BTN_RIGHT/MIDDLE on buttonpads
- btrfs: get rid of warning on transaction commit when using flushoncommit
- KVM: arm64: vgic: Read HW interrupt pending state from the HW
- block: loop:use kstatfs.f_bsize of backing file to set discard granularity
- tipc: fix a bit overflow in tipc_crypto_key_rcv()
- cifs: do not use uninitialized data in the owner/group sid
- cifs: fix double free race when mount fails in cifs_get_root()
- cifs: modefromsids must add an ACE for authenticated users
- selftests/seccomp: Fix seccomp failure by
[Kernel-packages] [Bug 1959593] Re: tcm_loop requires '-extras' for EKS optimised AMIs
This bug was fixed in the package linux-aws - 5.15.0-1003.5
---
linux-aws (5.15.0-1003.5) jammy; urgency=medium
* jammy/linux-aws: 5.15.0-1003.5 -proposed tracker (LP: #1965768)
* AWS: Hibernate resume crashes when platform changes (LP: #1965002)
- PM: hibernate: Allow ACPI hardware signature to be honoured
- PM: hibernate: Honour ACPI hardware signature by default for virtual
guests
* dependency on crda obsolete according to Debian (LP: #1958918)
- [Packaging] switch dependency from crda to wireless-regdb
* tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
- [Packaging] aws: Include tcm_loop.ko
* Miscellaneous Ubuntu changes
- [Config] aws: Sync configs with master
[ Ubuntu: 5.15.0-23.23 ]
* jammy/linux: 5.15.0-23.23 -proposed tracker (LP: #1964573)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
- debian/dkms-versions -- update from kernel-versions (main/master)
* [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests
(LP: #1959977)
- KVM: s390: pv: make use of ultravisor AIV support
* intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
(LP: #1958004)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs
* CVE-2022-23960
- ARM: report Spectre v2 status through sysfs
- ARM: early traps initialisation
- ARM: use LOADADDR() to get load address of sections
- ARM: Spectre-BHB workaround
- ARM: include unprivileged BPF status in Spectre V2 reporting
- arm64: Add Neoverse-N2, Cortex-A710 CPU part definition
- arm64: Add HWCAP for self-synchronising virtual counter
- arm64: Add Cortex-X2 CPU part definition
- arm64: add ID_AA64ISAR2_EL1 sys register
- arm64: cpufeature: add HWCAP for FEAT_AFP
- arm64: cpufeature: add HWCAP for FEAT_RPRES
- arm64: entry.S: Add ventry overflow sanity checks
- arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
- KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
- arm64: entry: Make the trampoline cleanup optional
- arm64: entry: Free up another register on kpti's tramp_exit path
- arm64: entry: Move the trampoline data page before the text page
- arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
- arm64: entry: Don't assume tramp_vectors is the start of the vectors
- arm64: entry: Move trampoline macros out of ifdef'd section
- arm64: entry: Make the kpti trampoline's kpti sequence optional
- arm64: entry: Allow the trampoline text to occupy multiple pages
- arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
- arm64: entry: Add vectors that have the bhb mitigation sequences
- arm64: entry: Add macro for reading symbol addresses from the trampoline
- arm64: Add percpu vectors for EL1
- arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of
Spectre-v2
- arm64: Mitigate spectre style branch history side channels
- KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
- arm64: Use the clearbhb instruction in mitigations
- arm64: proton-pack: Include unprivileged eBPF status in Spectre v2
mitigation reporting
- ARM: fix build error when BPF_SYSCALL is disabled
* CVE-2021-26401
- x86/speculation: Use generic retpoline by default on AMD
- x86/speculation: Update link to AMD speculation whitepaper
- x86/speculation: Warn about Spectre v2 LFENCE mitigation
- x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
* CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- x86/speculation: Add eIBRS + Retpoline options
- Documentation/hw-vuln: Update spectre doc
- x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation
reporting
* Jammy update: v5.15.27 upstream stable release (LP: #1964361)
- mac80211_hwsim: report NOACK frames in tx_status
- mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work
- i2c: bcm2835: Avoid clock stretching timeouts
- ASoC: rt5668: do not block workqueue if card is unbound
- ASoC: rt5682: do not block workqueue if card is unbound
- regulator: core: fix false positive in regulator_late_cleanup()
- Input: clear BTN_RIGHT/MIDDLE on buttonpads
- btrfs: get rid of warning on transaction commit when using flushoncommit
- KVM: arm64: vgic: Read HW interrupt pending state from the HW
- block: loop:use kstatfs.f_bsize of backing file to set discard granularity
- tipc: fix a bit overflow in tipc_crypto_key_rcv()
- cifs: do not use uninitialized data in the owner/group sid
- cifs: fix double free race when mount fails in cifs_get_root()
- cifs: modefromsids must add an ACE for authenticated users
- selftests/seccomp: Fix seccomp failure by
[Kernel-packages] [Bug 1965075] Re: arm64 suport
This bug was fixed in the package linux-gcp - 5.15.0-1002.5 --- linux-gcp (5.15.0-1002.5) jammy; urgency=medium * jammy/linux-gcp: 5.15.0-1002.5 -proposed tracker (LP: #1965077) * arm64 suport (LP: #1965075) - [packaging] arm64 bringup - [config] Import arm64 config from master and update-configs - [packaging] update annotations for arm64 -- Khalid Elmously Tue, 15 Mar 2022 23:44:47 -0400 ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1965075 Title: arm64 suport Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Bionic: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: Fix Released Bug description: [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1965075/+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 1965564] Re: Enable KMS by default in the packaging
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.60.02-0ubuntu1 --- nvidia-graphics-drivers-510 (510.60.02-0ubuntu1) jammy; urgency=medium * New upstream release: - Added support for the following GPUs: NVIDIA RTX A4000H NVIDIA RTX A5500 - Fixed a bug that could cause displays with HDMI or DisplayPort audio to be deselected as the default audio output device after resuming from suspend. - Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT- switches - Fixed a bug, introduced in 495.29.05, that caused GPU "Model:" in /proc/driver/nvidia/gpus//information to be "Unknown" for some GPUs. * debian/templates/nvidia-graphics-drivers-kms.conf.in, debian/templates/nvidia-kernel-common-flavour.install.in: - Enable KMS by default in /etc/modprobe.d (LP: #1965564). -- Alberto Milone Wed, 23 Mar 2022 09:45:07 + ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1965564 Title: Enable KMS by default in the packaging Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Bug description: Installing NVIDIA's 510 driver using the ubuntu-drivers tool enables KMS by default. The same should happen when installing the driver through apt or the UI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1965564/+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
