[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-ibm/5.15.0-1028.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-ibm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.17/5.17.0.1030.28)
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1030.28) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu12~22.04.1 (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/jammy/update_excuses.html#linux-meta-oem-5.17 [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 packaging 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 2006937] Re: Update the NVIDIA 525 series to 525.89.02
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.105.17-0ubuntu1 --- nvidia-graphics-drivers-525 (525.105.17-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2012529). -- Alberto Milone Mon, 27 Mar 2023 11:29:08 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2006937 Title: Update the NVIDIA 525 series to 525.89.02 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released 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] 525.89.02 [Kinetic, Jammy] * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. * debian/templates/control.in: - Switch libcuda1 and libnvidia-ml1 Provides to libcuda.so.1 and libnvidia-ml.so.1. This makes CUDA (from Multiverse) installable again. [Focal, Bionic] * New upstream release (LP: #2006937): - Fixed a bug that could cause banding or flickering of color gradients on DisplayPort monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2006937/+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 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.105.17-0ubuntu1
---
nvidia-graphics-drivers-525 (525.105.17-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
-- Alberto Milone Mon, 27 Mar 2023
11:29:08 +
** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in fabric-manager-470 source package in Kinetic:
New
Status in fabric-manager-515 source package in Kinetic:
[Kernel-packages] [Bug 2008823] Re: /sys/kernel/boot_params/data leaks random data
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Confirmed Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-raspi2/4.15.0-1130.138 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-raspi2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc.
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-oracle/4.15.0-1117.128 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc.
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-gcp/5.19.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc.
[Kernel-packages] [Bug 2015414] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2015414 Title: 5.15.0-69 ice driver deadlocks with bonded e810 NICs Status in linux package in Ubuntu: Confirmed Bug description: The ice driver in the 5.15.0-69 kernel deadlocks on rtnl_lock() when adding e810 NICs to a bond interface. Booting with `sysctl.hung_task_panic=1` and `sysctl.hung_task_all_cpu_backtrace=1` added to the kernel command-line shows (among lots of other output): ``` [ 244.980100] INFO: task kworker/6:1:182 blocked for more than 120 seconds. [ 244.988431] Not tainted 5.15.0-69-generic #76-Ubuntu [ 244.995279] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.004826] task:kworker/6:1 state:D stack:0 pid: 182 ppid: 2 flags:0x4000 [ 245.015017] Workqueue: events linkwatch_event [ 245.020734] Call Trace: [ 245.024144] [ 245.027137] __schedule+0x24e/0x590 [ 245.031848] schedule+0x69/0x110 [ 245.036228] schedule_preempt_disabled+0xe/0x20 [ 245.042066] __mutex_lock.constprop.0+0x267/0x490 [ 245.047993] __mutex_lock_slowpath+0x13/0x20 [ 245.053432] mutex_lock+0x38/0x50 [ 245.057714] rtnl_lock+0x15/0x20 [ 245.061901] linkwatch_event+0xe/0x30 [ 245.066571] process_one_work+0x228/0x3d0 [ 245.071607] worker_thread+0x53/0x420 [ 245.076260] ? process_one_work+0x3d0/0x3d0 [ 245.081493] kthread+0x127/0x150 [ 245.085592] ? set_kthread_struct+0x50/0x50 [ 245.090769] ret_from_fork+0x1f/0x30 [ 245.095266] ``` and ``` [ 245.530629] INFO: task ifenslave:849 blocked for more than 121 seconds. [ 245.540433] Not tainted 5.15.0-69-generic #76-Ubuntu [ 245.549050] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.558960] task:ifenslave state:D stack:0 pid: 849 ppid: 847 flags:0x4002 [ 245.570930] Call Trace: [ 245.576175] [ 245.581018] __schedule+0x24e/0x590 [ 245.587445] schedule+0x69/0x110 [ 245.593631] schedule_timeout+0x103/0x140 [ 245.600573] __wait_for_common+0xab/0x150 [ 245.607526] ? usleep_range_state+0x90/0x90 [ 245.614743] wait_for_completion+0x24/0x30 [ 245.621903] flush_workqueue+0x133/0x3e0 [ 245.628887] ib_cache_cleanup_one+0x21/0xf0 [ib_core] [ 245.637083] __ib_unregister_device+0x79/0xc0 [ib_core] [ 245.645398] ib_unregister_device+0x27/0x40 [ib_core] [ 245.653541] irdma_ib_unregister_device+0x4b/0x70 [irdma] [ 245.662105] irdma_remove+0x1f/0x70 [irdma] [ 245.669446] auxiliary_bus_remove+0x1d/0x40 [ 245.676688] __device_release_driver+0x1a8/0x2a0 [ 245.684241] device_release_driver+0x29/0x40 [ 245.691416] bus_remove_device+0xde/0x150 [ 245.698396] device_del+0x19c/0x400 [**712178] ice_lag_link.isra.0+0xdd/0xf0 [ice] m] (3 of 5) A start job is runni[ 245.720683] ice_lag_changeupper_event+0xe1/0x130 [ice] ng for\u2026rk interfaces (3min 47s[ 245.729739] ice_lag_event_handler+0x5b/0x150 [ice] / 5min 3s) [ 245.738525] raw_notifier_call_chain+0x46/0x60 [ 245.746006] call_netdevice_notifiers_info+0x52/0xa0 [ 245.754123] __netdev_upper_dev_link+0x1b7/0x310 [ 245.761658] netdev_master_upper_dev_link+0x3e/0x60 [ 245.769627] bond_enslave+0xc3a/0x1720 [bonding] [ 245.777398] ? sscanf+0x4e/0x70 [ 245.783375] bond_option_slaves_set+0xca/0x170 [bonding] [ 245.791738] __bond_opt_set+0xbd/0x1a0 [bonding] [ 245.799505] __bond_opt_set_notify+0x30/0xb0 [bonding] [ 245.807860] bond_opt_tryset_rtnl+0x56/0xa0 [bonding] [ 245.816062] bonding_sysfs_store_option+0x52/0xa0 [bonding] [ 245.824750] dev_attr_store+0x14/0x30 [ 245.831443] sysfs_kf_write+0x3b/0x50 [ 245.837979] kernfs_fop_write_iter+0x138/0x1c0 [ 245.845469] new_sync_write+0x111/0x1a0 [ 245.852210] vfs_write+0x1d5/0x270 [ 245.858429] ksys_write+0x67/0xf0 [ 245.864624] __x64_sys_write+0x19/0x20 [ 245.871288] do_syscall_64+0x59/0xc0 [ 245.877715] ? handle_mm_fault+0xd8/0x2c0 [ 245.884566] ? do_user_addr_fault+0x1e7/0x670 [ 245.891990] ? filp_close+0x60/0x70 [ 245.898452] ? exit_to_user_mode_prepare+0x37/0xb0 [ 245.906272] ? irqentry_exit_to_user_mode+0x9/0x20 [ 245.914042] ? irqentry_exit+0x1d/0x30 [ 245.920703] ? exc_page_fault+0x89/0x170 [ 245.927555] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 245.935763] RIP: 0033:0x7f1e86855a37 [ 245.942153] RSP: 002b:7fff8da477a8 EFLAGS: 0246 ORIG_RAX: 0001 [ 245.953034] RAX: ffda RBX: 000a RCX: 7f1e86855a37 [ 245.963554] RDX: 000a RSI: 556eff580510 RDI: 0001 [ 245.972468] RBP: 556eff580510 R08: 556eff582c5a R09: [
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-ibm/5.4.0-1047.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-ibm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual
[Kernel-packages] [Bug 2015414] [NEW] 5.15.0-69 ice driver deadlocks with bonded e810 NICs
Public bug reported: The ice driver in the 5.15.0-69 kernel deadlocks on rtnl_lock() when adding e810 NICs to a bond interface. Booting with `sysctl.hung_task_panic=1` and `sysctl.hung_task_all_cpu_backtrace=1` added to the kernel command-line shows (among lots of other output): ``` [ 244.980100] INFO: task kworker/6:1:182 blocked for more than 120 seconds. [ 244.988431] Not tainted 5.15.0-69-generic #76-Ubuntu [ 244.995279] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.004826] task:kworker/6:1 state:D stack:0 pid: 182 ppid: 2 flags:0x4000 [ 245.015017] Workqueue: events linkwatch_event [ 245.020734] Call Trace: [ 245.024144] [ 245.027137] __schedule+0x24e/0x590 [ 245.031848] schedule+0x69/0x110 [ 245.036228] schedule_preempt_disabled+0xe/0x20 [ 245.042066] __mutex_lock.constprop.0+0x267/0x490 [ 245.047993] __mutex_lock_slowpath+0x13/0x20 [ 245.053432] mutex_lock+0x38/0x50 [ 245.057714] rtnl_lock+0x15/0x20 [ 245.061901] linkwatch_event+0xe/0x30 [ 245.066571] process_one_work+0x228/0x3d0 [ 245.071607] worker_thread+0x53/0x420 [ 245.076260] ? process_one_work+0x3d0/0x3d0 [ 245.081493] kthread+0x127/0x150 [ 245.085592] ? set_kthread_struct+0x50/0x50 [ 245.090769] ret_from_fork+0x1f/0x30 [ 245.095266] ``` and ``` [ 245.530629] INFO: task ifenslave:849 blocked for more than 121 seconds. [ 245.540433] Not tainted 5.15.0-69-generic #76-Ubuntu [ 245.549050] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.558960] task:ifenslave state:D stack:0 pid: 849 ppid: 847 flags:0x4002 [ 245.570930] Call Trace: [ 245.576175] [ 245.581018] __schedule+0x24e/0x590 [ 245.587445] schedule+0x69/0x110 [ 245.593631] schedule_timeout+0x103/0x140 [ 245.600573] __wait_for_common+0xab/0x150 [ 245.607526] ? usleep_range_state+0x90/0x90 [ 245.614743] wait_for_completion+0x24/0x30 [ 245.621903] flush_workqueue+0x133/0x3e0 [ 245.628887] ib_cache_cleanup_one+0x21/0xf0 [ib_core] [ 245.637083] __ib_unregister_device+0x79/0xc0 [ib_core] [ 245.645398] ib_unregister_device+0x27/0x40 [ib_core] [ 245.653541] irdma_ib_unregister_device+0x4b/0x70 [irdma] [ 245.662105] irdma_remove+0x1f/0x70 [irdma] [ 245.669446] auxiliary_bus_remove+0x1d/0x40 [ 245.676688] __device_release_driver+0x1a8/0x2a0 [ 245.684241] device_release_driver+0x29/0x40 [ 245.691416] bus_remove_device+0xde/0x150 [ 245.698396] device_del+0x19c/0x400 [**712178] ice_lag_link.isra.0+0xdd/0xf0 [ice] m] (3 of 5) A start job is runni[ 245.720683] ice_lag_changeupper_event+0xe1/0x130 [ice] ng for\u2026rk interfaces (3min 47s[ 245.729739] ice_lag_event_handler+0x5b/0x150 [ice] / 5min 3s) [ 245.738525] raw_notifier_call_chain+0x46/0x60 [ 245.746006] call_netdevice_notifiers_info+0x52/0xa0 [ 245.754123] __netdev_upper_dev_link+0x1b7/0x310 [ 245.761658] netdev_master_upper_dev_link+0x3e/0x60 [ 245.769627] bond_enslave+0xc3a/0x1720 [bonding] [ 245.777398] ? sscanf+0x4e/0x70 [ 245.783375] bond_option_slaves_set+0xca/0x170 [bonding] [ 245.791738] __bond_opt_set+0xbd/0x1a0 [bonding] [ 245.799505] __bond_opt_set_notify+0x30/0xb0 [bonding] [ 245.807860] bond_opt_tryset_rtnl+0x56/0xa0 [bonding] [ 245.816062] bonding_sysfs_store_option+0x52/0xa0 [bonding] [ 245.824750] dev_attr_store+0x14/0x30 [ 245.831443] sysfs_kf_write+0x3b/0x50 [ 245.837979] kernfs_fop_write_iter+0x138/0x1c0 [ 245.845469] new_sync_write+0x111/0x1a0 [ 245.852210] vfs_write+0x1d5/0x270 [ 245.858429] ksys_write+0x67/0xf0 [ 245.864624] __x64_sys_write+0x19/0x20 [ 245.871288] do_syscall_64+0x59/0xc0 [ 245.877715] ? handle_mm_fault+0xd8/0x2c0 [ 245.884566] ? do_user_addr_fault+0x1e7/0x670 [ 245.891990] ? filp_close+0x60/0x70 [ 245.898452] ? exit_to_user_mode_prepare+0x37/0xb0 [ 245.906272] ? irqentry_exit_to_user_mode+0x9/0x20 [ 245.914042] ? irqentry_exit+0x1d/0x30 [ 245.920703] ? exc_page_fault+0x89/0x170 [ 245.927555] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 245.935763] RIP: 0033:0x7f1e86855a37 [ 245.942153] RSP: 002b:7fff8da477a8 EFLAGS: 0246 ORIG_RAX: 0001 [ 245.953034] RAX: ffda RBX: 000a RCX: 7f1e86855a37 [ 245.963554] RDX: 000a RSI: 556eff580510 RDI: 0001 [ 245.972468] RBP: 556eff580510 R08: 556eff582c5a R09: [ 245.983048] R10: 556eff582c59 R11: 0246 R12: 0001 [ 245.993402] R13: 000a R14: R15: [ 246.001700] ``` This appears consistent with the underlying cause being the bug fixed by mainline commit 248401cb2c4612d83eb0c352ee8103b78b8eb365 (commit 87b9ac7bd301f53b14fc8eddb1f4045e3f2c in the 5.15.y stable tree). The 5.15.0-67 kernel does not exhibit the problem; given that the 5.15.0-68 kernel apparently included the "RDMA/irdma: Report the correct link speed" patch listed in
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/5.19.0-1020.23)
All autopkgtests for the newly accepted linux-restricted-modules-oracle (5.19.0-1020.23) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) 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/kinetic/update_excuses.html#linux-restricted-modules-oracle [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 packaging 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 1887703] Canonical Certification.
*** This bug is a duplicate of bug 1893956 *** https://bugs.launchpad.net/bugs/1893956 H Valerie / Jeff, Are you still in certification submission review team ?. I have one system model ready to submit for the review. Somehow the used link does not work now . Would you please provide me the access link ?. Thank you, Ly, -- 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/1887703 Title: [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: [IMPACT] The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card but the kernel only sees the two SFP+ ports and cannot address or use the two copper ports. This is currently blocking certification for one of our hardware partners. After some investigation we see this works in a more recent version of the driver. Intel suggests the commit in FIXES from 5.5 should make this work. This is a regression from the i40e driver in Bionic (5.3 HWE) that, per the tester, does show all four ports. [FIXES] 3df5b9a6a9ec3c1e4431bf1db3426b54dc92dd91 i40e: enable X710 support I have a branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1887703-i40e-enable-x710 [TESTING] Boot system, verify four ports are visible and can be addressed and pass data. [IMPACT] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-gkeop/5.15.0-1018.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-gkeop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware
[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits
This bug is awaiting verification that the linux-gkeop/5.15.0-1018.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-gkeop -- 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/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-gcp source package in Lunar: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+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 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1018.18+1)
All autopkgtests for the newly accepted linux-restricted-modules-nvidia (5.15.0-1018.18+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) 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/jammy/update_excuses.html#linux-restricted-modules-nvidia [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 packaging 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 1786013] Autopkgtest regression report (linux-restricted-modules-gcp/5.19.0-1020.22)
All autopkgtests for the newly accepted linux-restricted-modules-gcp (5.19.0-1020.22) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) 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/kinetic/update_excuses.html#linux-restricted-modules-gcp [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 packaging 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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-oracle/5.19.0-1020.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware,
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Changed in: linux-oracle-5.15 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle-5.15 package in Ubuntu:
Fix Committed
Status in linux-oracle-5.15 source package in Focal:
Fix Released
Status in linux-oracle-5.15 source package in Jammy:
Fix Released
Bug description:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
On -1031 no interrupt is detected for both the alarm and update tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle-5.15/+bug/2011854/+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 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
Cuda testing passed for all drivers (470, 515, 525, 450-server,
470-server, 515-server, 525-server) on bionic, focal, jammy and kinetic
using both DKMS and LRM (when using the appropriate stream 2 ppa for the
LRM packages). DKMS testing also passed on lunar.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in fabric-manager-470 source package in Kinetic:
New
Status in fabric-manager-515 source package in Kinetic:
New
Status in fabric-manager-525 source package in Kinetic:
New
Status in libnvidia-nscq-450 source
[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic
** Tags added: kernel-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: New Bug description: losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+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 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic
** Also affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags added: jammy -- 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/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: New Bug description: losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+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 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: New Bug description: losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+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 2015400] [NEW] losetup with mknod fails on jammy with kernel 5.15.0-69-generic
Public bug reported: losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Package changed: nvidia-graphics-drivers-525 (Ubuntu) => ubuntu ** Package changed: ubuntu => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux ** Project changed: linux => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2015400 Title: losetup with mknod fails on jammy with kernel 5.15.0-69-generic Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: New Bug description: losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+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 2008823] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661371/+files/acpidump.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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661370/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio
[Kernel-packages] [Bug 2008823] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661369/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661368/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio
[Kernel-packages] [Bug 2008823] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661367/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name:
[Kernel-packages] [Bug 2008823] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661366/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 2008823] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661365/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio
[Kernel-packages] [Bug 2008823] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661364/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661363/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661362/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB
[Kernel-packages] [Bug 2008823] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2008823/+attachment/5661361/+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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-10-17 (1265 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: retsamarret To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: atomisp_lm3554 atomisp_gmin_platform Tags: jammy uec-images staging Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/21/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name:
[Kernel-packages] [Bug 2008823] Re: /sys/kernel/boot_params/data leaks random data
apport information ** Tags added: apport-collected staging ** Description changed: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-38-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2019-10-17 (1265 days ago) + InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 1221:3234 Unknown manufacturer Disk (Thumb drive) + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M + |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M + MachineType: retsamarret To be filled by O.E.M. + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro + ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-38-generic N/A + linux-backports-modules-5.19.0-38-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.12 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + StagingDrivers: atomisp_lm3554 atomisp_gmin_platform + Tags: jammy uec-images staging + Uname: Linux 5.19.0-38-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-08-13 (235 days ago) + UserGroups: adm cdrom dip lxd plugdev sudo + _MarkForUpload: True + dmi.bios.date: 04/21/2017 + dmi.bios.release: 5.6 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 5.6.5 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Aptio CRB + dmi.board.vendor: AMI Corporation + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias:
[Kernel-packages] [Bug 2015399] [NEW] Bionic update: upstream stable patchset 2023-04-05
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: upstream stable patchset 2023-04-05 Ported from the following upstream stable releases: v4.14.306, v4.19.273 v4.14.307, v4.19.274 v4.19.275 from git://git.kernel.org/ firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region bus: sunxi-rsb: Fix error handling in sunxi_rsb_init() ALSA: hda/via: Avoid potential array out-of-bound in add_secret_dac_path() netrom: Fix use-after-free caused by accept on already connected socket squashfs: harden sanity check in squashfs_read_xattr_id_table sctp: do not check hb_timer.expires when resetting hb_timer net: openvswitch: fix flow memory leak in ovs_flow_cmd_new scsi: target: core: Fix warning on RT kernels scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress net/x25: Fix to not accept on connected socket usb: gadget: f_fs: Fix unbalanced spinlock in __ffs_ep0_queue_wait fbcon: Check font dimension limits watchdog: diag288_wdt: do not use stack buffers for hardware data watchdog: diag288_wdt: fix __diag288() inline assembly efi: Accept version 2 of memory attributes table iio: hid: fix the retval in accel_3d_capture_sample iio: adc: berlin2-adc: Add missing of_node_put() in error path iio:adc:twl6030: Enable measurements of VUSB, VBAT and others parisc: Fix return code of pdc_iodc_print() parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps mm/swapfile: add cond_resched() in get_swap_pages() Squashfs: fix handling and sanity checking of xattr_ids count serial: 8250_dma: Fix DMA Rx completion race serial: 8250_dma: Fix DMA Rx rearm race btrfs: limit device extents to the device size ALSA: emux: Avoid potential array out-of-bound in snd_emux_xg_control() ALSA: pci: lx6464es: fix a debug loop pinctrl: aspeed: Fix confusing types in return value pinctrl: single: fix potential NULL dereference net: USB: Fix wrong-direction WARNING in plusb.c usb: core: add quirk for Alcor Link AK9563 smartcard reader migrate: hugetlb: check for hugetlb shared PMD in node migration tools/virtio: fix the vringh test for virtio ring changes net/rose: Fix to not accept on connected socket nvme-fc: fix a missing queue put in nvmet_fc_ls_create_association aio: fix mremap after fork null-deref mmc: sdio: fix possible resource leaks in some error paths ALSA: hda/conexant: add a new hda codec SN6180 hugetlb: check for undefined shift on 32 bit architectures revert "squashfs: harden sanity check in squashfs_read_xattr_id_table" i40e: add double of VLAN header when computing the max MTU net: bgmac: fix BCM5358 support by setting correct flags dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions. net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path net: stmmac: Restrict warning on disabling DMA store and fwd mode ipv6: Fix datagram socket connection with DSCP. ipv6: Fix tcp socket connection with DSCP. i40e: Add checking for null for nlmsg_find_attr() kvm: initialize all of the kvm_debugregs structure before sending it to userspace nilfs2: fix underflow in second superblock position calculations ata: libata: Fix sata_down_spd_limit() when no link speed is reported vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF thermal: intel: int340x: Protect trip temperature from concurrent updates iio:adc:twl6030: Enable measurement of VAC IB/hfi1: Restore allocated resources on failed copyout net: phy: meson-gxl: use MMD access dummy stubs for GXL, internal PHY riscv: Fixup race condition on PG_dcache_clean in flush_icache_pte arm64: dts: meson-gx: Make mmc host controller interrupts level-sensitive UBUNTU: Upstream stable to v4.14.306, v4.19.273 wifi: rtl8xxxu: gen2: Turn on the rate control powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G random: always mix cycle counter in add_latent_entropy() powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 alarmtimer: Prevent starvation by small intervals and SIG_IGN uaccess: Add speculation barrier to copy_from_user() wifi: mwifiex: Add missing compatible string for SD8787 bpf: add missing header file include vc_screen: don't clobber return value in vcs_read dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size UBUNTU: Upstream stable to v4.14.307, v4.19.275 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee:
[Kernel-packages] [Bug 2015400] [NEW] losetup with mknod fails on jammy with kernel 5.15.0-69-generic
You have been subscribed to a public bug: losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup with mknod fails on jammy with kernel 5.15.0-69-generic https://bugs.launchpad.net/bugs/2015400 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2015400] [NEW] losetup with mknod fails on jammy with kernel 5.15.0-69-generic
You have been subscribed to a public bug: losetup fails with devices created manually by mknod on kernel 5.15.0-69-generic # fallocate -l 1G test # mknod -m 660 /dev/loop8 b 7 8 # chown root:disk /dev/loop8 # losetup /dev/loop8 ./test losetup: ./test: failed to set up loop device: Device or resource busy Possibly as a result of this patch: https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/ which was introduced in 5.15.0-68: http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz On a machine prior to this change (no issue with losetup): # cat /sys/module/loop/parameters/max_loop 0 # uname -r 5.15.0-58-generic On a machine after the change (has losetup issue as described above): # cat /sys/module/loop/parameters/max_loop 8 # uname -r 5.15.0-69-generic So it looks like the default changed and the max amount of loop devices that can be created with mknod (not loop-control) is 8. If we set max_loop=0 on the kernel command line, it works as before. Cannot unload and reload module on a running system to change the parameter because it is built into the kernel. Another workaround is to use `losetup --find` but that means you cannot create with named devices created with mknod. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup with mknod fails on jammy with kernel 5.15.0-69-generic https://bugs.launchpad.net/bugs/2015400 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2013236] Re: Failed to install bcmwl wireless driver during the install
I tested this same scenario on Ubuntu 22.04.2 and while I still don't have a wireless device available I did discover the following: bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers list bcmwl-kernel-source bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers devices == /sys/devices/pci:00/:00:02.4/:05:00.0 == modalias : pci:v14E4d43B1sv1043sd85BAbc02sc80i00 vendor : Broadcom Inc. and subsidiaries model: BCM4352 802.11ac Wireless Network Adapter driver : bcmwl-kernel-source - distro non-free bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu10~22.04.1 Candidate: 6.30.223.271+bdcom-0ubuntu10~22.04.1 Version table: *** 6.30.223.271+bdcom-0ubuntu10~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 6.30.223.271+bdcom-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2015397] [NEW] Very slow boot using hybrid setup
Public bug reported: Hi, Lunar, 525.105.17 I get a very very very slow boot using dynamic graphics in my Lenovo Legion 5i pro i7/3070 Ti. Using discrete graphics is ok. Using Nouveau with hybrid graphics is ok. After some research, it seems the culprit is: Failed to start systemd-backlight@backlight:nvidia_0.service - Load/Save Screen Backlight Brightness of backlight:nvidia_0. systemd blame: 1min 34.046s plymouth-quit-wait.service 1min 30.278s gpu-manager.service ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2015397 Title: Very slow boot using hybrid setup Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: Hi, Lunar, 525.105.17 I get a very very very slow boot using dynamic graphics in my Lenovo Legion 5i pro i7/3070 Ti. Using discrete graphics is ok. Using Nouveau with hybrid graphics is ok. After some research, it seems the culprit is: Failed to start systemd-backlight@backlight:nvidia_0.service - Load/Save Screen Backlight Brightness of backlight:nvidia_0. systemd blame: 1min 34.046s plymouth-quit-wait.service 1min 30.278s gpu-manager.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2015397/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-raspi/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-raspi verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1:
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-raspi/5.4.0-1083.94 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
I tried installing using the desktop legacy image and noticed that `ubuntu-drivers` behaves the same way - recommending broadcom-sta-dkms but then not installing it. Additionally, looking at the device I see the following (which I also recall from the new installer): 05:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: ASUSTeK Computer Inc. BCM4352 802.11ac Wireless Network Adapter [1043:85ba] Physical Slot: 0-5 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bcma-pci-bridge Kernel modules: bcma While the bcma module might be in use I have not wireless devices setup. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2008823] 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 2008823 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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: Incomplete Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008823/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
After installing with the new desktop installer, rebooting, manually installing broadcom-sta-dkms, and rebooting again no wireless adapter was available. Additionally, running 'ubuntu-drivers install' (before installing broadcom-sta-dkms) indicated that all drivers were already installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2008823] Re: /sys/kernel/boot_params/data leaks random data
** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux (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/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: New Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008823/+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 2008823] Re: /sys/kernel/boot_params/data leaks random data
Oh yes, an ec2 instance I have that has non-zero content at the end of the file: Linux ip-172-26-15-115 4.4.0-1154-aws #169-Ubuntu SMP Fri Feb 17 11:05:27 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008823 Title: /sys/kernel/boot_params/data leaks random data Status in linux package in Ubuntu: New Bug description: Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte buffer is old kernel data. It really stood out as I saw parts of email contents in there. It seems be random RAM contents from what was present before rebooting. This was seen on Ubuntu 22.04.2 LTS with kernel 5.19.0-32-generic. After rebooting again I saw a fragment of yet another email in there. A couple of ubuntu 22.10 systems show similar non-zero data, but nothing as recognizable. Nothing after the entries at the front of e820_table was zeroed out as it should be. This could leak a substantial amount of data such as encryption keys. /sys/kernel/boot_params/data is readable by all users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Feb 28 13:24:06 2023 InstallationDate: Installed on 2019-10-17 (1229 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-08-13 (199 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008823/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-kvm/4.15.0-1138.143 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-kvm verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1:
[Kernel-packages] [Bug 2015369] Re: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Kinetic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
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/2015369
Title:
Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-azure source package in Jammy:
In Progress
Status in linux-azure source package in Kinetic:
In Progress
Status in linux-azure source package in Lunar:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
88e378d400fa0544d51cf62037e7774d8a4b4379 ('x86/ioremap: Add hypervisor
callback for private MMIO mapping in coco VM') from linux-next.
[Regression Potential]
Private memory mappings could be incorrect.
[Test Plan]
Microsoft tested.
[Other Info]
SF: #00355859
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2015369/+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 2015369] Re: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
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/2015369
Title:
Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-azure source package in Jammy:
New
Status in linux-azure source package in Kinetic:
New
Status in linux-azure source package in Lunar:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
88e378d400fa0544d51cf62037e7774d8a4b4379 ('x86/ioremap: Add hypervisor
callback for private MMIO mapping in coco VM') from linux-next.
[Regression Potential]
Private memory mappings could be incorrect.
[Test Plan]
Microsoft tested.
[Other Info]
SF: #00355859
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2015369/+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 2015372] [NEW] Add support for intel EMR cpu
Public bug reported: TODO current status in lunar and mainline. The following commits had to be backported to Jammy: Usually backporting new features to existing kernels it's not a common practice. But these backports were easy to pick. Some of the commits were already applied. More information about backporting these commits is addressed inline. 1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d Already applied to jammy. Picked up in v5.15.80 upstream stable release https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122 2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036 Had to adjust the path to uncore-frequency.c In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to uncore-frequency dir 3. PMU Update to Support New EMR CPU model Number: 3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467 3.2 5a8a05f165fb18d37526062419774d9088c2a9b9 Small adjustment needed because saphire, raptor changes were not there. 3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 upstream https://bugs.launchpad.net/bugs/2012665 3.4 69ced4160969025821f2999ff92163ed26568f1c already applied in 5.15.91 https://bugs.launchpad.net/bugs/2011467 4. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0 Manually solved small conflict due to missing 80275ca9e525c where a fixed DRAM domain energy unit is introduced 5. linux kernel: add EMR support to the intel_idle driver: 74528edfbc664f9d2c927c4e5a44f1285598ed0f clean cherry-pick 6. intel-speed-select tool support for EMR: 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5 clean cherry-pick 7. Turbostat support on EMR: 93cac4150727dae0ee89f501dd75413b88eedec0 clean cherry-pick 8. intel-RAPL drivers to support new EMR CPU model number: 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb clean cherry-pick 9. Provide accel-config for EMR : TODO userspace - this is user-space code, not kernel code (accel-config seems the package that we already have in lunar, sync'ed from Debian, not sure if we need to provide additional changes applied or if we need to backport the whole user-space package to jammy) 10. Enable in-field Array BIST for EMR code is still in the process of being reviewed, we shouldn't apply/backport this for now 11. CXL 1.1 Compatibility ECN Very big patch -- won't port it to jammy 12. Split Lock detection change for EMR: d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 TODO linux-next only 13. Add Emerald Rapids CPU model number ID for EDAC driver support: e4b2bc6616e21 clean cherry-pick Testing: Kernel was built on cbd. roxanan-jammy-63b23a4757ba-H6S4 TODO qemu Regression potential Very very low, these are new features, nothing to regress here. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Roxana Nicolescu (roxanan) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux (Ubuntu) Status: New => In Progress -- 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/2015372 Title: Add support for intel EMR cpu Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: New Bug description: TODO current status in lunar and mainline. The following commits had to be backported to Jammy: Usually backporting new features to existing kernels it's not a common practice. But these backports were easy to pick. Some of the commits were already applied. More information about backporting these commits is addressed inline. 1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d Already applied to jammy. Picked up in v5.15.80 upstream stable release https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122 2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036 Had to adjust the path to uncore-frequency.c In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to uncore-frequency dir 3. PMU Update to Support New EMR CPU model Number: 3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467 3.2 5a8a05f165fb18d37526062419774d9088c2a9b9 Small adjustment needed because saphire, raptor changes were not there. 3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 upstream https://bugs.launchpad.net/bugs/2012665 3.4 69ced4160969025821f2999ff92163ed26568f1c already
[Kernel-packages] [Bug 2008217] Re: Unsolicited wake from suspend with bluetooth connected (Intel AX211/AX201)
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2008217 Title: Unsolicited wake from suspend with bluetooth connected (Intel AX211/AX201) Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: [Summary] The system will auto wake from suspend with bluetooth connected. Note: 1. BT headset, BT Keyboard and BT mouse all can duplicate 2. RTL 8852BE & Intel AX201 cannot duplicate [Steps to reproduce] 1. Install dell-bto-jammy-jellyfish-quilladin-X72-20230216-17.iso 2. Boot to OS 3. Pair the bluetooth headset device. 4. Enter suspend. [Expected result] The system will not auto wake when the bluetooth device is connected. [Actual result] The system will auto wake from suspend with bluetooth connected. [Failure rate] 3/10 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008217/+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 1998883] Re: Micron NVME storage failure [1344, 5407]
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+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 2015369] [NEW] Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
Public bug reported:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
88e378d400fa0544d51cf62037e7774d8a4b4379 ('x86/ioremap: Add hypervisor
callback for private MMIO mapping in coco VM') from linux-next.
[Regression Potential]
Private memory mappings could be incorrect.
[Test Plan]
Microsoft tested.
[Other Info]
SF: #00355859
** Affects: linux-azure (Ubuntu)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-azure (Ubuntu Lunar)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
** Also affects: linux-azure (Ubuntu Lunar)
Importance: Undecided
Status: Fix Released
** Changed in: linux-azure (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Lunar)
Status: Fix Released => In Progress
** Changed in: linux-azure (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/2015369
Title:
Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-azure source package in Lunar:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
88e378d400fa0544d51cf62037e7774d8a4b4379 ('x86/ioremap: Add hypervisor
callback for private MMIO mapping in coco VM') from linux-next.
[Regression Potential]
Private memory mappings could be incorrect.
[Test Plan]
Microsoft tested.
[Other Info]
SF: #00355859
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2015369/+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 2013236] Re: Failed to install bcmwl wireless driver during the install
are you sure the dkms module is still needed with the v6.2 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2015279] Re: ftbfs during kernel build due to dkms changes in lunar
This bug was fixed in the package v4l2loopback - 0.12.7-2ubuntu3 --- v4l2loopback (0.12.7-2ubuntu3) lunar; urgency=medium * Revert to 0.12.7-2ubuntu1, as dkms that unconditionaly exports CC has been reverted. Otherwise, currently src:linux FTBFS when trying to vendor in this module. LP: #2015279 -- Dimitri John Ledkov Tue, 04 Apr 2023 17:41:18 +0100 ** Changed in: v4l2loopback (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015279 Title: ftbfs during kernel build due to dkms changes in lunar Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Fix Released Bug description: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS -- dkms in jammy and lunar are incompatible with each other, prevent kernel from using dkms during its buildtime to prebuild certain dkms modules. Workaround it by including a fixed copy of dkms script in the kernel, as used at build-time only to produce certain pre-built modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015279/+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 2015361] 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 2015361 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/2015361 Title: FTBFS with different dkms or when makeflags are set Status in linux package in Ubuntu: Incomplete Bug description: build_dkms fails 1) if updated dkms is used that changes return code for skip from 9 to 77 2) if MAKEFLAGS are exported that remove implicit variables, which dkms module submake invocations may require fix those things for lunar release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015361/+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 2015361] [NEW] FTBFS with different dkms or when makeflags are set
Public bug reported: build_dkms fails 1) if updated dkms is used that changes return code for skip from 9 to 77 2) if MAKEFLAGS are exported that remove implicit variables, which dkms module submake invocations may require fix those things for lunar release. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.04 -- 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/2015361 Title: FTBFS with different dkms or when makeflags are set Status in linux package in Ubuntu: New Bug description: build_dkms fails 1) if updated dkms is used that changes return code for skip from 9 to 77 2) if MAKEFLAGS are exported that remove implicit variables, which dkms module submake invocations may require fix those things for lunar release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015361/+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 2015279] Re: ftbfs during kernel build due to dkms changes in lunar
** Tags removed: block-proposed-lunar ** Changed in: v4l2loopback (Ubuntu) Status: New => Fix Committed -- 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/2015279 Title: ftbfs during kernel build due to dkms changes in lunar Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Fix Committed Bug description: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS -- dkms in jammy and lunar are incompatible with each other, prevent kernel from using dkms during its buildtime to prebuild certain dkms modules. Workaround it by including a fixed copy of dkms script in the kernel, as used at build-time only to produce certain pre-built modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015279/+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 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+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 2015352] 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 2015352 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/2015352 Title: System hangs during boot, When the Intel E810 NIC driver is used to create bonding. Status in linux package in Ubuntu: Incomplete Bug description: Description: On a Dell EMC PE system configured with Intel E810 card installed with Ubuntu 22.04.2. When bonding is enabled on the server, the system will hang at the initialization of OS. The kernel loads, but the system hang around the time it starts the Network Services by reporting below messages. echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message. INFO: task systemd-network:1769 blocked for more than 120 seconds not tained 5.15.0-69-generic #76-ubuntu Steps to reproduce: 1. Configure Dell EMC PE system with Intel E-810 NIC. 2. Install Ubuntu 22.04.2 and boot into OS. 3. Create a bonding interface by editing netplan configuration file as below. bonds: bond0: dhcp4: true interfaces: [enp209s0f0, enp209s0f1] parameters: mode: active-backup Where [enp209s0f0, enp209s0f1] are Intel E-810 Interfaces. 4. Execute #Netplan apply and reboot the system. 5. Observe system hangs at starting Network Services. Actual Results: System hang is observed. Expected results: No system hang should be Observe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015352/+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 1523565] Re: Qualcomm atheros network controller [168c:0042] (rev 30) does not work
** No longer affects: linux (Ubuntu) ** Changed in: linux-firmware (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1523565 Title: Qualcomm atheros network controller [168c:0042] (rev 30) does not work Status in linux-firmware package in Ubuntu: Fix Released Bug description: I installed the latest ath10k driver, which changed the status of the hardware from unclaimed to claimed, but it still does not seem to be recognized as a wireless device. WORKAROUND: Install from upstream both the latest ath10k driver: https://github.com/kvalo/ath/tree/master/drivers/net/wireless/ath/ath10k and ath10k firmware: https://github.com/kvalo/ath10k-firmware ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: (removed for privacy) 1358 F pulseaudio /dev/snd/controlC0: (removed for privacy) 1358 F pulseaudio CurrentDesktop: Unity Date: Mon Dec 7 21:22:43 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec603e54-8e2b-40c2-9bd4-559d5e329d2c InstallationDate: Installed on 2015-12-07 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd05/27/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1523565/+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 2015352] [NEW] System hangs during boot, When the Intel E810 NIC driver is used to create bonding.
Public bug reported: Description: On a Dell EMC PE system configured with Intel E810 card installed with Ubuntu 22.04.2. When bonding is enabled on the server, the system will hang at the initialization of OS. The kernel loads, but the system hang around the time it starts the Network Services by reporting below messages. echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message. INFO: task systemd-network:1769 blocked for more than 120 seconds not tained 5.15.0-69-generic #76-ubuntu Steps to reproduce: 1. Configure Dell EMC PE system with Intel E-810 NIC. 2. Install Ubuntu 22.04.2 and boot into OS. 3. Create a bonding interface by editing netplan configuration file as below. bonds: bond0: dhcp4: true interfaces: [enp209s0f0, enp209s0f1] parameters: mode: active-backup Where [enp209s0f0, enp209s0f1] are Intel E-810 Interfaces. 4. Execute #Netplan apply and reboot the system. 5. Observe system hangs at starting Network Services. Actual Results: System hang is observed. Expected results: No system hang should be Observe. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screen shot shows system hang during boot" https://bugs.launchpad.net/bugs/2015352/+attachment/5661192/+files/image-2023-04-04-15-41-41-614.png -- 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/2015352 Title: System hangs during boot, When the Intel E810 NIC driver is used to create bonding. Status in linux package in Ubuntu: New Bug description: Description: On a Dell EMC PE system configured with Intel E810 card installed with Ubuntu 22.04.2. When bonding is enabled on the server, the system will hang at the initialization of OS. The kernel loads, but the system hang around the time it starts the Network Services by reporting below messages. echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message. INFO: task systemd-network:1769 blocked for more than 120 seconds not tained 5.15.0-69-generic #76-ubuntu Steps to reproduce: 1. Configure Dell EMC PE system with Intel E-810 NIC. 2. Install Ubuntu 22.04.2 and boot into OS. 3. Create a bonding interface by editing netplan configuration file as below. bonds: bond0: dhcp4: true interfaces: [enp209s0f0, enp209s0f1] parameters: mode: active-backup Where [enp209s0f0, enp209s0f1] are Intel E-810 Interfaces. 4. Execute #Netplan apply and reboot the system. 5. Observe system hangs at starting Network Services. Actual Results: System hang is observed. Expected results: No system hang should be Observe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015352/+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 1988989] Re: HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen.
Oh man. This turned out to be a hardware issue. A replacement adapter works fine. I'd never have thought, when the kernel changed so much. I'm on 5.19 now, didn't see a glitch yet, where I'd normally couldn't work. Phew. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1988989 Title: HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen. Status in linux package in Ubuntu: Invalid Bug description: Having upgraded to 5.19.0-15, my display connected over a USB-C → HDMI connection goes off and on multiple times a minute, rendering it unusable. Downgrading back to 5.15.0-27 makes it work again. I've bisected mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/ to reach: v5.18.19 GOOD v5.19-rc3 BAD ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 7948 F wireplumber /dev/snd/controlC0: michal 7948 F wireplumber /dev/snd/seq:michal 7939 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 14:28:48 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-08-31 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: Framework Laptop (12th Gen Intel Core) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zw6n2j@/vmlinuz-5.19.0-15-generic root=ZFS=rpool/ROOT/ubuntu_zw6n2j 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA42321000N dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988989/+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 2015223] Re: linux-firmware logs kernel
broken pipe error 32 linux firmware and linux kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015223 Title: linux-firmware logs kernel Status in linux-firmware package in Ubuntu: Incomplete Bug description: linux firmware logs asus computer inc laptop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alvar 1686 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:20:05 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2023-03-13 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. E402SA PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=45b0810a-3f7a-47d9-9368-7204c1732d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015223/+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 2015293] Re: netfilter: ctnetlink: Support offloaded conntrack entry deletion
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New -- 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/2015293 Title: netfilter: ctnetlink: Support offloaded conntrack entry deletion Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: New Bug description: * Explain the bug(s) conntrack -D or conntrack -F doesn't delete offloaded tuples. * brief explanation of fixes Add support for to delete offloaded tuples via netlink interface and userspace conntrack utility. * 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 UDP connection, e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -u -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i See tuples were offloaded: ipv4 2 udp 17 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 Flush the tuples: conntrack -F Verify tuples are deleted: cat /proc/net/nf_conntrack | grep -i Before fix, the above tuple shows again, after fix, it's deleted, and shows nothing. * What it could break. Conntrack -F / -D not working on offloaded tuples. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015293/+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 2015307] Re: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2015307 Title: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: New Bug description: SRU Justification: [Impact] This change is needed to avoid unnecessary eMMC GPIO toggling when eMMC is idle [Fix] The fix implements the runtime PM operations for BlueField-3 SoC to disable the card clock when idle. [Test Case] Same functionality and testing as on BlueField-1/2. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015307/+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 2015139] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bi
** Tags added: kern-6380 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015139 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado Status in linux-firmware package in Ubuntu: New Bug description: Its block everything i can not use ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.10 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonny 4894 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 3 19:35:21 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DpkgHistoryLog: Start-Date: 2023-04-03 19:34:56 Commandline: aptdaemon role='role-commit-packages' sender=':1.187' Upgrade: linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.10, 20220329.git681281e4-0ubuntu3.11) ErrorMessage: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2023-03-05 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. ens33 no wireless extensions. MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=118d92a8-1f56-4180-8fc6-b52a55e9d30e ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015139/+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 2015139] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bi
** Tags added: kern-6379 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015139 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado Status in linux-firmware package in Ubuntu: New Bug description: Its block everything i can not use ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.10 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonny 4894 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 3 19:35:21 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DpkgHistoryLog: Start-Date: 2023-04-03 19:34:56 Commandline: aptdaemon role='role-commit-packages' sender=':1.187' Upgrade: linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.10, 20220329.git681281e4-0ubuntu3.11) ErrorMessage: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2023-03-05 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. ens33 no wireless extensions. MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=118d92a8-1f56-4180-8fc6-b52a55e9d30e ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015139/+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 2015139] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bi
dpkg-deb (sub-processo): ZSTD_decompressStream error : Corrupted block detected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015139 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado Status in linux-firmware package in Ubuntu: New Bug description: Its block everything i can not use ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.10 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonny 4894 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 3 19:35:21 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DpkgHistoryLog: Start-Date: 2023-04-03 19:34:56 Commandline: aptdaemon role='role-commit-packages' sender=':1.187' Upgrade: linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.10, 20220329.git681281e4-0ubuntu3.11) ErrorMessage: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2023-03-05 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. ens33 no wireless extensions. MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=118d92a8-1f56-4180-8fc6-b52a55e9d30e ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015139/+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 2015308] 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 2015308 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/2015308 Title: Amd Radeon Navi RX 6600m poor performance Status in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I can't open steam because it crashes and there are strange artifacts on the screen, the performance overall is really bad (for example Age of empires 2 works bad on 1080p and low settings). I've noticed an error message on the terminal that says possibly missing firmware each time I update grub. Currently using 23.04, no PPA's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015308/+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 2015333] [NEW] [UBUNTU 23.04] Fix for the IBMCA provider
Public bug reported: Details will be provided later via comments. ==> Please mark this LP entry as "private" ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-202168 severity-high targetmilestone-inin2304 ** Tags added: architecture-s39064 bugnameltc-202168 severity-high targetmilestone-inin2304 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (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/2015333 Title: [UBUNTU 23.04] Fix for the IBMCA provider Status in linux package in Ubuntu: New Bug description: Details will be provided later via comments. ==> Please mark this LP entry as "private" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015333/+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 2015333] [NEW] [UBUNTU 23.04] Fix for the IBMCA provider
You have been subscribed to a public bug: Details will be provided later via comments. ==> Please mark this LP entry as "private" ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-202168 severity-high targetmilestone-inin2304 -- [UBUNTU 23.04] Fix for the IBMCA provider https://bugs.launchpad.net/bugs/2015333 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2015223] Re: linux-firmware logs kernel
That bug description is not very helpful. Please explain what you think is your problem and why you think it's firmware related. ** Tags added: kern-6371 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015223 Title: linux-firmware logs kernel Status in linux-firmware package in Ubuntu: Incomplete Bug description: linux firmware logs asus computer inc laptop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alvar 1686 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:20:05 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2023-03-13 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. E402SA PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=45b0810a-3f7a-47d9-9368-7204c1732d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015223/+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 2015233] Re: linux-firmware MS 7817
That bug description is not very helpful. Please explain what you think is your problem and why you think it's firmware related. ** Tags added: kern-6372 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015233 Title: linux-firmware MS 7817 Status in linux-firmware package in Ubuntu: Incomplete Bug description: linux-firmware MS 7817 linux kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1619 F pulseaudio /dev/snd/controlC0: alvar 1619 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 15:43:16 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: MSI MS-7817 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015233/+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 2015297] Re: Update GPU F/W for DCN 3.1.4 products to fix S0i3 issue
** Tags added: kern-6373 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015297 Title: Update GPU F/W for DCN 3.1.4 products to fix S0i3 issue Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Kinetic: New Status in linux-firmware source package in Lunar: New Bug description: [ Impact ] The current GPU firmware in place for DCN 3.1.4 based products fails to resume from s2idle on newer BIOSes. The following GPU F/W stack is confirmed to fix the problem and works both with the older BIOSes and newer BIOSes: 9ee24ce0 amdgpu: Update SDMA 6.0.1 firmware 7df2a1ae amdgpu: Add PSP 13.0.11 firmware f098803d amdgpu: Update PSP 13.0.4 firmware 2cc9a4d0 amdgpu: Update GC 11.0.1 firmware eb13e669 amdgpu: Update DCN 3.1.4 firmware 898b7def amdgpu: Add GC 11.0.4 firmware Those binaries are part of upstream linux-firmware tag 20230404. [ Test Plan ] * Run s2idle cycle using OEM-6.1 1008 or 1009 kernel on a DCN 3.1.4 platform * Verify that display comes back [ Where problems could occur ] * This GPU F/W is only used for DCN 3.1.4 based products. These aren't yet on the market and there is no risk to regression to any Ubuntu users. * Without this firmware update OEM systems running newer BIOS won't be able to be certified. [ Other Info ] * AMD has found this regression and validated this stack on reference hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015297/+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 2015308] Re: Amd Radeon Navi RX 6600m poor performance
** Also 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/2015308 Title: Amd Radeon Navi RX 6600m poor performance Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I can't open steam because it crashes and there are strange artifacts on the screen, the performance overall is really bad (for example Age of empires 2 works bad on 1080p and low settings). I've noticed an error message on the terminal that says possibly missing firmware each time I update grub. Currently using 23.04, no PPA's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015308/+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 2015279] 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 2015279 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/2015279 Title: ftbfs during kernel build due to dkms changes in lunar Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: New Bug description: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS -- dkms in jammy and lunar are incompatible with each other, prevent kernel from using dkms during its buildtime to prebuild certain dkms modules. Workaround it by including a fixed copy of dkms script in the kernel, as used at build-time only to produce certain pre-built modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015279/+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 2015279] Re: ftbfs during kernel build due to dkms changes in lunar
** Description changed: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS + + + -- + + dkms in jammy and lunar are incompatible with each other, prevent kernel + from using dkms during its buildtime to prebuild certain dkms modules. + Workaround it by including a fixed copy of dkms script in the kernel, as + used at build-time only to produce certain pre-built modules. ** Also 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/2015279 Title: ftbfs during kernel build due to dkms changes in lunar Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: New Bug description: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS -- dkms in jammy and lunar are incompatible with each other, prevent kernel from using dkms during its buildtime to prebuild certain dkms modules. Workaround it by including a fixed copy of dkms script in the kernel, as used at build-time only to produce certain pre-built modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015279/+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 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in lttng-modules source package in Bionic: Fix Released Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Released Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: Fix Released Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: Fix Released Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ 782 21:14:39 DEBUG| [stdout] | ^~~ 783 21:14:39 DEBUG| [stdout]
[Kernel-packages] [Bug 2009436] Re: dkms modules are not built anymore for linux-kvm
** Changed in: autopkgtest (Ubuntu Jammy)
Status: New => Invalid
** Changed in: autopkgtest (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-kvm (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-kvm (Ubuntu Kinetic)
Status: New => Invalid
--
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/2009436
Title:
dkms modules are not built anymore for linux-kvm
Status in autopkgtest package in Ubuntu:
Invalid
Status in dkms package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
Invalid
Status in autopkgtest source package in Jammy:
Invalid
Status in dkms source package in Jammy:
New
Status in linux-kvm source package in Jammy:
Invalid
Status in autopkgtest source package in Kinetic:
Invalid
Status in dkms source package in Kinetic:
New
Status in linux-kvm source package in Kinetic:
Invalid
Bug description:
SRU Justification
[Impact]
Some dkms modules are not built anymore when a retry is triggred from adt
matrix page.
It was noticed because these modules previously failed during build (because
a config options is disabled) but now they pass (artificial pass).
Affected modules:
1. digimend-dkms
2. oss4
3. rtl8812au
4. rtl8812ce
Looking at digimend-dkms for jammy:linux-kvm, first time the test was correct
(it failed) was when the new kernel was just pushed to proposed and adt testing
was triggered. When a manual retry was done, it passed because build was
ignored.
Looking at the artifacts (attached for both cases), ADT_TEST_TRIGGERS differs:
1. when build is triggered, ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26
linux-kvm/5.15.0-1030.35 linux-signed-kvm/5.15.0-1030.35
logs
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230213_171044_032fa@/log.gz
2. when build is not triggered,
ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26
logs:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230301_110606_17e6d@/log.gz
Last log line present in both cases is:
"I: Testing binary package $pkg".
Looking at dkms: debian/scripts/dkms-autopkgtest
After that line and the line where build is triggered the following code:
dkms_pkg=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_NAME"
2>/dev/null)
dkms_ver=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_VERSION"
2>/dev/null)
for k in /lib/modules/*/build
do
test -d "$k" || continue
kver="${k%/build}"
kver="${kver#/lib/modules/}"
# If any linux-meta is in triggers, only test abistems that
# match triggers otherwise continue. This helps integration
# with adt-matrix which specifically requests test results
# against each individual linux-meta and tracks unique results
# per kernel abi.
abistem=$(echo $kver | sed 's/-[a-z]*$//')
## abistem is 5.15.0-130
case "${ADT_TEST_TRIGGERS-}" in
*linux-meta*)
case "$ADT_TEST_TRIGGERS" in
*"$abistem"*)
;;
*)
continue
;;
esac
esac
echo "I: Trying to build $dkms_pkg/$dkms_ver for $kver"
What happens here is that it never gets passed the switch case and
build is not triggered when ADT_TEST_TRIGGERS consists of linux-meta
only, because abistem=-, but meta
version=.. Notice the dot instead of the
dash.
This justifies why the module is built when ADT_TEST_TRIGGERS=linux-
meta-kvm/5.15.0.1030.26 linux-kvm/5.15.0-1030.35 linux-signed-
kvm/5.15.0-1030.35, but not when ADT_TEST_TRIGGERS=linux-meta-
kvm/5.15.0.1030.26
[Fix]
Add an extra check for meta_version in that switch case statement.
[Testcase]
1. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. before fix
I: linux-headers-virtual
I: Testing binary package digimend-dkms
autopkgtest [11:14:45]: test dkms-autopkgtest: ---]
autopkgtest [11:14:46]: test dkms-autopkgtest: - - - - - - - - - - results -
- - - - - - - - -
dkms-autopkgtest PASS
autopkgtest [11:14:47]: summary
dkms-autopkgtest PASS
qemu-system-x86_64: terminating on signal 15 from pid 15111 (/usr/bin/python3)
2. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. with the fix
I: Testing binary package digimend-dkms
I: Trying to build digimend/10 for 5.15.0-1029-kvm
Creating symlink /var/lib/dkms/digimend/10/source -> /usr/src/digimend-10
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j1 KERNELRELEASE=5.15.0-1029-kvm KVERSION=5.15.0-1029-kvm...(bad exit
status: 2)
ERROR (dkms apport): kernel package linux-headers-5.15.0-1029-kvm
[Kernel-packages] [Bug 1989470] Re: BGP adjacency not established on linux-image-5.15.0-1019-aws
new kernel 5.19.0-1023-aws fixed the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1989470 Title: BGP adjacency not established on linux-image-5.15.0-1019-aws Status in linux-aws package in Ubuntu: New Bug description: We have a simple eBGP setup with a peer over IPsec using a VTI interface using frr (default BGP daemon in Ubuntu 22.04). Everything worked fine until we upgraded to the latest kernel available for our machine: linux-image-5.15.0-1019-aws. After that the adjacency would simply not come up. I have investigated for some time, and found no issues with the configuration (obviously, it was not modified since it was working fine) and also no other issues. There are no firewall rules on this machine. Also there is no issue with the IPsec and the VTI interface, traffic flows through it, the BGP neighbor is pingable etc. We have confirmed that downgrading to linux-image-5.15.0-1017-aws fixes the issue. According to tcpdump it seems like both ends initiate the connection, but then there are just a lot of TCP retransmissions and Duplicate ACKs after the OPEN messages. The other side sends a KEEPALIVE but FRR seems to be stuck getting it. Basically it looks like according to the tcpdump that after the initial exchange of messages the ACKs are not recognized properly by the kernel (?) and therefore continous retransmissions occur until the timer of BGP expires. Since other TCP applications (e.g. SSH) work fine I'm assuming this might be related to: - VTI interfaces - FRR itself To drive initiatives in parallel I have opened a bug at FRR as well: https://github.com/FRRouting/frr/issues/11943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1989470/+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 1999882] Re: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part
This bug is not related to bluefield, hence setting focal verification again to done, to unblock. -- 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/1999882 Title: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Description: KVM: s390: pv: don't allow userspace to set the clock under PV Symptom: Timer issues and RCU stalls after suspending and resuming an IBM Secure Execution guest Problem: KVM and QEMU try to set the guest's TOD clock after resume under PV, even though that is not permitted under SE. Hence,their view of the guest clock may deviate from the ultravisor's, possibly causing KVM to re-dispatch the guest too late on clock comparator interrupts. Solution: Don't set the clock after resume under PV. Note that kernel and QEMU patches are required in lockstep, to avoid a warning message in QEMU. Reproduction: 1. Start SE guest using libvirt. 2. Pause the guest using "virsh suspend", wait for a few seconds, resume using "virsh resume". 3. Run "time sleep 1" in the guest. 4. The sleep will sleep much longer than one second. Upstream-ID: 6973091d1b50ab4042f6a2d495f59e9db3662ab8 Preventive fix: yes Author:Nico Boehr Please note that fixing the described problem requires patches for the kernel as well as for QEMU. This bug covers the kernel part, whereas the required QEMU part is described and handled in the following related bug: Bug?200901 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - qemu part Both parts, the kernel and the qemu patches should be applied / released at the same time to avoid problems resulting in the following warning message for customers: 'warning: Unable to set KVM guest TOD clock: Operation not supported' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1999882/+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 2013186] Re: 5.15.0-69 breaks my wifi
Same problem, 67 -> wifi works, 69 -> wifi disapears. wireless card is ASUS PCE-AC88 Some digging supports theory that patch was backported to kernel 5.15.0-69 which treats valid value as faulty/indication of error therefore preventing loading of module: [ 2740.647600] brcmfmac :0d:00.0: brcmf_pcie_init_ringbuffers: invalid > max_flowrings(264). Reference: https://lore.kernel.org/all/3c470a48-e971-9991-e096-3adfe1cc4...@broadcom.com/ https://lore.kernel.org/all/20220929031001.9962-3-ian@infineon.com/ https://askubuntu.com/questions/1461414/lack-of-wireless-connection-ubuntu-22-04-2-and-asus-pce-ac88 https://www.reddit.com/r/archlinux/comments/104pqv9/no_wifi_since_kernel_update_yesterday/ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2013186 Title: 5.15.0-69 breaks my wifi Status in linux package in Ubuntu: Confirmed Bug description: Latest linux kernel completely kills my Wifi. Have had to use the GRUB boot loader to revert the kernel back twice. Kernel 5.15.0-67 works perfectly with my wifi. In network settings the wifi option is entirely missing when I am on the -69 version. Output of command `lspci`: ➜ ~ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a80a 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge 04:00.0 Network controller: Broadcom Inc. and subsidiaries Device 43c3 (rev 04) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 26) 06:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 06:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 07:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 09:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) 09:00.1 Audio device: NVIDIA Corporation
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield -- 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+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 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield -- 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/1951447 Title: ubuntu_kernel_selftests: net:udpgso_bench.sh failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: 04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh 04:41:59 DEBUG| [stdout] # ipv4 04:41:59 DEBUG| [stdout] # tcp 04:42:00 DEBUG| [stdout] # tcp tx: 2736 MB/s46415 calls/s 46415 msg/s 04:42:00 DEBUG| [stdout] # tcp rx: 2737 MB/s46161 calls/s 04:42:01 DEBUG| [stdout] # tcp tx: 2735 MB/s46392 calls/s 46392 msg/s 04:42:01 DEBUG| [stdout] # tcp rx: 2739 MB/s46226 calls/s 04:42:02 DEBUG| [stdout] # tcp tx: 2717 MB/s46092 calls/s 46092 msg/s 04:42:02 DEBUG| [stdout] # tcp zerocopy 04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m 04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1 04:42:54 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 04:42:54 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 252, in run_once raise error.TestError(test_name + ' failed.') TestError: net:udpgso_bench.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+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 1986717] Re: [SRU]Update ice driver to support E823 devices
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield -- 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/1986717 Title: [SRU]Update ice driver to support E823 devices Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low These patches did not cherry pick cleanly I had to make some minor changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+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 1999882] Re: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/1999882 Title: [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Description: KVM: s390: pv: don't allow userspace to set the clock under PV Symptom: Timer issues and RCU stalls after suspending and resuming an IBM Secure Execution guest Problem: KVM and QEMU try to set the guest's TOD clock after resume under PV, even though that is not permitted under SE. Hence,their view of the guest clock may deviate from the ultravisor's, possibly causing KVM to re-dispatch the guest too late on clock comparator interrupts. Solution: Don't set the clock after resume under PV. Note that kernel and QEMU patches are required in lockstep, to avoid a warning message in QEMU. Reproduction: 1. Start SE guest using libvirt. 2. Pause the guest using "virsh suspend", wait for a few seconds, resume using "virsh resume". 3. Run "time sleep 1" in the guest. 4. The sleep will sleep much longer than one second. Upstream-ID: 6973091d1b50ab4042f6a2d495f59e9db3662ab8 Preventive fix: yes Author:Nico Boehr Please note that fixing the described problem requires patches for the kernel as well as for QEMU. This bug covers the kernel part, whereas the required QEMU part is described and handled in the following related bug: Bug?200901 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - qemu part Both parts, the kernel and the qemu patches should be applied / released at the same time to avoid problems resulting in the following warning message for customers: 'warning: Unable to set KVM guest TOD clock: Operation not supported' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1999882/+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 2004132] Re: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield -- 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/2004132 Title: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2004132 [Impact] xfstests btrfs/154 fails on both Bionic and Focal, leading to a kernel oops and the btrfs volume being forced readonly. In btrfs, item key collision is allowed for some item types, namely dir item and inode references. When inserting items into the btree, there are two objects, the btrfs_item and the item data. These objects must fit within the btree nodesize. When a hash collision occurs, and we call btrfs_search_slot() to place the objects in the tree, when btrfs_search_slot() reaches the leaf node, a check is performed to see if we need to split the leaf. The check is incorrect, returning that we need to split the leaf, since it thinks that both btrfs_item and the item data need to be inserted, when in reality, the item can be merged with the existing one and no new btrfs_item will be inserted. split_leaf() will return EOVERFLOW from following code: if (extend && data_size + btrfs_item_size_nr(l, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(fs_info)) return -EOVERFLOW; In the rename case, btrfs_check_dir_item_collision() is called early stages of treewalking, and correctly calculates the needed size, taking into account that a hash collision has occurred. data_size = sizeof(*di) + name_len; if (data_size + btrfs_item_size_nr(leaf, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(root->fs_info)) The two sizes reported from btrfs_check_dir_item_collision() and btrfs_search_slot() are different, and rename fails due to split_leaf() returning -EOVERFLOW, leading to transaction abort and forcing the volume readonly. Kernel oops: BTRFS: Transaction aborted (error -75) WARNING: CPU: 0 PID: 2921 at /build/linux-fTmV3T/linux-4.15.0/fs/btrfs/inode.c:10217 btrfs_rename+0xcf1/0xdf0 [btrfs] CPU: 0 PID: 2921 Comm: python3 Not tainted 4.15.0-202-generic #213-Ubuntu RIP: 0010:btrfs_rename+0xcf1/0xdf0 [btrfs] RSP: 0018:9e6f4183fd20 EFLAGS: 00010282 RAX: RBX: 91a493f27b98 RCX: 0006 RDX: 0007 RSI: 0096 RDI: 91a4bfc1b4d0 RBP: 9e6f4183fdc0 R08: 02b4 R09: 0004 R10: R11: 0001 R12: 0236 R13: 91a493f56518 R14: 91a4b6b57b40 R15: 91a493f27b98 FS: 7f6041081740() GS:91a4bfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6040fe84c8 CR3: 00015c8ca005 CR4: 00760ef0 PKRU: 5554 Call Trace: btrfs_rename2+0x1d/0x30 [btrfs] vfs_rename+0x46e/0x960 SyS_rename+0x362/0x3c0 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 Code: 0f ba a8 d0 cd 00 00 02 72 2b 41 83 f8 fb 0f 84 d9 00 00 00 44 89 c6 48 c7 c7 68 43 4b c0 44 89 55 80 44 89 45 98 e8 8f 5c a6 d0 <0f> 0b 44 8b 45 98 44 8b 55 80 44 89 55 80 44 89 c1 44 89 45 98 ---[ end trace 9c6b87a19f4436f3 ]--- BTRFS: error (device vdd) in btrfs_rename:10217: errno=-75 unknown BTRFS info (device vdd): forced readonly [Testcase] Start a fresh Bionic or Focal VM. Attach two scratch disks, I used standard virtio disks with 3gb of storage each. These disks are /dev/vdc and /dev/vdd. Compile xfstests: $ sudo apt-get install acl attr automake bc dbench dump e2fsprogs fio gawk \ gcc git indent libacl1-dev libaio-dev libcap-dev libgdbm-dev libtool \ libtool-bin libuuid1 lvm2 make psmisc python3 quota sed \ uuid-dev uuid-runtime xfsprogs linux-headers-$(uname -r) sqlite3 make $ sudo apt-get install f2fs-tools ocfs2-tools udftools xfsdump \ xfslibs-dev $ git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git $ cd xfstests-dev $ make $ sudo su # mkdir
[Kernel-packages] [Bug 2006391] Re: net:fcnal-test.sh 'nettest' command not found on F/K
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2006391 Title: net:fcnal-test.sh 'nettest' command not found on F/K Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: On Focal and Kinetic the fcnal-test.sh does not run because it reports that 'nettest' command not found; skipping tests This is due to the nettest binary not being found in the path and skipping the tests, but it is built and exists in the net directory where the tests are run. There are also other tests in selftests/net that are skipped due to the binary being missing. There is a patch upstream "selftests/net: Find nettest in current directory" (bd5e1e42826f18147afb0) that fixes this by looking in the current directory. The patch is in Jammy through stable updates, but the patch hasnt made it to the other stable trees yet for whatever reasons so might as well just cherry-pick them into F/K. - [Impact] fcnal-test.sh in selftests/net gets skipped with 'nettest' command not found because its looking for the nettest binary in the path and not in the current directory where the binary is built and run from. There are also other tests in net that are skipped due to this binary not being found. [Fix] Add the current directory to the path and check again. This patch exists in Jammy through a stable update but hasn't made it to the other upstream-stable trees yet, but might as well get the patch in our other trees to enable this test to run. [Backport] For focal patch skip the pmtu.sh file as nettest is not run there and is not checked. Also minor context adjustments on return variable. [Potential regression] None. Just enabling the tests to run. [Tests] Verified tests are now not skipped and run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006391/+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 2006453] Re: Fix selftests/ftracetests/Meta-selftests
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+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 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2006692 Title: net:fcnal-test.sh didn't return a non-zero value even with some sub- tests failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The net/fcnal-test.sh on F/J won't return a non-zero value even with some sub test cases failed, here is an example on Jammy: # Tests passed: 857 # Tests failed: 5 ok 1 selftests: net: fcnal-test.sh Therefore it's marked as PASSED on our report and making it difficult to spot these failures: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] [Fix] * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code This patch can be cherry-picked into Focal and Jammy kernel. We don't have this test in Bionic, and this patch has already landed on Kinetic and OEM-5.17 [Test] Run the patched test, the return value will be 1 whenever the number of failed test cases is not 0. [Where problems could occur] Change limited to testing tools, but we're expected to see new failures in Jammy. With bug 2006391 fixed later on, we will see failures reported in F/K as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+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 2007219] Re: xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield -- 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/2007219 Title: xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2007219 [Impact] A deadlock exists in the XFS filesystem that occurs when the XFS log buffer becomes completely exhausted. XFS maintains a circular ring buffer for the log, and it is a fixed size. To be able to create a transaction, you need to be able to reserve space on the log buffer. Certain ioend transactions, such as file append, can be preallocated for a negligible performance gain. This takes up space in the log buffer, and these preallocated ioends are placed on a workqueue, behind other ioends that are not preallocated. The deadlock occurs when the XFS log buffer is running low on space, and an ioend append transaction comes in. It is preallocated, consuming nearly all of the remaining XFS log buffer space, and is placed at the very end of the ioend workqueue. The kernel then takes a ioend from the top of the ioend workqeueue, creates a transaction, xfs_trans_alloc(), attempts to allocate space for it, xfs_trans_reserve(), xfs_log_reserve(), and then waits in a while loop checking free space in the log, xlog_grant_head_check(), xlog_grant_head_wait(). Since there is no space, the thread sleeps with schedule(). This happens with all ioend transactions, since the log is exhausted and I/O is not moving. Since I/O never moves, the thread is never woken up, and we get hung task timeouts, with system failure shortly afterward. An example hung task timeout is: INFO: task kworker/60:0:4002982 blocked for more than 360 seconds. Tainted: G OE 5.4.0-137-generic #154-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kworker/60:0D0 4002982 2 0x90004080 Workqueue: xfs-conv/dm-3 xfs_end_io [xfs] Call Trace: __schedule+0x2e3/0x740 schedule+0x42/0xb0 xlog_grant_head_wait+0xb9/0x1e0 [xfs] xlog_grant_head_check+0xde/0x100 [xfs] xfs_log_reserve+0xc9/0x1e0 [xfs] xfs_trans_reserve+0x17a/0x1e0 [xfs] xfs_trans_alloc+0xda/0x170 [xfs] xfs_iomap_write_unwritten+0x128/0x2f0 [xfs] xfs_end_ioend+0x15b/0x1b0 [xfs] xfs_end_io+0xb1/0xe0 [xfs] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x40 There is no known workaround, other than to have a larger log buffer at filesystem creation, but even then, it only buys you time until you get high enough load to exhaust the log buffer. [Fix] This was fixed in 5.13-rc1 by the following patch: commit 7cd3099f4925d7c15887d1940ebd65acd66100f5 Author: Brian Foster Date: Fri Apr 9 10:27:43 2021 -0700 Subject: xfs: drop submit side trans alloc for append ioends Link: https://github.com/torvalds/linux/commit/7cd3099f4925d7c15887d1940ebd65acd66100f5 The patch more or less removes all preallocated ioend transactions, and instead, when ioend appends are needed, they go to the standard workqueue like any other ioend, where transactions are allocated when they reach the top of the workqueue. The patch required some backporting for Focal. The changes to the patch itself is minimal and should be straightforward to read, however, the changes to the XFS ioend subsystem between 5.4 and 5.13-rc1 were quite extreme, with a lot of refactoring taking place over very many commits. Additionally, the patch was part of a five part series, the first, fixes the deadlock, and the rest remove all the code to do with transaction preallocation. It is safe to leave the rest of the code in place. It will become dead code, but it will not be reachable, and not cause any risk of regression, due to ioend->io_append_trans always being NULL, and not entering into any of the if statements. [Testcase] There is currently no known testcase for this issue. The issue has only been seen in a
[Kernel-packages] [Bug 2007581] Re: gpio: Restrict usage of GPIO chip irq members before initialization
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2007581 Title: gpio: Restrict usage of GPIO chip irq members before initialization Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] GPIO chip irq members are exposed before they could be completely initialized and this leads to race conditions. One such issue was observed for the gc->irq.domain variable which was accessed through the pwr-mlxbf.c driver in gpiochip_to_irq() before it could be initialized by gpiochip_add_irqchip(). This resulted in Kernel NULL pointer dereference. This is a well known issue in the linux community and was fixed via 2 commits: 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 and 06fb4ecfeac7e00d6704fa5ed19299f2fefb3cc9 (since the previous commit caused a regression) This race condition is intermittent and hard to reproduce. [Fix] * Cherry pick: 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 to fix the bug at stake * cherry-pick: 06fb4ecfeac7e00d6704fa5ed19299f2fefb3cc9 to fix a regression introduced by the previous commit [Test Case] * Check that the gpio-mlxbf2.c driver is loaded with no kernel panic * check that all drivers dependent on gpio-mlxbf2.c driver are loaded (mlxbf-gige and pwr-mlxbf) * do 5000 reboots to make sure this race condition no longer happens [Regression Potential] This could cause some regression with the use of gpio interrupts so it is important to test the dependent drivers mlxbf-gige and pwr-mlxbf. Trigger power reset interrupt to test pwr-mlxbf and bring down/up the oob_net0 interface to test mlxbf-gige. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2007581/+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 2008136] Re: netfilter: flowtable: add counter support in HW offload
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-focal -- 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/2008136 Title: netfilter: flowtable: add counter support in HW offload Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) While conntrack tuples are offloaded to hardware and conntrack packet accounting is enabled, offloaded packets aren't counted. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. ef803b3cf96a netfilter: flowtable: add counter support in HW offload 9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add() note: need to change a little due to cherry-pick conflict with 24384e28586c netfilter: flowtable: Set offload timeouts according to proto values * 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 TCP connection, e.g: on mlx5 VF1 iperf -s on mlx5 VF2 iperf -c -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i See counters (packets=.*) advancing while tuples were offloaded: ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136/+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 2015033] Re: 5.15.0-69 breaks my wifi
** This bug is no longer a duplicate of bug 2013397 Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module ** This bug has been marked a duplicate of bug 2013186 5.15.0-69 breaks my wifi -- 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/2015033 Title: 5.15.0-69 breaks my wifi Status in linux package in Ubuntu: Confirmed Bug description: Latest linux kernel completely kills my Wifi. Have had to use the GRUB boot loader to revert the kernel back twice. wlan devices are recognized, but they cannot find any network. Reinstall of device driver did not help. Revert to Kernel 5.15.0-67 brings wlan back. see also bug 2013186 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas1177 F pulseaudio /dev/snd/controlC1: andreas1177 F pulseaudio /dev/snd/controlC2: andreas1177 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 06:32:09 2023 InstallationDate: Installed on 2019-04-09 (1454 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408.2) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=1bc58a0c-41ca-4f6a-ad9d-df0a5fe02b37 ro quiet splash systemd.unified_cgroup_hierarchy=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-10 (296 days ago) dmi.bios.date: 12/21/2018 dmi.bios.release: 7.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS XI HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd12/21/2018:br7.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015033/+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 2013397] Re: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module
*** This bug is a duplicate of bug 2013186 *** https://bugs.launchpad.net/bugs/2013186 ** This bug has been marked a duplicate of bug 2013186 5.15.0-69 breaks my wifi -- 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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to:
[Kernel-packages] [Bug 2015033] Re: 5.15.0-69 breaks my wifi
** This bug has been marked a duplicate of bug 2013397 Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module -- 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/2015033 Title: 5.15.0-69 breaks my wifi Status in linux package in Ubuntu: Confirmed Bug description: Latest linux kernel completely kills my Wifi. Have had to use the GRUB boot loader to revert the kernel back twice. wlan devices are recognized, but they cannot find any network. Reinstall of device driver did not help. Revert to Kernel 5.15.0-67 brings wlan back. see also bug 2013186 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas1177 F pulseaudio /dev/snd/controlC1: andreas1177 F pulseaudio /dev/snd/controlC2: andreas1177 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 06:32:09 2023 InstallationDate: Installed on 2019-04-09 (1454 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408.2) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=1bc58a0c-41ca-4f6a-ad9d-df0a5fe02b37 ro quiet splash systemd.unified_cgroup_hierarchy=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-10 (296 days ago) dmi.bios.date: 12/21/2018 dmi.bios.release: 7.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS XI HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd12/21/2018:br7.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015033/+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 2015033] Re: 5.15.0-69 breaks my wifi
please do handle this as duplicate as the bug 2013186 stays in state unconfirmed because of missing log files. ** This bug is no longer a duplicate of bug 2013186 5.15.0-69 breaks my wifi -- 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/2015033 Title: 5.15.0-69 breaks my wifi Status in linux package in Ubuntu: Confirmed Bug description: Latest linux kernel completely kills my Wifi. Have had to use the GRUB boot loader to revert the kernel back twice. wlan devices are recognized, but they cannot find any network. Reinstall of device driver did not help. Revert to Kernel 5.15.0-67 brings wlan back. see also bug 2013186 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas1177 F pulseaudio /dev/snd/controlC1: andreas1177 F pulseaudio /dev/snd/controlC2: andreas1177 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 06:32:09 2023 InstallationDate: Installed on 2019-04-09 (1454 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408.2) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=1bc58a0c-41ca-4f6a-ad9d-df0a5fe02b37 ro quiet splash systemd.unified_cgroup_hierarchy=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-10 (296 days ago) dmi.bios.date: 12/21/2018 dmi.bios.release: 7.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS XI HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd12/21/2018:br7.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015033/+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
