[Kernel-packages] [Bug 2054218] [NEW] kvm: Running perf against qemu processes results in page fault inside guest
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/2054218 [Impact] Running perf against a QEMU/kvm process results in the guest suffering a page fault in trying to store Precise Event Based Sampling (PEBS) records for the host. This affects both using perf against a single process, in which it crashes the targeted guest, or using perf system wide, in which it crashes all running guests on the system. The issue was introduced in 6.0 by: commit c59a1f106f5cd4843c097069ff1bb2ad72103a67 Author: Like Xu Date: Mon Apr 11 18:19:36 2022 +0800 Subject: KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c59a1f106f5cd4843c097069ff1bb2ad72103a67 This affects all 6.2 and 6.5 kernels. There is no known workaround, apart from not using perf on affected systems. [Fix] The issue was fixed in 6.7 by: commit 971079464001c6856186ca137778e534d983174a Author: Paolo Bonzini Date: Thu Jan 4 16:15:17 2024 +0100 Subject: KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=971079464001c6856186ca137778e534d983174a This reinstates the logic for setting MSR_CORE_PERF_GLOBAL_CTRL to what it was before "KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS". - .guest = intel_ctrl & (~cpuc->intel_ctrl_host_mask | ~pebs_mask), + .guest = intel_ctrl & ~cpuc->intel_ctrl_host_mask & ~pebs_mask, The faulty logic includes any bit that isn't both marked as exclude_guest and using PEBS, while it should really be excluding PEBS from the host. [Testcase] Start a bare metal server. Enable KVM, start a few VMs. The VMs can be idle, they don't require any workload. $ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils uvtool $ sudo reboot $ ssh-keygen $ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-b release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-c release=jammy arch=amd64 $ virsh list Id Name State - 2jammy-a running 3jammy-b running 4jammy-c running $ uvt-kvm ssh jammy-a Check it works. $ ps aux | grep qemu Find the pid of jammy-a $ perf top -p $PID $ virsh console jammy-a Escape character is ^] (Ctrl + ]) [ 357.793039] BUG: unable to handle page fault for address: fe49178c6028 $ uvt-kvm ssh jammy-a (no response) Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf379502-test If you install it, then running perf against the PID of qemu processes will no longer crash the guest, and they will be accessible by SSH afterward. [Where problems could occur] We are rearranging the logic of setting the PEBS MSRs, which affects processor sampling of events. This will affect any profiling tools running against KVM based virtual machines, namely perf against QEMU. If a regression were to occur, running perf against a VM could cause it to page fault and subsequently crash, resulting in downtime. The only workaround will be to disable all profiling tools until a fix is available. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Mantic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: mantic sts ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: - BugLink: https://bugs.launchpad.net/bugs/ + BugLink: https://bugs.launchpad.net/bugs/2054218 [Impact] Running perf against a QEMU/kvm process results in the guest suffering a page fault in trying to store Precise Event Based Sampling (PEBS) records for the host. This affects both using perf against a single process, in which it crashes the targeted guest, or using perf system wide, in which it crashes all running guests on the system. The issue was introduced in 6.0 by: commit c59a1f106f5cd4843c097069ff1bb2ad72103a67 Author: Like Xu Date: Mon Apr 11 18:19:36 2022 +0800 Subject: KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c59a1f106f5cd4843c097069ff1bb2ad72103a67 This affects all 6.2 and 6.5 kernels. There is no known workaround, apart from not using perf on affec
[Kernel-packages] [Bug 2054218] Re: kvm: Running perf against qemu processes results in page fault inside guest
Cover letter: https://lists.ubuntu.com/archives/kernel-team/2024-February/148896.html Patch: https://lists.ubuntu.com/archives/kernel-team/2024-February/148897.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/2054218 Title: kvm: Running perf against qemu processes results in page fault inside guest Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2054218 [Impact] Running perf against a QEMU/kvm process results in the guest suffering a page fault in trying to store Precise Event Based Sampling (PEBS) records for the host. This affects both using perf against a single process, in which it crashes the targeted guest, or using perf system wide, in which it crashes all running guests on the system. The issue was introduced in 6.0 by: commit c59a1f106f5cd4843c097069ff1bb2ad72103a67 Author: Like Xu Date: Mon Apr 11 18:19:36 2022 +0800 Subject: KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c59a1f106f5cd4843c097069ff1bb2ad72103a67 This affects all 6.2 and 6.5 kernels. There is no known workaround, apart from not using perf on affected systems. [Fix] The issue was fixed in 6.7 by: commit 971079464001c6856186ca137778e534d983174a Author: Paolo Bonzini Date: Thu Jan 4 16:15:17 2024 +0100 Subject: KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=971079464001c6856186ca137778e534d983174a This reinstates the logic for setting MSR_CORE_PERF_GLOBAL_CTRL to what it was before "KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS". - .guest = intel_ctrl & (~cpuc->intel_ctrl_host_mask | ~pebs_mask), + .guest = intel_ctrl & ~cpuc->intel_ctrl_host_mask & ~pebs_mask, The faulty logic includes any bit that isn't both marked as exclude_guest and using PEBS, while it should really be excluding PEBS from the host. [Testcase] Start a bare metal server. Enable KVM, start a few VMs. The VMs can be idle, they don't require any workload. $ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils uvtool $ sudo reboot $ ssh-keygen $ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-b release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-c release=jammy arch=amd64 $ virsh list Id Name State - 2jammy-a running 3jammy-b running 4jammy-c running $ uvt-kvm ssh jammy-a Check it works. $ ps aux | grep qemu Find the pid of jammy-a $ perf top -p $PID $ virsh console jammy-a Escape character is ^] (Ctrl + ]) [ 357.793039] BUG: unable to handle page fault for address: fe49178c6028 $ uvt-kvm ssh jammy-a (no response) Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf379502-test If you install it, then running perf against the PID of qemu processes will no longer crash the guest, and they will be accessible by SSH afterward. [Where problems could occur] We are rearranging the logic of setting the PEBS MSRs, which affects processor sampling of events. This will affect any profiling tools running against KVM based virtual machines, namely perf against QEMU. If a regression were to occur, running perf against a VM could cause it to page fault and subsequently crash, resulting in downtime. The only workaround will be to disable all profiling tools until a fix is available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054218/+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 2049195] Re: Wifi missing after upgrade to 6.5 kernel
I can confirm that with 6.5.0.17.17~22.04.9 the issue no longer appears for me, too. ** Changed in: linux-meta-hwe-6.5 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049195 Title: Wifi missing after upgrade to 6.5 kernel Status in linux-meta-hwe-6.5 package in Ubuntu: Fix Released Bug description: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
** Merge proposal linked: https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/460729 -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
Here is a backport of the partial fix to jammy https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd- rootfs/+merge/460729 I'm not sure I am best placed to update this bug description to match the SRU template though -- I'm not sure which builds are being affected in practice and so should be incorporated into the test plan. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2054234] [NEW] package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error e
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 Public bug reported: Error while applying changes pk-client-error-quark: Error while installing package: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10(313) lsb_release -rd Description:Ubuntu 22.04.4 LTS Release:22.04 $XDG_SESSION_TYPE wayland: command not found This is result from trying "additional drivers"option in "Software & Updates" (Obviously, after using Ubuntu since 10.04, my copy paste terminal chops reveal me to still be a noob.) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Feb 18 13:20:58 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2024-02-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check ** Attachment added: "Screenshot from 2024-02-18 13-27-58.png" https://bugs.launchpad.net/bugs/2054234/+attachment/5747069/+files/Screenshot%20from%202024-02-18%2013-27-58.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2054234 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Error while applying changes pk-client-error-quark: Error while installing package: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10(313) lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $XDG_SESSION_TYPE wayland: command not found This is result from trying "additional drivers"option in "Software & Updates" (Obviously, after using Ubuntu since 10.04, my copy paste terminal chops reveal me to still be a noob.) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Feb 18 13:20:58 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2024-02-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 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-390/+bug/2054234/+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 2054234] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2054234 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Error while applying changes pk-client-error-quark: Error while installing package: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10(313) lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $XDG_SESSION_TYPE wayland: command not found This is result from trying "additional drivers"option in "Software & Updates" (Obviously, after using Ubuntu since 10.04, my copy paste terminal chops reveal me to still be a noob.) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Feb 18 13:20:58 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2024-02-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 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-390/+bug/2054234/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
** Merge proposal linked: https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/460732 -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: [impact] In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. The losetup usage has been backported to Jammy, and sees frequent failures there. [test case] The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. [regression potential] If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
** Description changed: - In mantic, we migrated livecd-rootfs to use losetup -P instead of - kpartx, with the expectation that this would give us a reliable, race- - free way of loop-mounting partitions from a disk image during image - build. + [impact] + In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is - https://launchpad.net/~ubuntu- + https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. - https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/noble/ppc64el + https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. + + The losetup usage has been backported to Jammy, and sees frequent + failures there. + + [test case] + The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. + + [regression potential] + If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: [impact] In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. The losetup usage has been backported to Jammy, and sees frequent failures there. [test case] The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. [regression potential] If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post t
[Kernel-packages] [Bug 2051341] Re: black screen when wake up from s3 with AMD W7600 gfx
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-oem-6.5 verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051341 Title: black screen when wake up from s3 with AMD W7600 gfx Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The display is blank when resumed from s3 with AMD W7600 DGFx and Dell E2422H monitor [Fix] Mario points out the commit in 6.7 may help 3b401e30c249 drm/ttm: Reorder sys manager cleanup step [Test] 1. Build W7600 dGFx + Monitor: E2422H Config and FIDA Ubunutu22.04 OS. 2. Boot OS, put SUT to suspend. 3. Wake up the System from suspend. 4. Right away reboot the system from Ubuntu OS. 5. Put SUT to suspend and wake up the system. 6. After wake up Suspend, SUT should not be black screen. 7. Repetition Step 2~6 30 cycles [Where problems could occur] Handling the system memory manager after the workqueue is destroyed prevents from the pointer beeing used after free. Should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051341/+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 2051334] Re: There is sound from the speakers and headphones at the same time on one dell platform
** Tags removed: verification-needed-jammy-linux-oem-6.1 verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051334 Title: There is sound from the speakers and headphones at the same time on one dell platform 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] After headphone is plugged, the sound plays from both headphone and speaker. [Fix] Cirrus provides a fix for this issue and currently, the patch is in sound subsystem tree https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=fcfc9f711d1e2fc7876ac12b1b16c509404b9625 [Verify] Plugin headphone and play sounds, the sound should be from headphone only. [Where problems could occur] The fix is only for 2 specific models, and has been verfied. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051334/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
QA has done regression test on jammy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2054266] [NEW] microphone and headset does not work
Public bug reported: I have an Acer Aspire device and my internal microphone or headset does not work. And also frequently my device freezes and raises an error and redirects me to shell/black screen which I need to force reboot. I find here to report a bug since I'm an Ubuntu community member who runs Ubuntu 22.04.3 LTS version with Ubuntu Pro. If this is not the right place to ask my question then please give me some tip to get started kernel development and fixing Ubuntu bugs. happy hacking ! hwpplayer1@hwpplayer1-Aspire-A315-24P:~$ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename:jammy hwpplayer1@hwpplayer1-Aspire-A315-24P:~$ lspci | grep Audio 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1640 03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 6f) 03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller hwpplayer1@hwpplayer1-Aspire-A315-24P:~$ grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC256 hwpplayer1@hwpplayer1-Aspire-A315-24P:~$ lsmod | grep '^snd' | column -t snd_hda_codec_realtek 192512 1 snd_soc_dmic 12288 0 snd_hda_codec_generic 122880 1 snd_hda_codec_realtek snd_soc_acp6x_mach 24576 0 snd_acp6x_pdm_dma 12288 0 snd_hda_codec_hdmi 94208 1 snd_sof_amd_rembrandt 16384 0 snd_sof_amd_renoir 16384 0 snd_sof_amd_acp49152 2 snd_sof_amd_rembrandt,snd_sof_amd_renoir snd_sof_pci24576 2 snd_sof_amd_rembrandt,snd_sof_amd_renoir snd_hda_intel 61440 6 snd_sof_xtensa_dsp 12288 1 snd_sof_amd_acp snd_sof356352 2 snd_sof_amd_acp,snd_sof_pci snd_sof_utils 16384 1 snd_sof snd_intel_dspcfg 32768 2 snd_hda_intel,snd_sof snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg snd_hda_codec 212992 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 147456 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_soc_core 446464 4 snd_soc_acp6x_mach,snd_sof,snd_acp6x_pdm_dma,snd_soc_dmic snd_compress 28672 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core snd_hwdep 20480 1 snd_hda_codec snd_seq_midi 24576 0 snd_pci_ps 24576 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rpl_pci_acp6x 16384 0 snd_acp_pci12288 0 snd_pci_acp6x 16384 0 snd_rawmidi57344 1 snd_seq_midi snd_pcm196608 14 snd_sof_amd_acp,snd_hda_codec_hdmi,snd_pci_acp6x,snd_hda_intel,snd_hda_codec,snd_sof,snd_acp6x_pdm_dma,snd_compress,snd_soc_core,snd_sof_utils,snd_hda_core,snd_pci_ps,snd_pcm_dmaengine snd_seq118784 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_pci_acp5x 16384 0 snd_timer 49152 2 snd_seq,snd_pcm snd_rn_pci_acp3x 16384 0 snd_acp_config 16384 7 snd_rn_pci_acp3x,snd_pci_acp6x,snd_pci_acp5x,snd_sof_amd_rembrandt,snd_acp_pci,snd_pci_ps,snd_sof_amd_renoir snd143360 25 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi snd_soc_acpi 12288 2 snd_sof_amd_acp,snd_acp_config snd_pci_acp3x 16384 0 hwpplayer1@hwpplayer1-Aspire-A315-24P:~$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic_1 [HD-Audio Generic], device 0: ALC256 Analog [ALC256 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-18-generic 6.5.0-18.18~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 05:18:50 2024 InstallationDate: Installed on 2023-11-27 (83 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64
[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051896 Title: Fix spurious wakeup caused by Cirque touchpad Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Spurious wakeup event caused by Cirque touchpad, prevent the system from sleep properly. [Fix] Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad. [Test] Suspend the system 100 times and make sure non of the wakeup event is caused by the touchpad and its IRQ line. [Where problems could occur] Logically the power consumption can increase slightly, but in reality there isn't any noticeable change. Since the quirk only applies to one device, there isn't much regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051896/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
> With the last jigsaw in position, people may then test all necessary
components as a whole. So, yes, they were verified as an integrated set
with all proposed parts installed.
* linux/mantic-proposed version 6.5.0-17.17
* linux-oem-6.5 version 6.5.0-1010.11
* firmware-sof/mantic-proposed version 2.2.6-1ubuntu1.3
* firmware-sof/jammy-proposed version 2.0-1ubuntu4.5.
** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2049838] Re: Mute/mic LEDs no function on HP ZBook
Tested on SKUs of the said HP ZBooks with the following procedures: 1. Add PPA for Canonical Kernel Team (#2) [1] 2. Install the said kernel $ sudo apt install linux-image-unsigned-6.5.0-1015-oem 3. Reboot machine 4. Verify the kernel version using uname -a 5. Click the mute button and confirm that the mute LED works accordingly on those SKUs. The LED on the mute button works as expected. [1] https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa2 ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049838 Title: Mute/mic LEDs no function on HP ZBook Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The mute LEDS are not work properly on some newer HP ZBooks. [Fix] It needs the specific quirk for the hardware layout. Add it accordingly. [Test] Install the patched kernel and click the mute button. Confirm that the LED on the mute key turns on an off according to mute status. [Where problems could occur] This quirk only works if design of the board w.r.t. the same subsystem ID is unchanged. Otherwise the quirk will not work (the mute LEDs won't function normally). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2049838/+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 2054181] [NEW] Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu
You have been subscribed to a public bug: Dear Ubuntu Bug Tracking Team, I hope this message finds you well. I am writing to report an issue I have encountered while using Ubuntu. Issue Description: When connecting my BenQ monitor to a Belkin docking station via DisplayPort, Ubuntu fails to detect the monitor. Other monitor connected to same docking station via hdmi is working Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 12:33:13 2024 DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac] InstallationDate: Installed on 2020-06-01 (1355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago) dmi.bios.date: 07/17/2023 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N2SET31W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390: dmi.product.family: ThinkPad X390 dmi.product.name: 20SDCTO1WW dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu https://bugs.launchpad.net/bugs/2054181 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054181] Re: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu
I wonder if the Belkin docking station has enough bandwidth to drive multiple monitors simultaneously. Have you tried unplugging everything from the dock and just plugging in a monitor to the DisplayPort alone? Also next time the bug occurs, please run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054181 Title: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Dear Ubuntu Bug Tracking Team, I hope this message finds you well. I am writing to report an issue I have encountered while using Ubuntu. Issue Description: When connecting my BenQ monitor to a Belkin docking station via DisplayPort, Ubuntu fails to detect the monitor. Other monitor connected to same docking station via hdmi is working Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 12:33:13 2024 DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac] InstallationDate: Installed on 2020-06-01 (1355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago) dmi.bios.date: 07/17/2023 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N2SET31W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390: dmi.product.family: ThinkPad X390 dmi.product.name: 20SDCTO1WW dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2054181/+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 2054181] Re: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu
Also the specs for the Lenovo X390 suggest only one of the USB-C ports supports Thunderbolt, so it might be worth checking to see the dock is plugged into that port for the best performance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054181 Title: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Dear Ubuntu Bug Tracking Team, I hope this message finds you well. I am writing to report an issue I have encountered while using Ubuntu. Issue Description: When connecting my BenQ monitor to a Belkin docking station via DisplayPort, Ubuntu fails to detect the monitor. Other monitor connected to same docking station via hdmi is working Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 12:33:13 2024 DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac] InstallationDate: Installed on 2020-06-01 (1355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago) dmi.bios.date: 07/17/2023 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N2SET31W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390: dmi.product.family: ThinkPad X390 dmi.product.name: 20SDCTO1WW dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2054181/+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 2054212] Re: System starts, but monitor on HDMI has no signal
Can you test some other desktop environment like GNOME? And try Wayland? At the moment all I can see is that Xorg thinks both monitors are working. So the bug may be Xorg, the amdgpu Xorg driver, XFCE, or the kernel. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete ** Tags added: amdgpu ** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - System starts, but monitor on HDMI has no signal + System starts, but monitor on HDMI has no signal in 6.5 (but 6.2 works) ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054212 Title: System starts, but monitor on HDMI has no signal in 6.5 (but 6.2 works) Status in linux-hwe-6.5 package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I have been running with kernel 6.2 without any problems. However, when the system upgraded to kernel 6.5, the system boots, but the monitor connected via HDMI has no signal. The system seems to think everything is OK, there are no errors in the Xorg log, xrandr shows both displays, so does inxi -Fxxxrz. Both monitors are connected via the AMD Radeon RX 6600 graphics card, the LG using DisplayPort, the Benq using HDMI. The Benq monitor will show "No Signal Detected" when the system boots and I log into the desktop. The LG monitor shows the correct display. The Display app will show both monitors as present, it's just that nothing is actually sent via the cable to the monitor. So the monitor doesn't get any signal. If I connect the Benq via DisplayPort and the LG via HDMI, then the LG shows "No Signal Detected". Comparing the Xorg.0.log files from using kernel 6.2 and 6.5, I don't see any errors or indications why the HDMI output isn't sending data. I've attached a tar.gz file with the 6.2 and 6.5 kernel results for the Xorg.0.log, the output of "inxi -Fxxxrz" and "xrandr -q". My current work around is to boot into kernel 6.2, but I would like to see the new kernel functioning properly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Feb 17 17:09:53 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.50, 6.2.0-39-generic, x86_64: installed virtualbox/6.1.50, 6.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cezanne [1043:8809] InstallationDate: Installed on 2015-08-11 (3112 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-18-generic root=UUID=e6fe56b0-c6a6-48fd-9203-44e7395670df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2604 dmi.board.asset.tag: Default string dmi.board.name: PRIME B550-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2604:bd02/25/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB550-PLUS:rvrRevX.0x: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 vers
[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
verified:
* linux-firmware/jammy-proposed version 20220329.git681281e4-0ubuntu3.28
* linux-firmware/mantic-proposed version 20230919.git3672ccab-0ubuntu2.8
** Tags removed: verification-failed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic
--
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/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2048977
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
'hot reset' assert
2nd PCIe reset' assert
Asmedia 'hot reset' deassert
PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
5217b76bed90 ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37")
324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0:
update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git
history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
linux-firmware/noble version 20240202.git36777504-0ubuntu1 has all the
required commits already.
** Changed in: linux-firmware (Ubuntu Noble)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048853/+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 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
verified linux-firmware/mantic-proposed version
20230919.git3672ccab-0ubuntu2.8.
--
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/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048853/+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 2031882] Re: Missing firmware for Intel VPU on Intel Meteor Lake platforms
** Also affects: linux-firmware (Ubuntu Noble) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Fix Released ** Changed in: linux-firmware (Ubuntu Noble) Status: Fix Released => In Progress -- 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/2031882 Title: Missing firmware for Intel VPU on Intel Meteor Lake platforms Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware source package in Noble: In Progress Bug description: [SRU Justification] [Impact] Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform. intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 intel_vpu :00:0b.0: Failed to initialize VPU device: -2 intel_vpu: probe of :00:0b.0 failed with error -2 [Fix] Upstream Intel VPU linux driver project https://github.com/intel/linux-vpu-driver stores firmware blob in git- lfs. [Test Case] Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded. [Where problems could occur] Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet. [Other Info] While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default. == original bug report == Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https://github.com/intel/linux-vpu-driver, and firmware is the first one missing. [ 68.602028] intel_vpu :00:0b.0: enabling device ( -> 0002) [ 68.604010] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [ 68.604013] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 [ 68.604263] intel_vpu :00:0b.0: Failed to initialize VPU device: -2 [ 68.604272] intel_vpu: probe of :00:0b.0 failed with error -2 The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/intel/vpu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031882/+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 2031882] Re: Missing firmware for Intel VPU on Intel Meteor Lake platforms
Already fixed in linux-firmware/noble version 20240202.git36777504-0ubuntu1. ** Changed in: linux-firmware (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2031882 Title: Missing firmware for Intel VPU on Intel Meteor Lake platforms Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform. intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 intel_vpu :00:0b.0: Failed to initialize VPU device: -2 intel_vpu: probe of :00:0b.0 failed with error -2 [Fix] Upstream Intel VPU linux driver project https://github.com/intel/linux-vpu-driver stores firmware blob in git- lfs. [Test Case] Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded. [Where problems could occur] Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet. [Other Info] While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default. == original bug report == Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https://github.com/intel/linux-vpu-driver, and firmware is the first one missing. [ 68.602028] intel_vpu :00:0b.0: enabling device ( -> 0002) [ 68.604010] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [ 68.604013] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 [ 68.604263] intel_vpu :00:0b.0: Failed to initialize VPU device: -2 [ 68.604272] intel_vpu: probe of :00:0b.0 failed with error -2 The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/intel/vpu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031882/+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
