[Kernel-packages] [Bug 2027959] Re: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33
@Renjith, @Mario, please help confirm three more commits needed as listed in bug description. -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: Fix Released Bug description: Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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 2027959] [NEW] Follow-up: potential S3 issue for amdgpu Navi 31/Navi33
Public bug reported: Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-firmware (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-firmware (Ubuntu Lunar) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** No longer affects: linux-firmware (Ubuntu Kinetic) ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Lunar) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Description changed: Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release + * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: Fix Released Bug description: Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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 2026625] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r
make -C /lib/modules/6.2.0-24-generic/build M=/var/lib/dkms/rcraid/9.3.0/build/src modules make[1]: Entering directory '/usr/src/linux-headers-6.2.0-24-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 You are using: gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 CC [M] /var/lib/dkms/rcraid/9.3.0/build/src/rc_init.o In file included from /var/lib/dkms/rcraid/9.3.0/build/src/rc.h:70, from /var/lib/dkms/rcraid/9.3.0/build/src/rc_init.c:25: /var/lib/dkms/rcraid/9.3.0/build/src/rc_msg_platform.h:31:10: fatal error: stdarg.h: No such file or directory 31 | #include | ^~ compilation terminated. make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/rcraid/9.3.0/build/src/rc_init.o] Error 1 make[1]: Leaving directory '/usr/src/linux-headers-6.2.0-24-generic' make[1]: *** [Makefile:2026: /var/lib/dkms/rcraid/9.3.0/build/src] Error 2 make: *** [Makefile:100: all] Error 2 make: Leaving directory '/var/lib/dkms/rcraid/9.3.0/build/src' # # Driver module not built -- install aborted! # -- 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/2026625 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: Occurred during installation ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Jul 8 12:13:10 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 MachineType: Alienware Alienware Aurora Ryzen Edition ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=b6810121-855e-41ef-a565-e89e88e0b75f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-09 (60 days ago) dmi.bios.date: 01/13/2023 dmi.bios.release: 2.4 dmi.bios.vendor: Alienware dmi.bios.version: 2.4.0 dmi.board.name: 0NWN7M dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr2.4.0:bd01/13/2023:br2.4:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.4.0:rvnAlienware:rn0NWN7M:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku098E: dmi.product.family: Alienware dmi.product.name: Alienware Aurora Ryzen Edition dmi.product.sku: 098E dmi.product.version: 2.4.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026625/+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 2026625] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r
You have an unsupported DKMS modules installed that prevent the kernel installation/upgrade. Remove it and retry: $ dkms remove rcraid/9.3.0 --all ** Changed in: linux (Ubuntu) Status: New => 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/2026625 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: Occurred during installation ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Jul 8 12:13:10 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 MachineType: Alienware Alienware Aurora Ryzen Edition ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=b6810121-855e-41ef-a565-e89e88e0b75f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-09 (60 days ago) dmi.bios.date: 01/13/2023 dmi.bios.release: 2.4 dmi.bios.vendor: Alienware dmi.bios.version: 2.4.0 dmi.board.name: 0NWN7M dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr2.4.0:bd01/13/2023:br2.4:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.4.0:rvnAlienware:rn0NWN7M:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku098E: dmi.product.family: Alienware dmi.product.name: Alienware Aurora Ryzen Edition dmi.product.sku: 098E dmi.product.version: 2.4.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026625/+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 2026625] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r
You have an unsupported DKMS modules installed that prevent the kernel installation/upgrade. Remove it and retry: $ dkms remove rcraid/9.3.0 --all -- 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/2026625 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: Occurred during installation ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Jul 8 12:13:10 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 MachineType: Alienware Alienware Aurora Ryzen Edition ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=b6810121-855e-41ef-a565-e89e88e0b75f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-09 (60 days ago) dmi.bios.date: 01/13/2023 dmi.bios.release: 2.4 dmi.bios.vendor: Alienware dmi.bios.version: 2.4.0 dmi.board.name: 0NWN7M dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr2.4.0:bd01/13/2023:br2.4:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.4.0:rvnAlienware:rn0NWN7M:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku098E: dmi.product.family: Alienware dmi.product.name: Alienware Aurora Ryzen Edition dmi.product.sku: 098E dmi.product.version: 2.4.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026625/+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 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
See follow-up in bug 2027959. -- 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/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2026821] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r
make -j8 KERNELRELEASE=6.2.0-24-generic -j8 -C /lib/modules/6.2.0-24-generic/build M=/var/lib/dkms/amdgpu/17.40-492261/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-24-generic (x86_64) Consult /var/lib/dkms/amdgpu/17.40-492261/build/make.log for more information. dkms autoinstall on 6.2.0-24-generic/x86_64 failed for amdgpu(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! -- 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/2026821 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: installation problem ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakti 1914 F wireplumber /dev/snd/seq:shakti 1912 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Tue Jul 11 15:10:15 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-10 (30 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 25a7:fa67 Areson Technology Corp 2.4G Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=4fb6c419-cba7-43ff-856c-3adb6810ed18 ro 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.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 02DYKC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd03/13/2023:br1.23:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn02DYKC:rvrA00:cvnDellInc.:ct10:cvr:sku096A: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.product.sku: 096A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026821/+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 2026821] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r
You have an unsupported DKMS modules installed that prevent the kernel installation/upgrade. Please remove it and retry: $ dkms remove amdgpu/17.40-492261 --all ** Changed in: linux (Ubuntu) Status: New => 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/2026821 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: installation problem ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakti 1914 F wireplumber /dev/snd/seq:shakti 1912 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Tue Jul 11 15:10:15 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-10 (30 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 25a7:fa67 Areson Technology Corp 2.4G Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=4fb6c419-cba7-43ff-856c-3adb6810ed18 ro 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.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 02DYKC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd03/13/2023:br1.23:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn02DYKC:rvrA00:cvnDellInc.:ct10:cvr:sku096A: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.product.sku: 096A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026821/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Description changed: [impact] + While booting into OOBE, the screen freeze [AMD W7500 only] [fix] + AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. + Intel CPU may not support the dynamic lane/speed switching. + + Turn off the dynamic gen/lane switching when platform is Intel. + amdgpu driver would pick the highest gen/lane instead. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] + low, just fix the pci gen/lane. -- 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in linux package in Ubuntu: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Description changed: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. - Turn off the dynamic gen/lane switching when platform is Intel. - amdgpu driver would pick the highest gen/lane instead. + - Detect Intel x86 systems that don't support dynamic switching + - Override the input caps to maximum supported for that system + - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] - low, just fix the pci gen/lane. + low, this could lead issue when setting higher speeds than supported. ** Description changed: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. + Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. -- 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in linux package in Ubuntu: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027957/+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 2027957] Re: Fix AMDGPU: the screen freeze with W7500
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-2024460 somerville ** Tags added: originate-from-2026462 -- 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/2027957 Title: Fix AMDGPU: the screen freeze with W7500 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: New Bug description: [impact] While booting into OOBE, the screen freeze [AMD W7500 only] [fix] AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled. Intel CPU may not support the dynamic lane/speed switching. Solution is, - Detect Intel x86 systems that don't support dynamic switching - Override the input caps to maximum supported for that system - Force all PCIe levels to use the same settings, rather than try to configure each level differently. [test cases] 1. boot with w7500 2. the screen doesn't freeze and can't find the error message in dmesg. "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out" [where the issue could happen] low, this could lead issue when setting higher speeds than supported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2027957/+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 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
Kernel 5.15.0-79.86 from jammy-proposed is verified to fix this bug. ** 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+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 2002226] Re: Support for kernels compiled with CONFIG_EFI_ZBOOT
This is resolved correctly in grub2-2.12~rc1. Once that hits mantic, we
will be able to upgrade most of our arm64 kernels to that (generic,
cloud).
Kernels that use u-boot (direct), abootimg, piboot will have to stay as
they are - unless they gain zboot image format boot support.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Support for kernels compiled with CONFIG_EFI_ZBOOT
+ Add support for kernels compiled with CONFIG_EFI_ZBOOT
--
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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
TBD
[Where problems could occur]
TBD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
** Patch added: "0001-UBUNTU-Config-Turn-on-CONFIG_EFI_ZBOOT-on-ARM64.patch"
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2002226/+attachment/5686814/+files/0001-UBUNTU-Config-Turn-on-CONFIG_EFI_ZBOOT-on-ARM64.patch
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: grub2-unsigned (Ubuntu)
Importance: Undecided => Medium
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: grub2-unsigned (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
--
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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
TBD
[Where problems could occur]
TBD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
>> Kernels that use u-boot (direct), abootimg, piboot will have to stay
as they are - unless they gain zboot image format boot support.
Hello Dimitri,
zboot kernels are regualr EFI binaries. Where did you see problems in
booting them with U-Boot's bootefi command?
Best regards
Heinrich
--
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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
TBD
[Where problems could occur]
TBD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 2026338] Re: Update Mantic to 1.2.9
I had to run $ update-maintainer The original maintainer is: Debian ALSA Maintainers Resetting as: Ubuntu Developers after applying the merge debdiff. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2026338 Title: Update Mantic to 1.2.9 Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Mantic: New Bug description: The current version in Mantic is 1.2.6.3-1ubuntu10 which is based on upstream 1.2.6.3 which is from December 2021. From the 17 Ubuntu patches [1] all except the last three are in Debian unstable 1.2.9-1. We haven't updated since Jammy so let's do that. [1] 0001-ucm2-add-PinePhone-configuration.patch 0002-ucm2-add-PineTab-configuration.patch 0003-ucm2-add-improved-Librem-5-profiles.patch 0004-HDA-acp-avoid-to-create-Mic-ACP-LED-control-for-the-.patch 0005-acp6x-add-initial-support-for-AMD-Yellow-Carp-ACP6x.patch sof-hda-dsp-fix-multiple-If.dmic-blocks.patch 0001-ucm2-sof-soundwire-add-basic-settings-for-RT1318-SDC.patch sof-soundwire-set-PGA-capture-switch-for-rt715-mic-i.patch ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch ucm2-sof-hda-dsp-If.devdmic-cleanup.patch sof-hda-dsp-Set-Dmic0-Capture-Switch-on.patch ucm2-sof-soundwire-Update-Mic-LED-settings.patch 0001-ucm2-HDA-Update-Mic-LED-settings-for-ACP-DMIC.patch 0006-sof-hda-dsp-Add-speaker-led-support.patch 0001-acp63-add-initial-support-for-AMD-Pink-Sardine-ACP63.patch 0002-acp63.conf-use-symbolic-link.patch 0003-acp62-add-initial-support-for-AMD-ACP-v6.2-RPL.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2026338/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
@Andreas firmware-sof in Mantic is 2.2.6, which already has everything in Acelan's merge proposal. @Steve Acelan's merge proposal indeed pulls in 16 new binaries from upstream's firmware-sof 2.2.5 and 2.2.6, more than this bug originally need. It's because when we roll out a new HWE kernel in the future, some users will eventually need the other firmwares. Do you advise us to: 1. update the bug description, or 2. submit a new MR with only the firmwares we need for this bug. -- 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/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Incomplete Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Hello Andreas, I saw the same error on a 13th Gen Intel(R) Core(TM) i7-1370PE using the IOT release of jammy desktop. I can confirm that installing mutter from jammy-proposed fixed the issue on my system. $ uname -a Linux amr-rplp-01 5.15.0-1034-intel-iotg #39-Ubuntu SMP Thu Jun 22 20:56:05 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy Now I have this mutter release: $ apt list -a mutter Listing... Done mutter/jammy-proposed,now 42.9-0ubuntu3 amd64 [installed] mutter/jammy-updates 42.9-0ubuntu1 amd64 mutter/jammy 42.0-3ubuntu2 amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2022098] Re: Severe NFS performance degradation after LP #2003053
I am removing the duplication of this bug due to the fact that this requires a separate fix from bug 2015827, and the fix is still applied and queued for release. ** This bug is no longer a duplicate of bug 2015827 NFS performance issue while clearing the file access cache upon login -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux package in Ubuntu: Confirmed Status in linux-gke package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-gke source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gke source package in Jammy: Fix Released Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+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 2015827] Re: NFS performance issue while clearing the file access cache upon login
Hello @ihmesa, We cannot release linux-5.4.0-154.171 anymore, it has been replaced in -proposed by linux-5.4.0-156.173 which also contains the same fix. We would appreciate if you could help us test the fix from this version in -proposed. Thank you. -- 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/2015827 Title: NFS performance issue while clearing the file access cache upon login Status in linux package in Ubuntu: In Progress Bug description: The performance issue that has been observed may be attributed to an increase in NFS ACCESS operations, possibly due to a new mechanism introduced in the Linux 6.2-rc3 NFS client side. This mechanism clears the access cache as soon as the cache timestamp becomes older than the user's login time, with the primary objective of preventing the NFS client's access cache from becoming stale due to any changes made to the user's group membership on the server after the user has already logged in on the client. It's worth noting that POSIX only refreshes the user's supplementary group information upon login. Upstream has taken into consideration that users may reasonably expect the access cache to be cleared when they log out and log back in again, with all behavior returning to normal after the replacement. The performance overhead can be particularly noticeable when applications or users switch to other privileged users via commands such as "su" to operate on NFS-mounted folders. In such cases, the privileged user's login time will be renewed, and NFS ACCESS operations will need to be re-sent, potentially leading to performance degradation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827/+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 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar-linux verification-needed-lunar -- 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/2024900 Title: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+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 2023952] Re: UNII-4 5.9G Band support request on 8852BE
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar-linux verification-needed-lunar -- 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/2023952 Title: UNII-4 5.9G Band support request on 8852BE Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The platform can't connect to AP with Wi-Fi 5.9G capability and wifi function doesn't work properly. [Fix] Realtek has verified the 5.9G function with 8852BE WLAN on WarlockMLK2 Intel platform and submitted upstream. https://lore.kernel.org/linux-wireless/20230508081211.38760-1-pks...@realtek.com/ Included in v6.5-rc e3b77c06c886 wifi: rtw89: support U-NII-4 channels on 5GHz band a002f98123dd wifi: rtw89: regd: judge UNII-4 according to BIOS and chip e897b0bef38a wifi: rtw89: introduce realtek ACPI DSM method [Test] Verified by ODM and can connect to 5.9G AP [Where problems could occur] commit 5 added new callback functions which change the device behavior during suspending/resuming, not sure if this impacts old chips. Other commits looks normal and should not lead to regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023952/+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 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar-linux verification-needed-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. The similiar patch has been included in v6.4-rc7 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar-linux verification-needed-lunar -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+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 2023650] Re: Add microphone support of the front headphone port on P3 Tower
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2023650 Title: Add microphone support of the front headphone port on P3 Tower Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed 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 Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The 3.5mm headphone port in front panel cannot detect the microphone. [Fix] Add quirk for headset mic pin on P3 Tower. [Test] Tested with alsa audio, mic works fine. [Where problems could occur] Low risk to add specific hardware ID. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023650/+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 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete 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: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2023539 Title: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: [Impact] No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2 [Fix] Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2. [Test] Tested with alsa audio, audio works fine. [Where problems could occur] Risk low due to specific hardware. These 2 patches are already in Unstable and OEM-6.1 already got them via stable updates. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023539/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete 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 Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released 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 Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2023004 Title: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress 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 Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [impact] The default sync pulse length for fast wake AUX transactions was changed from 18 to 10, which was causing issues with some eDP panels. [fix] Revert the sync pulse length for fast wake AUX transactions back to the hardware default of 18 (10 precharge + 8 preamble). [test cases] 1. configure with thunderbolt.clx=0. 2. check edp's behavior and it should work well and there's no garbage. [where the issue could happen] low, By reverting this setting back to the default, this commit restores stability for configurations using fast wake AUX transactions, especially those involving eDP panels that were incompatible with the shorter sync pulse length. The longer, hardware-default sync pulse length is compatible with more use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023004/+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 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid 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.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. [Misc] Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, so skip Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid 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.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justfication] [Impact] On AMD Phoenix platforms, system may hang, or reboot while resuming from suspend. [Fix] Two patches in v6.4-rc3 for amdgpu. The first one is pulled for dependency. [Test Case] $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 $ checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots [Where problems could occur] The fix is to safely guard register access as it should be. No potential problem identified so far. [Other Info] This should affects v6.1 or above as which AMD Phoenix are supported, and has been included in mantic-6.3 through stable-6.3.4 and in oem-6.1 through stable-6.1.30, leaving lunar-6.2 unfixed only. == original bug report == To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dm
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+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 2020356] Re: generate linux-lib-rust only on amd64
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2020356 Title: generate linux-lib-rust only on amd64 Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] Rust is only supported by amd64 at the moment, so there is no reason to generate linux-lib-rust packages on the other architectures. [Test case] Simply build the kernel, generating all the deb packages. [Fix] Produce linux-lib-rust only on amd64. [Regression potential] If Rust will be enabled on other architectures we need to remember to undo this change, or selectively enable the packaging on the architectures that will get the Rust support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020356/+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 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1
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-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.
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-lunar
** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2020062
Title:
No HDMI/DP audio output on dock(Nvidia GPU)
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
When the machine is docked with an external monitor, it is able to output
display, but the HDMI/DP audio output option is lost in DGFF Hybrid
Discrete/Discrete mode(Nvidia GPU).
[Fix]
Nvidia provides a patch to fix it
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
in 6.4-rc3
dc4f2ccaeddd ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table
[Test]
Verified on the target machine.
{Where problems could occur]
The patch just adds IDs, and won't lead to any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020062/+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 2019915] Re: Enable audio LEDs on HP laptops
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2019915 Title: Enable audio LEDs on HP laptops Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Audio LEDs are not working on some new HP laptops. [Fix] Use Realtek codec specific method, VREF, to enable audio LEDs. [Test] With the fix applied, audio LEDs function correctly. [Where problems could occur] The fix only applies to two hardwares, so other hardwares are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2019915/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-kvm source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-kvm source package in Mantic: In Progress Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_IMA_ARCH_POLICY (The latter is needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/2018591 Title: Enable Tracing Configs for OSNOISE and TIMERLAT Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: In Progress Bug description: == SRU Justification == These config changes will allow tracing with the OSNOISE and TIMERLAT tracing tools. These tracers can be enabled at run-time and should not affect performance or add any additional overhead. == Fix == UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs == Regression Potential == Low. These config changes will just allow the use of tracing tools. == Test Case == Test build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018591/+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 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1
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-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.
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-lunar-linux-riscv
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in Release Notes for Ubuntu:
New
Status in linux package in Ubuntu:
Triaged
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Triaged
Status in linux-hwe-5.19 source package in Mantic:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1988806/+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 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- 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/1977827 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker[PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command[PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter[PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing[PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types[PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments[PASS] # [51] Kretprobe dynamic event with maxactive[PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events[PASS] # [54] Kprobe profile[PASS] # [55] Uprobe event parser error log check [PASS] #
[Kernel-packages] [Bug 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar ** Tags added: kernel-spammed-lunar-linux-riscv verification-needed-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Fix only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Triaged Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.13 source package in Lunar: Invalid Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-5.13 source package in Mantic: Invalid Status in linux-oem-5.14 source package in Mantic: Invalid Status in linux-oem-5.17 source package in Mantic: Invalid Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 1975592] Re: Enable Nezha board
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.1 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-lunar' to 'verification-done-lunar'. If the problem still exists, change the tag 'verification-needed-lunar' to 'verification-failed-lunar'. 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-lunar-linux-riscv verification-needed-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1975592 Title: Enable Nezha board Status in linux-allwinner package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Bug description: [Impact] integrate linux-allwinner patches into linux-riscv kernel [Test] * Newly built images should boot and work on both nezha and licheerv * Upgraded systems using old images should reboot and work on both nezha and licheerv * livecd-rootfs must continue to install linux-allwinner when building for nezha and licheerv [Implementation details] * linux[-image]-allwinner depends on new enough generic kernel with allwinner support pull request applied; and contains additional initramfs configuration to ensure booting is possible [Regression potential] Ensure this new build of linux-riscv doesn't regress on existing supported systems (sifive & qemu) scope: linux-riscv https://lists.ubuntu.com/archives/kernel-team/2023-May/139655.html u-boot-nezha patch attached linux-meta-riscv patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/1975592/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
** Tags added: patch
--
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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
TBD
[Where problems could occur]
TBD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 2027959] Re: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33
60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release introduced a regression on 11.0.1/11.0.4, which is why specifically requested (https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/16) below commit. 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 But if you need to take whole series to get there then yes this is an accurate list. Just make sure that the order is correct so the last one picked is 1c513ec74. -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: Fix Released Bug description: Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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 2025538] Re: Unrequested kernel update
Hi, on 23.04 again nvidia driver and kernel problems... had the same issue back in march under 22.10 with funny flickering screens to total black and back just after an update and therefore a totally unusable system, and guess? no maintainer showed interest in that messed up situation, so out of luck after several weeks and one upgrade to 23.04 with a persistent problem (lmao seriously the problem survived the transition from 22.10 to 23.04) i had updated the nvidia driver to the "beta" 535 driver and had a usable system... Now just 3 months later there it is again the same friggin problem with flickering screens and unusable system... hope that this bug request will result in some kind of patch with workable kernel and driver... but i lost hope and go to check if there is some "new" "betastyle" nvidia driver package greater than 535 in hope that i have again a usable system for at least 3 months until the game starts again... Seriously dear maintainers, take a deep breath, do a honest self assessment and recognize your abilities and accept them, afterwards you can implement then a rollback mechanism for updates in apt and snap so that we users haven't to suffer any more and can at least roll one update back to something more usable instead of hoping that you get that stuff right before the sun freezes... sorry but i'm really frustrated and disappointed with the overall situation regarding the nvidia drivers... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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 2027983] [NEW] CONFIG_MPTCP_IPV6 is no longer enabled in Raspi Lunar in v6.2.0
Public bug reported:
Hello,
First, thank you for maintaining this kernel package for RPi!
When looking at something else[1], Phil Elwell from Raspbian OS noticed
that in the Ubuntu Raspi Lunar image with a kernel v6.2,
CONFIG_MPTCP_IPV6 is not enabled.
I guess this is because CONFIG_IPV6 is compiled as a module while it
should be inlined according to the source code [2][3]:
CONFIG_IPV6policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el':
'y', 's390x': 'y'}>
CONFIG_IPV6mark note
The note explicitly says that it should not be set as a module.
Note that the previous kernels v5.15 and v5.19 do have CONFIG_IPV6=y
(and CONFIG_MPTCP_IPV6=y) [4]. Also, the last v6.2 "generic" kernel
config is also OK (CONFIG_IPV6=y) [5].
It looks like the v6.2.0-1001.1 [6] was OK but not the next one,
6.2.0-1002.2 [7]. I hope this will help finding the "regression".
Cheers,
Matt
[1] https://github.com/raspberrypi/linux/pull/5487
[2]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/lunar/tree/debian.raspi/config/annotations
[3]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/lunar/tree/debian.master/config/annotations
[4] https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux-raspi/
[5] https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux/
[6]
https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux-raspi/6.2.0-1001.1/arm64-config.flavour.raspi
[7]
https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux-raspi/6.2.0-1002.2/arm64-config.flavour.raspi
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2027983
Title:
CONFIG_MPTCP_IPV6 is no longer enabled in Raspi Lunar in v6.2.0
Status in linux-raspi package in Ubuntu:
New
Bug description:
Hello,
First, thank you for maintaining this kernel package for RPi!
When looking at something else[1], Phil Elwell from Raspbian OS
noticed that in the Ubuntu Raspi Lunar image with a kernel v6.2,
CONFIG_MPTCP_IPV6 is not enabled.
I guess this is because CONFIG_IPV6 is compiled as a module while it
should be inlined according to the source code [2][3]:
CONFIG_IPV6policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el':
'y', 's390x': 'y'}>
CONFIG_IPV6mark note
The note explicitly says that it should not be set as a module.
Note that the previous kernels v5.15 and v5.19 do have CONFIG_IPV6=y
(and CONFIG_MPTCP_IPV6=y) [4]. Also, the last v6.2 "generic" kernel
config is also OK (CONFIG_IPV6=y) [5].
It looks like the v6.2.0-1001.1 [6] was OK but not the next one,
6.2.0-1002.2 [7]. I hope this will help finding the "regression".
Cheers,
Matt
[1] https://github.com/raspberrypi/linux/pull/5487
[2]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/lunar/tree/debian.raspi/config/annotations
[3]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/lunar/tree/debian.master/config/annotations
[4] https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux-raspi/
[5] https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux/
[6]
https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux-raspi/6.2.0-1001.1/arm64-config.flavour.raspi
[7]
https://kernel.ubuntu.com/~kernel-ppa/config/lunar/linux-raspi/6.2.0-1002.2/arm64-config.flavour.raspi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2027983/+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 2027988] [NEW] qla2xxx driver fails all paths
Public bug reported:
After upgrading an HP BL460 G7 from 20.04 to 22.04, the storage mounted from an
hp msa2324fc using the QLogic QMH2462 dual channel adapter fails all paths
after a while, usually less than an hour.
This occured with kernel 5.15.0-76-generic installed by upgrading, but gave
5.19.0-46-generic a shot hoping to be bug free.
In the same blade enclosure are other server blades connected to the same
storage via the same switches
with ubuntu 16.04 18.04 20.04 which operate as intended plus a couple more
non-blade servers.
When the issue occurs all cpu goes to 100 iowait, load average keeps climbing
up until i do
echo 1 > /sys/class/fc_host/host2/issue_lip ( and host3 ) and flush the
multipath device after using umount ( if mounted ) because it gets stuck
without even mounting it.
I verified multipathd.conf configuration if correct.
=== multipath.conf ===
blacklist {
devnode "^sda"
}
defaults {
polling_interval 5
fast_io_fail_tmo 5
dev_loss_tmo 10
checker_timeout 15
}
devices {
device {
vendor "HP"
product "MSA2312fc|MSA2324fc"
hardware_handler "0"
uid_attribute ID_SERIAL
path_selector "round-robin 0"
path_grouping_policy group_by_prio
failbackimmediate
rr_weight uniform
no_path_retry 18
rr_min_io 100
path_checkertur
prioalua
}
}
multipaths {
multipath {
wwid3600c0ff000daa122bf012d500100
alias wtsql
path_grouping_policygroup_by_prio
}
}
=== end multipath.conf ===
qla2xxx module parameters: "ql2xmaxqdepth=16 qlport_down_retry=10
ql2xloginretrycount=30 ql2xextended_error_logging=0x1e40"
lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
apt-cache policy linux-generic-hwe-22.04
linux-generic-hwe-22.04:
Installed: 5.19.0.46.47~22.04.21
Candidate: 5.19.0.46.47~22.04.21
Version table:
*** 5.19.0.46.47~22.04.21 500
500 http://gr.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
5.15.0.25.27 500
500 http://gr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jul 17 16:40:10 2023
SourcePackage: linux-signed-hwe-5.19
UpgradeStatus: Upgraded to jammy on 2023-07-12 (5 days ago)
mtime.conffile..etc.logrotate.d.apport: 2017-08-03T08:14:27.712298
** Affects: linux-signed-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
** Attachment added: "dmesg output from modprobe until all paths fail."
https://bugs.launchpad.net/bugs/2027988/+attachment/5686840/+files/dmesg.txt
--
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/2027988
Title:
qla2xxx driver fails all paths
Status in linux-signed-hwe-5.19 package in Ubuntu:
New
Bug description:
After upgrading an HP BL460 G7 from 20.04 to 22.04, the storage mounted from
an hp msa2324fc using the QLogic QMH2462 dual channel adapter fails all paths
after a while, usually less than an hour.
This occured with kernel 5.15.0-76-generic installed by upgrading, but gave
5.19.0-46-generic a shot hoping to be bug free.
In the same blade enclosure are other server blades connected to the same
storage via the same switches
with ubuntu 16.04 18.04 20.04 which operate as intended plus a couple more
non-blade servers.
When the issue occurs all cpu goes to 100 iowait, load average keeps climbing
up until i do
echo 1 > /sys/class/fc_host/host2/issue_lip ( and host3 ) and flush the
multipath device after using umount ( if mounted ) because it gets stuck
without even mounting it.
I verified multipathd.conf configuration if correct.
=== multipath.conf ===
blacklist {
devnode "^sda"
}
defaults {
polling_interval 5
fast_io_fail_tmo 5
dev_loss_tmo 10
checker_timeout 15
}
devices {
device {
vendor "HP"
product "MSA2312fc|MSA2324fc"
hardware_handler "0"
uid_attribute ID_SERIAL
path_selector "round-robin 0"
path_grouping_policy group_by_prio
failbackimmediate
[Kernel-packages] [Bug 2027988] Re: qla2xxx driver fails all paths
** Attachment added: "lspci output for the mezzanine card"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+attachment/5686846/+files/lspci-output-host2
--
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/2027988
Title:
qla2xxx driver fails all paths
Status in linux-signed-hwe-5.19 package in Ubuntu:
New
Bug description:
After upgrading an HP BL460 G7 from 20.04 to 22.04, the storage mounted from
an hp msa2324fc using the QLogic QMH2462 dual channel adapter fails all paths
after a while, usually less than an hour.
This occured with kernel 5.15.0-76-generic installed by upgrading, but gave
5.19.0-46-generic a shot hoping to be bug free.
In the same blade enclosure are other server blades connected to the same
storage via the same switches
with ubuntu 16.04 18.04 20.04 which operate as intended plus a couple more
non-blade servers.
When the issue occurs all cpu goes to 100 iowait, load average keeps climbing
up until i do
echo 1 > /sys/class/fc_host/host2/issue_lip ( and host3 ) and flush the
multipath device after using umount ( if mounted ) because it gets stuck
without even mounting it.
I verified multipathd.conf configuration if correct.
=== multipath.conf ===
blacklist {
devnode "^sda"
}
defaults {
polling_interval 5
fast_io_fail_tmo 5
dev_loss_tmo 10
checker_timeout 15
}
devices {
device {
vendor "HP"
product "MSA2312fc|MSA2324fc"
hardware_handler "0"
uid_attribute ID_SERIAL
path_selector "round-robin 0"
path_grouping_policy group_by_prio
failbackimmediate
rr_weight uniform
no_path_retry 18
rr_min_io 100
path_checkertur
prioalua
}
}
multipaths {
multipath {
wwid3600c0ff000daa122bf012d500100
alias wtsql
path_grouping_policygroup_by_prio
}
}
=== end multipath.conf ===
qla2xxx module parameters: "ql2xmaxqdepth=16 qlport_down_retry=10
ql2xloginretrycount=30 ql2xextended_error_logging=0x1e40"
lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
apt-cache policy linux-generic-hwe-22.04
linux-generic-hwe-22.04:
Installed: 5.19.0.46.47~22.04.21
Candidate: 5.19.0.46.47~22.04.21
Version table:
*** 5.19.0.46.47~22.04.21 500
500 http://gr.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0.25.27 500
500 http://gr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jul 17 16:40:10 2023
SourcePackage: linux-signed-hwe-5.19
UpgradeStatus: Upgraded to jammy on 2023-07-12 (5 days ago)
mtime.conffile..etc.logrotate.d.apport: 2017-08-03T08:14:27.712298
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+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 2027988] Re: qla2xxx driver fails all paths
** Attachment added: "multipath -ll -v3 when OK"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+attachment/5686845/+files/multipath-ll-v3
--
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/2027988
Title:
qla2xxx driver fails all paths
Status in linux-signed-hwe-5.19 package in Ubuntu:
New
Bug description:
After upgrading an HP BL460 G7 from 20.04 to 22.04, the storage mounted from
an hp msa2324fc using the QLogic QMH2462 dual channel adapter fails all paths
after a while, usually less than an hour.
This occured with kernel 5.15.0-76-generic installed by upgrading, but gave
5.19.0-46-generic a shot hoping to be bug free.
In the same blade enclosure are other server blades connected to the same
storage via the same switches
with ubuntu 16.04 18.04 20.04 which operate as intended plus a couple more
non-blade servers.
When the issue occurs all cpu goes to 100 iowait, load average keeps climbing
up until i do
echo 1 > /sys/class/fc_host/host2/issue_lip ( and host3 ) and flush the
multipath device after using umount ( if mounted ) because it gets stuck
without even mounting it.
I verified multipathd.conf configuration if correct.
=== multipath.conf ===
blacklist {
devnode "^sda"
}
defaults {
polling_interval 5
fast_io_fail_tmo 5
dev_loss_tmo 10
checker_timeout 15
}
devices {
device {
vendor "HP"
product "MSA2312fc|MSA2324fc"
hardware_handler "0"
uid_attribute ID_SERIAL
path_selector "round-robin 0"
path_grouping_policy group_by_prio
failbackimmediate
rr_weight uniform
no_path_retry 18
rr_min_io 100
path_checkertur
prioalua
}
}
multipaths {
multipath {
wwid3600c0ff000daa122bf012d500100
alias wtsql
path_grouping_policygroup_by_prio
}
}
=== end multipath.conf ===
qla2xxx module parameters: "ql2xmaxqdepth=16 qlport_down_retry=10
ql2xloginretrycount=30 ql2xextended_error_logging=0x1e40"
lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
apt-cache policy linux-generic-hwe-22.04
linux-generic-hwe-22.04:
Installed: 5.19.0.46.47~22.04.21
Candidate: 5.19.0.46.47~22.04.21
Version table:
*** 5.19.0.46.47~22.04.21 500
500 http://gr.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0.25.27 500
500 http://gr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jul 17 16:40:10 2023
SourcePackage: linux-signed-hwe-5.19
UpgradeStatus: Upgraded to jammy on 2023-07-12 (5 days ago)
mtime.conffile..etc.logrotate.d.apport: 2017-08-03T08:14:27.712298
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+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 2027988] Re: qla2xxx driver fails all paths
When all paths are fails multipath -ll or any other command that
accesses those disks ( fdisk , hdparm ) hangs indefinitely until echo 1
> issue_lip is issued
dmesg output after the issue_lip is attached as well
** Attachment added: "dmesg output after issue_lip"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+attachment/5686847/+files/dmesg-after-lip.txt
--
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/2027988
Title:
qla2xxx driver fails all paths
Status in linux-signed-hwe-5.19 package in Ubuntu:
New
Bug description:
After upgrading an HP BL460 G7 from 20.04 to 22.04, the storage mounted from
an hp msa2324fc using the QLogic QMH2462 dual channel adapter fails all paths
after a while, usually less than an hour.
This occured with kernel 5.15.0-76-generic installed by upgrading, but gave
5.19.0-46-generic a shot hoping to be bug free.
In the same blade enclosure are other server blades connected to the same
storage via the same switches
with ubuntu 16.04 18.04 20.04 which operate as intended plus a couple more
non-blade servers.
When the issue occurs all cpu goes to 100 iowait, load average keeps climbing
up until i do
echo 1 > /sys/class/fc_host/host2/issue_lip ( and host3 ) and flush the
multipath device after using umount ( if mounted ) because it gets stuck
without even mounting it.
I verified multipathd.conf configuration if correct.
=== multipath.conf ===
blacklist {
devnode "^sda"
}
defaults {
polling_interval 5
fast_io_fail_tmo 5
dev_loss_tmo 10
checker_timeout 15
}
devices {
device {
vendor "HP"
product "MSA2312fc|MSA2324fc"
hardware_handler "0"
uid_attribute ID_SERIAL
path_selector "round-robin 0"
path_grouping_policy group_by_prio
failbackimmediate
rr_weight uniform
no_path_retry 18
rr_min_io 100
path_checkertur
prioalua
}
}
multipaths {
multipath {
wwid3600c0ff000daa122bf012d500100
alias wtsql
path_grouping_policygroup_by_prio
}
}
=== end multipath.conf ===
qla2xxx module parameters: "ql2xmaxqdepth=16 qlport_down_retry=10
ql2xloginretrycount=30 ql2xextended_error_logging=0x1e40"
lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
apt-cache policy linux-generic-hwe-22.04
linux-generic-hwe-22.04:
Installed: 5.19.0.46.47~22.04.21
Candidate: 5.19.0.46.47~22.04.21
Version table:
*** 5.19.0.46.47~22.04.21 500
500 http://gr.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0.25.27 500
500 http://gr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jul 17 16:40:10 2023
SourcePackage: linux-signed-hwe-5.19
UpgradeStatus: Upgraded to jammy on 2023-07-12 (5 days ago)
mtime.conffile..etc.logrotate.d.apport: 2017-08-03T08:14:27.712298
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+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 1964916] Re: [HP Omni 120-2110il AIO] Flickering white lines on screen
Attached video of HP Omni 120 Flickering, I tested with kernel 6.0, 6.1, 6.2 (compiled by my self using drm-tip branch), and 6.2 from 23.04, now testing 6.3, same issue, the only workaround is "nomodeset i915.modeset=0" ** Attachment added: "HP Omni 120 Flickering" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1964916/+attachment/5686848/+files/VID20230717090856.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1964916 Title: [HP Omni 120-2110il AIO] Flickering white lines on screen Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: https://www.youtube.com/watch?v=GcAXAicoZqY this is the video of my error i am having this issue on all versions of ubuntu-- i have tried installing versions 20.04, 18.04.06, 12.04.. i have intel pentium g630 processor with intel graphics 2000 (Vram-256M). I used Windows 10 on my PC but i thought of switching to ubuntu when this problem arose.. The glitch shows up on ubuntu splash screen and remains there until i restart my pc with nomodeset parameter...i have reinstalled windows 10 but i want this issue to get fixed.. i need to use ubuntu ...pls ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 14:59:57 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2022-03-05 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Hewlett-Packard 120-2110il ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=54d1c05e-a544-4510-8da7-87e1a7242e0f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 101 dmi.chassis.asset.tag: 4CS2040B0F dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-2110il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-2110il dmi.product.sku: QF135AA#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1964916/+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 2022387] Re: mlxbf-gige: Fix intermittent no ip issue
** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2022387 Title: mlxbf-gige: Fix intermittent no ip issue Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] Although the link is up, and the PHY interrupt is cleared, there is no ip assigned. Nothing is being transmitted, and nothing is received. The RX error count keeps on increasing (check ifconfig oob_net0). After several minutes, the RX error count stagnates and the oob finally gets an ip and is pingable. [Fix] The issue is in the mlxbf_gige_rx_init function. As soon as the RX DMA is enabled, the RX CI reaches the max 128, it becomes equal to RX PI. And RX CI doesn't decrease since the code hasn't ran phy_start yet. The solution is to move the rx init after phy_start. [Test Case] * Check if the gige driver is loaded * Check that the oob_net0 interface is up and pingable from an external host * Do at ~1000 resets and powercycles and check the oon_net0 interface again [Regression Potential] * No known regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2022387/+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 2016039] Re: mlxbf-tmfifo: fix potential race
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2016039 Title: mlxbf-tmfifo: fix potential race Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+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 2013383] Re: mlxbf-bootctl: support SMC call for setting ARM boot state
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2013383 Title: mlxbf-bootctl: support SMC call for setting ARM boot state Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Add a new SMC call which allows setting the ARM boot progress state to "OS is up". [Fix] * Add a new SMC call in mlxbf-bootctl which allows setting the ARM boot progress state to "OS is up". [Test Case] * Check that /sys/devices/platform/MLNXBF04:00/driver/os_up exists [Regression Potential] * No known regression because it is just adding a sysfs entry. It is backward compatible with older TAF images. If the SMC call is not supported by ATF, it is ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013383/+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 2027996] [NEW] vulkaninfo fails with libnvidia-gl-535 under Wayland
Public bug reported: vulkaninfo under Wayland fails with: WARNING: [Loader Message] Code 0 : loader_parse_icd_manifest: Can not find 'ICD' object in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json. Skipping ICD JSON ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR failed with ERROR_INITIALIZATION_FAILED Removing nvidia_layers.json gets rid of the warning but not the error: ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR failed with ERROR_INITIALIZATION_FAILED ** Affects: ubuntu Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2027996 Title: vulkaninfo fails with libnvidia-gl-535 under Wayland Status in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: vulkaninfo under Wayland fails with: WARNING: [Loader Message] Code 0 : loader_parse_icd_manifest: Can not find 'ICD' object in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json. Skipping ICD JSON ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR failed with ERROR_INITIALIZATION_FAILED Removing nvidia_layers.json gets rid of the warning but not the error: ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR failed with ERROR_INITIALIZATION_FAILED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2027996/+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 2006797] Re: MT7922 firmware not working
Has this worked with older (<5.19) kernel, i.e., is it a regression? -- 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/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 8.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0823 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B650-A GAMING WIFI 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.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006797/+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 2006797] Re: MT7922 firmware not working
You could try newest mainline kernels from [1] to see if that makes it any better. Note that these are not supported and only for testing and you need to disable Secure Boot. [1] https://kernel.ubuntu.com/~juergh/dashboard.html -- 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/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 8.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0823 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B650-A GAMING WIFI 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.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006797/+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 2024479] Re: kdump fails on big arm64 systems when offset is not specified
For documentation purposes: the riscv64 build fails on jammy/lunar-proposed, which is not a regression; that is since/on the jammy/lunar-release pockets. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Committed Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. - Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. - Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. kexec-tools - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that the reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 ar
[Kernel-packages] [Bug 1553750] Re: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
*** This bug is a duplicate of bug 1532355 *** https://bugs.launchpad.net/bugs/1532355 ** This bug is no longer a duplicate of bug 1547505 package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth ** This bug has been marked a duplicate of bug 1532355 package linux-image-4.3.0-5-generic 4.3.0-5.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1553750 Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in linux-meta package in Ubuntu: New Bug description: upgrading from 15.10 with latest update software ( after do a apt-get update && sudo apt-get upgrade). I got 5 or more errors in sequence. I'll try to install manually other kernel. probably same bug as: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553744 and https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553749 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.10.11 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zhe1403 F pulseaudio /dev/snd/controlC0: zhe1403 F pulseaudio /dev/snd/controlC2: zhe1403 F pulseaudio Date: Sun Mar 6 12:37:12 2016 ErrorMessage: dependency problems - leaving unconfigured HibernationDevice: RESUME=UUID=614b6ea9-83ad-4c8a-a581-03bcf289e06e InstallationDate: Installed on 2016-03-06 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7900 ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=d8cd991e-7ac6-4097-b3cc-775150407e05 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-meta Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago) dmi.bios.date: 01/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-G45 GAMING (MS-7900) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd01/12/2016:svnMSI:pnMS-7900:pvr1.0:rvnMSI:rnA88X-G45GAMING(MS-7900):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7900 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1553750/+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 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT
** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- 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/2018591 Title: Enable Tracing Configs for OSNOISE and TIMERLAT Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: In Progress Bug description: == SRU Justification == These config changes will allow tracing with the OSNOISE and TIMERLAT tracing tools. These tracers can be enabled at run-time and should not affect performance or add any additional overhead. == Fix == UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs == Regression Potential == Low. These config changes will just allow the use of tracing tools. == Test Case == Test build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018591/+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 1879077] Re: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: casper (Ubuntu) Status: New => Confirmed -- 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/1879077 Title: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in casper package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Invalid Bug description: when I am trying to upgrade to 16.04 from 14 , i am getting below error Cmd : lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 What I expected to happen -- Ubuntu upgrades to 16.04 with upgraded kernel 4.4 What happened instead : it upgraded to 16.04 but with old kernel only and my sound has stopped Setting up initramfs-tools (0.122ubuntu8.16) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.157.23) ... update-initramfs: Generating /boot/initrd.img-3.13.0-38-generic E: amd64-microcode: unsupported kernel version! E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-38-generic with 1. dpkg: error processing package linux-firmware (--configure): subprocess installed post-installation script returned error exit status 1 Setting up linux-image-4.4.0-178-generic (4.4.0-178.208) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-firmware; however: Package linux-firmware is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 4.4.0.178.186); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.122ubuntu8.16) ... update-initramfs: Generating /boot/initrd.img-3.13.0-38-generic E: amd64-microcode: unsupported kernel version! E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-38-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already Processing triggers for linux-image-4.4.0-178-generic (4.4.0-178.208) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 4.4.0-178-generic Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.4.0-178-generic E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-178-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-4.4.0-178-generic (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-firmware linux-image-generic linux-generic initramfs-tools linux-image-4.4.0-178-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.23 ProcVersionSignature: Ubuntu 3.13.0-38.65somerville1-generic 3.13.11.9 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Sat May 16 21:00:04 2020 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
Anthony, I have no preference about 1 vs 2, I only ask that the bug (and therefore the SRU verification process) be consistent with the upload. -- 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/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Incomplete Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
"@Andreas firmware-sof in Mantic is 2.2.6, which already has everything in Acelan's merge proposal." ** Changed in: firmware-sof (Ubuntu Mantic) Status: New => Fix Released -- 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/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Incomplete Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2026590] Re: Azure: SMB3: Add missing locks to protect deferred close file list
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** 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/2026590 Title: Azure: SMB3: Add missing locks to protect deferred close file list Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] The deferred closed list in SMB3 could get corrupted [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab9ddc87a9055c4bebd6524d5d761d605d52e557 [Regression Potential] Possible lockup due to nested locks (though quite unlikely) [Other Info] SF: #00363737 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2026590/+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 2006716] Re: 5 failures reported in net:fcnal-test.sh on Jammy
** Tags added: sru-s20230612 -- 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/2006716 Title: 5 failures reported in net:fcnal-test.sh on Jammy Status in ubuntu-kernel-tests: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: New Bug description: This is not a regression, but something covered by bug 2006692 There are 5 sub-test failures reported in this test on Jammy: # Tests passed: 857 # Tests failed: 5 # 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] We might see failure came up in F/K after bug 2006391 being fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006716/+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 2026736] Re: Azure: Fix lockup in swiotlb when used as a CVM
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/2026736 Title: Azure: Fix lockup in swiotlb when used as a CVM Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] Azxure CVM instances can lock up when run under stress. [Test Plan] MSFT tested using the nttcp test. [Regression potential] CVM instances could continue to lock up under stress. [Other info] SF: #00363432 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026736/+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 2028011] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-nvidia-tools-common 5
Public bug reported: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: linux-tools-5.15.0-76 linux-tools-5.15.0-76-generic linux-tools-common The following NEW packages will be installed: linux-tools-5.15.0-76 linux-tools-5.15.0-76-generic linux-tools-common linux-tools-generic 0 upgraded, 4 newly installed, 0 to remove and 2 not upgraded. Need to get 8.218 kB of archives. After this operation, 28,2 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-common all 5.15.0-76.83 [276 kB] Get:2 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-5.15.0-76 amd64 5.15.0-76.83 [7.938 kB] Get:3 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-5.15.0-76-generic amd64 5.15.0-76.83 [1.792 B] Get:4 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-generic amd64 5.15.0.76.74 [2.346 B] Fetched 8.218 kB in 8s (969 kB/s) Selecting previously unselected package linux-tools-common. (Reading database ... 232466 files and directories currently installed.) Preparing to unpack .../linux-tools-common_5.15.0-76.83_all.deb ... Unpacking linux-tools-common (5.15.0-76.83) ... dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0-76.83_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-nvidia-tools-common 5.15.0-1028.28 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package linux-tools-5.15.0-76. Preparing to unpack .../linux-tools-5.15.0-76_5.15.0-76.83_amd64.deb ... Unpacking linux-tools-5.15.0-76 (5.15.0-76.83) ... Selecting previously unselected package linux-tools-5.15.0-76-generic. Preparing to unpack .../linux-tools-5.15.0-76-generic_5.15.0-76.83_amd64.deb ... Unpacking linux-tools-5.15.0-76-generic (5.15.0-76.83) ... Selecting previously unselected package linux-tools-generic. Preparing to unpack .../linux-tools-generic_5.15.0.76.74_amd64.deb ... Unpacking linux-tools-generic (5.15.0.76.74) ... Errors were encountered while processing: /var/cache/apt/archives/linux-tools-common_5.15.0-76.83_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.15.0-76:amd64: Install linux-tools-5.15.0-76-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: zouz 2112 F pulseaudio /dev/snd/controlC0: zouz 2112 F pulseaudio /dev/snd/controlC1: zouz 2112 F pulseaudio /dev/snd/controlC2: zouz 2112 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Jul 17 21:46:35 2023 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.15.0-76.83_all.deb ... Unpacking linux-tools-common (5.15.0-76.83) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0-76.83_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-nvidia-tools-common 5.15.0-1028.28 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-nvidia-tools-common 5.15.0-1028.28 InstallationDate: Installed on 2023-07-17 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: FUJITSU CELSIUS H760 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=9dd92be4-7fc8-482c-83ad-ee2a984ca2da ro quiet splash vt.handoff=7 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 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-nvidia-tools-common 5.15.0-1028.28 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/
[Kernel-packages] [Bug 2028014] [NEW] package nvidia-firmware-535-535.54.03 (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also
Public bug reported: error trying to update latest driver ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-firmware-535-535.54.03 (not installed) ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 17 22:20:56 2023 ErrorMessage: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-firmware-535-server-535.54.03 535.54.03-0ubuntu0.20.04.1 InstallationDate: Installed on 2023-07-17 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-firmware-535-535.54.03 (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-firmware-535-server-535.54.03 535.54.03-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2028014 Title: package nvidia-firmware-535-535.54.03 (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-firmware-535-server-535.54.03 535.54.03-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: error trying to update latest driver ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-firmware-535-535.54.03 (not installed) ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 17 22:20:56 2023 ErrorMessage: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-firmware-535-server-535.54.03 535.54.03-0ubuntu0.20.04.1 InstallationDate: Installed on 2023-07-17 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-firmware-535-535.54.03 (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-firmware-535-server-535.54.03 535.54.03-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2028014/+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 2006716] Re: 5 failures reported in net:fcnal-test.sh on Jammy
This affects jammy:linux-oracle-5.15-1040.46 for the 2023.07.10 cycle ** Tags added: sru-20230710 -- 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/2006716 Title: 5 failures reported in net:fcnal-test.sh on Jammy Status in ubuntu-kernel-tests: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: New Bug description: This is not a regression, but something covered by bug 2006692 There are 5 sub-test failures reported in this test on Jammy: # Tests passed: 857 # Tests failed: 5 # 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] We might see failure came up in F/K after bug 2006391 being fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006716/+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 1931390] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed after successful CPU1 offline
This affects jammy:linux-oracle-5.15-1040.46 for the 2023.07.10 cycle The issue is a bit flaky, fails maybe 1/5 times. ** Tags added: sru-20230710 -- 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/1931390 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed after successful CPU1 offline Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: In cpuhotplug (ubuntu_ltp) tests, offline and online of CPU1 succeeds, but later the test fails with: utils:0153| [stdout] Name: cpuhotplug03 utils:0153| [stdout] Date: Wed Jun 9 03:52:16 UTC 2021 utils:0153| [stdout] Desc: Do tasks get scheduled to a newly on-lined CPU? utils:0153| [stdout] utils:0153| [stdout] CPU is 1 utils:0153| [stdout] USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND utils:0153| [stdout] root 858611 0.0 0.0 2616 540 ? R 03:52 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop ... ... ... utils:0153| [stdout] 49 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop utils:0153| [stdout] 82 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop utils:0153| [stdout] 18 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop utils:0153| [stdout] cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1 utils:0153| [stdout] tag=cpuhotplug03 stime=1623210736 dur=3 exit=exited stat=1 core=no cu=22260 cs=78 IMPORTANT: The CPU1 got properly offlined and onlined. For failures of CPU1 offline, please see lp:1836167 (reported previously as part of lp:1836167). Po-Hsu Lin (cypressyew) wrote on 2020-09-25: On F-oem-5.6 with node glameow: cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1 Kelsey Skunberg (kelsey-skunberg) wrote on 2020-10-06: spotted on Focal aws : 5.4.0-1026.26 : amd64 cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1 Po-Hsu Lin (cypressyew) wrote on 2021-06-09: Found on 5.11.0-1005.5 - intel Node spitfire, passed on node bavor. cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931390/+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 1522327] Re: package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 1522501 package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- 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/1522327 Title: package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: cd/dvd player dont read the discs device its working properly ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-71-generic 3.13.0-71.114 ProcVersionSignature: Ubuntu 3.13.0-64.104-generic 3.13.11-ckt26 Uname: Linux 3.13.0-64-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoe1670 F pulseaudio /dev/snd/seq:timidity 1284 F timidity Date: Thu Dec 3 10:44:45 2015 DuplicateSignature: package:linux-image-3.13.0-71-generic:3.13.0-71.114:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=8685940b-7d7e-4e26-a120-317e39c21913 InstallationDate: Installed on 2015-08-08 (116 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Hewlett-Packard HP Compaq dx6120 MT(EP691ES) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.5 SourcePackage: linux Title: package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/05/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786C2 v01.06 dmi.board.name: 09CCh dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC6120B30 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786C2v01.06:bd04/05/2005:svnHewlett-Packard:pnHPCompaqdx6120MT(EP691ES):pvr:rvnHewlett-Packard:rn09CCh:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dx6120 MT(EP691ES) dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522327/+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 2019971] Re: Add EPYC-Genoa model
As far as I have researched, the Linux patches pointed by Markus haven't been backported to any of our kernels yet. As such, I am adding a Linux task to this bug so that the kernel team can chime in and provide some feedback as to whether these patches will be backported. @Kernel team, could you please take a look and let us know? TIA. ** 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/2019971 Title: Add EPYC-Genoa model Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Triaged Status in linux source package in Jammy: New Status in qemu source package in Jammy: Triaged Status in linux source package in Kinetic: New Status in qemu source package in Kinetic: Triaged Status in linux source package in Lunar: New Status in qemu source package in Lunar: Triaged Status in linux source package in Mantic: New Status in qemu source package in Mantic: Triaged Bug description: [Impact] * To avoid bugs with newer Hardware and to allow users/admins to control the KVM guests correctly we usually try to backport major CPU- detect/control features back to at least the last LTS (currently jammy) In SRU Terms this is under the second entry in https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases * In this particular case it is about Support for EPYC Genoa chips https://en.wikipedia.org/wiki/Epyc#Fourth_generation_Epyc_(Genoa) [Test Plan] * First of all we'll (and have in advance) run general regression tests * Second you'd want to run this with host-model and host-passthrough on Rome / Milan chips to ensure no case is now falling in to a totally dysfunctional state * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Genoa x86 EPYC-Genoa (alias configured by machine type) x86 EPYC-Genoa-v1 AMD EPYC-Genoa Processor * Finally migrations between old->new should be checked to work fine. [Where problems could occur] * This kind of "add the new type" usually only s a problem in backward- migratebility which isn't supported anyway. Never the less the areas to look out for is behavior on various AMD EPYC chips. To ensure that old chips won't change in a breaking way (they might detect new features now, but not more) and that new Milan chips are now all detected properly. [Other Info] * This is not the first time new AMD chips need to add their definitions, for example bug 1921880 was similar QEMU added a separate model for EPYC-Genoa in https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02087.html On the qemu side most bits are already present as far back as jammy. The only things missing are the vnmi and auto-ibrs flag. The lfence-always-serializing, amd-psfd, no-nested-data-bp, null-sel-clr-base are part of the Milan-v2 patch set https://github.com/qemu/qemu/commit/62a798d4bc2c3e767d94670776c77a7df274d7c5.patch https://github.com/qemu/qemu/commit/166b1741884dd4fd7090b753cd7333868457a29b.patch Kernel auto-ibrs et al: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch x86/cpu: Support AMD Automatic IBRS https://github.com/torvalds/linux/commit/e7862eda309ecfccc36bb5558d937ed3ace07f3f.patch KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch Add support for virtual NMIs https://github.com/torvalds/linux/commit/4a5fd419952e49ef870e9259d815718062871cc1.patch Please consider adding/backporting these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019971/+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 2019968] Re: Add missing feature bits in EPYC-Milan model
As far as I have researched, the Linux patches pointed by Markus haven't been backported to any of our kernels yet. As such, I am adding a Linux task to this bug so that the kernel team can chime in and provide some feedback as to whether these patches will be backported. @Kernel team, could you please take a look and let us know? TIA. ** 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/2019968 Title: Add missing feature bits in EPYC-Milan model Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: New Status in linux source package in Jammy: New Status in qemu source package in Jammy: New Status in linux source package in Kinetic: New Status in qemu source package in Kinetic: New Status in linux source package in Lunar: New Status in qemu source package in Lunar: New Status in linux source package in Mantic: New Status in qemu source package in Mantic: New Bug description: [Impact] Add the following feature bits for EPYC-Milan model and bump the version. vaes: Vector VAES(ENC|DEC), VAES(ENC|DEC)LAST instruction support vpclmulqdq : Vector VPCLMULQDQ instruction support stibp-always-on : Single Thread Indirect Branch Prediction Mode has enhanced performance and may be left Always on amd-psfd: Predictive Store Forward Disable no-nested-data-bp : Processor ignores nested data breakpoints lfence-always-serializing : LFENCE instruction is always serializing null-sel-clr-base : Null Selector Clears Base. When this bit is set, a null segment load clears the segment base [Test Plan] * First of all we'll (and have in advance) run general regression tests * Qemu shall show to be aware of the new types # qemu-system-x86_64 -cpu ? | grep EPYC-Milan x86 EPYC-Milan (alias configured by machine type) x86 EPYC-Milan-v1 AMD EPYC-Milan Processor x86 EPYC-Milan-v2 AMD EPYC-Milan Processor [Where problems could occur] * There are two areas to look at a) compat behavior on old systems - e.g. libvirt would now detect IBRS on such AMD chips and one might wonder about the change. E.g. compatibility would exist between old-code/new-code/old->new code; but any action (e.g. suspend resume) from new to old code might run into trouble (not supported that way but worth to mention for awareness) b) Migrations between systems - this should be covered by chip versioning but still is worth to mention. Versioning will recognize a formerly started system as v1 and continue to handle it that way. Only new started guests would become v2 and behave the new and improved way. [Other Info] * n/a --- https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02082.html https://github.com/qemu/qemu/commit/27f03be6f59d04bd5673ba1e1628b2b490f9a9ff.patch This patch depends on the definitions that were added as part of the EPYC-Milan patch: amd-psfd, stibp-always-on: * https://github.com/qemu/qemu/commit/bb039a230e6a7920d71d21fa9afee2653a678c48.patch Add feature bits for CPUID_Fn8021_EAX: * https://github.com/qemu/qemu/commit/b70eec312b185197d639bff689007727e596afd1.patch Kernel patches: https://lkml.kernel.org/lkml/20230124163319.2277355-1-kim.phill...@amd.com/ kvm: Add support for CPUID_8021_EAX * https://github.com/torvalds/linux/commit/8415a74852d7c24795007ee9862d25feb519007c.patch kvm: Add the NO_NESTED_DATA_BP feature * https://github.com/torvalds/linux/commit/a9dc9ec5a1fafc3d2fe7a7b594eefaeaccf89a6b.patch kvm: Move X86_FEATURE_LFENCE_RDTSC to its native leaf * https://github.com/torvalds/linux/commit/84168ae786f8a15a7eb0f79d34f20b8d261ce2f5.patch kvm: Add the Null Selector Clears Base feature * https://github.com/torvalds/linux/commit/5b909d4ae59aedc711b7a432da021be0e82c95a0.patch kvm: Add the SMM_CTL MSR not present feature https://github.com/torvalds/linux/commit/faabfcb194a8d0686396e3fff6a5b42911f65191.patch And probably this one as well: KVM: Add common feature flag for AMD's PSFD https://github.com/torvalds/linux/commit/3d8f61bf8bcd69bcd397276d53aa18f7ca8347f9.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019968/+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 2025120] Re: Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting, while 6.2.0-21 always works
Sounds like a kernel bisection is needed? -- 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/2025120 Title: Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting, while 6.2.0-21 always works Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+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 2025120] Re: Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting, while 6.2.0-21 always works
Yes it's on my todo list. -- 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/2025120 Title: Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting, while 6.2.0-21 always works Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
I've updated the bug description for firmware-sof SRU, and provide the link to where the firmare is from. ** Description changed: + SRU Jusitification for firmware-sof + + [Impact] + To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 + + [Fix] + Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too + + [Test Case] + The new firmware has been verified by our SWE team. + + [Where problems could occur] + Those are new firmware, so it's not possible to introduce any regressions. + + [Misc] + https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 + https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 + + + [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. -- 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/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Incomplete Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] The new firmware has been verified by our SWE team. [Where problems could occur] Those are new firmware, so it's not possible to introduce any regressions. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2027959] Re: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33
@Mario, thank you. -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: Fix Released Bug description: Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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 2020141] Re: Ubuntu 22.04 Screen Flickering Left Hand of the screen
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2020141 Title: Ubuntu 22.04 Screen Flickering Left Hand of the screen Status in linux package in Ubuntu: Expired Bug description: Machine: Hardware Model: Lenovo IdeaPad 5 Pro 14iTL6 16gb RAM 1TB SSD Graphics: Mesa Intel XE Graphics (TGL GT2) (Intel IRIS XE Graphics) OS: Ubuntu 22.04 64-bit Wayland Gnome Version: 42.5 Kernel Version: 5.19.0.-41-generic Bug Description: Just bought a laptop and installed Ubuntu 22.04. The screen flickering happens on left-hand side of the screen whenever I'm typing, scrolling or coding. Or while something is loading. It doesn't happen if it's idle or just watching videos. Hope someone can help me as it affect my productivity and it's very annoying given that I just bought this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020141/+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 2019152] Re: [btintel] Bluetooth crashes in Ubuntu 23.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2019152 Title: [btintel] Bluetooth crashes in Ubuntu 23.04 Status in linux package in Ubuntu: Expired Bug description: Bluetooth stops working. Mouse (logitech M720) stopped mid scroll. Never had any problems with this mouse under Ubuntu before. Workaround: Reboot fixes the problem. Switching in and out of airplane mode gets bluetooth working again Frequency: Second time this has happened since upgrade from 22.10 (about 2 weeks ago) Limited knowledge fault tracing: >sudo systemctl restart bluetooth doesn't make any difference >rfkill shows no bluetooth device >lspci ... 3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) ... Ubuntu settings - show bluetooth is off, but I didn't disable it and it can't be re-enabled. So I assume the driver has crashed, but I don't know how to find out more about this. Could collect some more info next time it happens if someone tells me what to do. >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019152/+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 2028027] [NEW] package nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', wh
Public bug reported: While trying to `sudo apt upgrade`, the following error shows up: Errors were encountered while processing: /tmp/apt-dpkg-install-E3zKrf/01-libnvidia-gl-535_535.54.03-0ubuntu0.22.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-firmware-535-535.54.03:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jul 18 09:49:01 2023 Dependencies: DpkgTerminalLog: Preparing to unpack .../nvidia-firmware-535-535.54.03_535.54.03-0ubuntu0.22.04.1_amd64.deb ... Unpacking nvidia-firmware-535-535.54.03 (535.54.03-0ubuntu0.22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/nvidia-firmware-535-535.54.03_535.54.03-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu22.04.1 ErrorMessage: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu22.04.1 InstallationDate: Installed on 2023-06-12 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu22.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2028027 Title: package nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu22.04.1 Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: While trying to `sudo apt upgrade`, the following error shows up: Errors were encountered while processing: /tmp/apt-dpkg-install-E3zKrf/01-libnvidia-gl-535_535.54.03-0ubuntu0.22.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-firmware-535-535.54.03:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jul 18 09:49:01 2023 Dependencies: DpkgTerminalLog: Preparing to unpack .../nvidia-firmware-535-535.54.03_535.54.03-0ubuntu0.22.04.1_amd64.deb ... Unpacking nvidia-firmware-535-535.54.03 (535.54.03-0ubuntu0.22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/nvidia-firmware-535-535.54.03_535.54.03-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu22.04.1 ErrorMessage: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu22.04.1 InstallationDate: Installed on 2023-06-12 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/lib/firmware/nvidia/535.54.03/gsp_ga10x.bin', which is also in package nvidia-kernel-common-535 535.54.03-0ubuntu0~gpu22.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2028027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscr
[Kernel-packages] [Bug 1975592] Autopkgtest regression report (linux-meta-riscv/6.2.0.27.28.1)
All autopkgtests for the newly accepted linux-meta-riscv (6.2.0.27.28.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/unknown (amd64) cryptsetup/unknown (ppc64el, s390x) ipmitool/unknown (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/lunar/update_excuses.html#linux-meta-riscv [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-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1975592 Title: Enable Nezha board Status in linux-allwinner package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Bug description: [Impact] integrate linux-allwinner patches into linux-riscv kernel [Test] * Newly built images should boot and work on both nezha and licheerv * Upgraded systems using old images should reboot and work on both nezha and licheerv * livecd-rootfs must continue to install linux-allwinner when building for nezha and licheerv [Implementation details] * linux[-image]-allwinner depends on new enough generic kernel with allwinner support pull request applied; and contains additional initramfs configuration to ensure booting is possible [Regression potential] Ensure this new build of linux-riscv doesn't regress on existing supported systems (sifive & qemu) scope: linux-riscv https://lists.ubuntu.com/archives/kernel-team/2023-May/139655.html u-boot-nezha patch attached linux-meta-riscv patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/1975592/+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 2027959] Re: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33
SRU: * https://lists.ubuntu.com/archives/kernel-team/2023-July/141148.html (jammy) * https://lists.ubuntu.com/archives/kernel-team/2023-July/141149.html (lunar) ** Description changed: + [SRU Justification] + + [Impact] + + Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms + will sometimes fail to wake from S3. + + This is a follow-up to bug 2024427 to patch additional models. + + [Fix] + + firmware patches: + * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release + * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release + * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 + + [Test Case] + + $ checkbox-cli run com.canonical.certification::stress- + suspend-30-cycles-with-reboots-automated + + [Where problems could occur] + + Little we know about the firmware fixes. However, while with these commits have + been pulled via stable kernel fixes, the driver begins to request new firmware + blobs of a different filename. + + [Other Info] + + For the firmware parts, they have been included in linux-firmware/mantic, + leaving only linux-firmware/lunar and linux-firmware/jammy to be fixed. + + == original bug report == + Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. This is a follow-up to bug 2024427 to patch additional models. [Fix] firmware patches: * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] For the firmware parts, they have been included in linux-firmware/mantic, leaving only linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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
