[Bug 2170475] [NEW] Closing the lid resulted in a dead-lock

Public bug reported: After closing the lid of the Laptop (HP Elitebook 840) the system did hang partly. After opening again, the Kubuntu/KDE Ui did work, but some commands in the shell like "sudo" stopped working. Trying to restart the either through the shell or the menu did not work. BIOS is up-to-date. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mitosch 2055 F.... pipewire mitosch 2059 F.... wireplumber /dev/snd/pcmC0D0p: mitosch 2055 F...m pipewire /dev/snd/seq: mitosch 2055 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 11 08:15:59 2026 InstallationDate: Installed on 2026-10-06 (5 days ago) InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) MachineType: HP HP EliteBook 840 14 inch G10 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=f56dacf8-dc22-4b6e-b2a0-b04d7b15d900 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2026 dmi.bios.release: 13.1 dmi.bios.vendor: HP dmi.bios.version: V70 Ver. 01.13.01 dmi.board.name: 8B41 dmi.board.vendor: HP dmi.board.version: KBC Version 51.47.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.71 dmi.modalias: dmi:bvnHP:bvrV70Ver.01.13.01:bd07/08/2026:br13.1:efr81.71:svnHP:pnHPEliteBook84014inchG10NotebookPC:pvrSBKPFV3:rvnHP:rn8B41:rvrKBCVersion51.47.00:cvnHP:ct10:cvr:sku6V5W7AV:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 14 inch G10 Notebook PC dmi.product.sku: 6V5W7AV dmi.product.version: SBKPFV3 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "stack trace of the deadlock causing the hang" https://bugs.launchpad.net/bugs/2170475/+attachment/6008075/+files/ec-deadlock-trace.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170475 Title: Closing the lid resulted in a dead-lock Status in linux package in Ubuntu: New Bug description: After closing the lid of the Laptop (HP Elitebook 840) the system did hang partly. After opening again, the Kubuntu/KDE Ui did work, but some commands in the shell like "sudo" stopped working. Trying to restart the either through the shell or the menu did not work. BIOS is up-to-date. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mitosch 2055 F.... pipewire mitosch 2059 F.... wireplumber /dev/snd/pcmC0D0p: mitosch 2055 F...m pipewire /dev/snd/seq: mitosch 2055 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 11 08:15:59 2026 InstallationDate: Installed on 2026-10-06 (5 days ago) InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) MachineType: HP HP EliteBook 840 14 inch G10 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=f56dacf8-dc22-4b6e-b2a0-b04d7b15d900 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2026 dmi.bios.release: 13.1 dmi.bios.vendor: HP dmi.bios.version: V70 Ver. 01.13.01 dmi.board.name: 8B41 dmi.board.vendor: HP dmi.board.version: KBC Version 51.47.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.71 dmi.modalias: dmi:bvnHP:bvrV70Ver.01.13.01:bd07/08/2026:br13.1:efr81.71:svnHP:pnHPEliteBook84014inchG10NotebookPC:pvrSBKPFV3:rvnHP:rn8B41:rvrKBCVersion51.47.00:cvnHP:ct10:cvr:sku6V5W7AV:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 14 inch G10 Notebook PC dmi.product.sku: 6V5W7AV dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170475/+subscriptions

[Bug 2160416] Re: Unable to connect to 6 GHz networks with MT7921K

apport information ** Tags added: apport-collected stonking ** Description changed: I am unable to use 6ghz WiFi with this chipset in Kubuntu 26.04. Only just noticed it because I upgraded my mesh WiFi at home to ASUS BT8, and my other devices work fine. Running "iw list" shows all 6ghz disabled. I tried forcing Swedish region with "sudo iw reg set SE" but no change. I found a bug report here, not sure if this is the same or not https://bugzilla.kernel.org/show_bug.cgi?id=218731 Happy to provide any additional information needed to help solve this. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jul 11 12:43:37 2026 InstallationDate: Installed on 2023-01-16 (1272 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-27 (106 days ago) dmi.bios.date: 04/16/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.20 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.20:bd04/16/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock + --- + ProblemType: Bug + ApportVersion: 2.36.0-0ubuntu1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 26.10 + InstallationDate: Installed on 2023-01-16 (1364 days ago) + InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) + MachineType: ASRock B650E PG Riptide WiFi + Package: linux (not installed) + ProcEnviron: + LANG=sv_SE.UTF-8 + LANGUAGE= + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 amdgpu.lttpr_enable=0 + ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + Tags: stonking + Uname: Linux 7.3.0-9-generic x86_64 + UpgradeStatus: Upgraded to stonking on 2026-10-10 (1 days ago) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 06/02/2026 + dmi.bios.release: 5.41 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: 4.41 + dmi.board.asset.tag: Default string + dmi.board.name: B650E PG Riptide WiFi + dmi.board.vendor: ASRock + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.41:bd06/02/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: + dmi.product.family: Default string + dmi.product.name: B650E PG Riptide WiFi + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: ASRock ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2160416/+attachment/6008035/+files/AlsaInfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160416 Title: Unable to connect to 6 GHz networks with MT7921K Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: I am unable to use 6ghz WiFi with this chipset in Kubuntu 26.04. Only just noticed it because I upgraded my mesh WiFi at home to ASUS BT8, and my other devices work fine. Running "iw list" shows all 6ghz disabled. I tried forcing Swedish region with "sudo iw reg set SE" but no change. I found a bug report here, not sure if this is the same or not https://bugzilla.kernel.org/show_bug.cgi?id=218731 Happy to provide any additional information needed to help solve this. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jul 11 12:43:37 2026 InstallationDate: Installed on 2023-01-16 (1272 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-27 (106 days ago) dmi.bios.date: 04/16/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.20 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.20:bd04/16/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock --- ProblemType: Bug ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 26.10 InstallationDate: Installed on 2023-01-16 (1364 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi Package: linux (not installed) ProcEnviron: LANG=sv_SE.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 amdgpu.lttpr_enable=0 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: stonking Uname: Linux 7.3.0-9-generic x86_64 UpgradeStatus: Upgraded to stonking on 2026-10-10 (1 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/02/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.41 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.41:bd06/02/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160416/+subscriptions

[Bug 2163126] Re: CMI8738 PCI audio device disappears with kernel 6.8.0-137

[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 subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163126 Title: CMI8738 PCI audio device disappears with kernel 6.8.0-137 Status in linux package in Ubuntu: Expired Bug description: I am reporting a possible kernel regression affecting a C-Media CMI8738/CMI8768 PCI audio card in a Dell OptiPlex 9020. With Ubuntu kernel 6.8.0-136-generic, the CMI8738 has remained stable during normal operation. After upgrading to kernel 6.8.0-137-generic, the CMI8738 initially works normally, but after approximately two hours the sound card disappears. When the failure occurs, the device disappears from both: aplay -l and: lspci The PCI device normally appears as: 05:00.0 Multimedia audio controller: C-Media Electronics Inc CMI8738/CMI8768 PCI Audio (rev 10) Because the device disappears from lspci, this appears to be below the PipeWire/ALSA user-space audio stack. Rebooting restores the device. The same hardware and Ubuntu installation remain stable when booted with 6.8.0-136-generic. Expected behavior: The CMI8738 PCI audio device should remain available during normal operation. Actual behavior: The device disappears after approximately two hours when running 6.8.0-137-generic. This appears to be a possible regression between kernel 6.8.0-136-generic and 6.8.0-137-generic. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-136-generic 6.8.0-136.136 ProcVersionSignature: Ubuntu 6.8.0-136.136-generic 6.8.12 Uname: Linux 6.8.0-136-generic x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 9 16:00:32 2026 InstallationDate: Installed on 2024-01-09 (943 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IwConfig: lo no wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9020 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-136-generic root=UUID=4b74565e-7d6f-48f1-80b4-0e0e3fd569ad 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: linux-restricted-modules-6.8.0-136-generic N/A linux-backports-modules-6.8.0-136-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.release: 65.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0N4YC8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd12/27/2017:br65.21:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:sku05A4: dmi.product.name: OptiPlex 9020 dmi.product.sku: 05A4 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163126/+subscriptions

[Bug 2169326] Re: Ubuntu 26.10 Concept - Wifi does not work after sleep [Lenovo Yoga Slim 7x]

The workaround I used was a script that reset the wifi hardware when it came out of standby. It might make it take a few seconds longer than a correct fix, but it worked well enough: Create the script: sudo nano /lib/systemd/system-sleep/wifi-unbind.sh Script contents: #!/bin/bash case "$1/$2" in pre/*) # Physically remove the Wi-Fi endpoint from the PCI bus before suspend if [ -d /sys/bus/pci/devices/0004:01:00.0 ]; then echo 1 > /sys/bus/pci/devices/0004:01:00.0/remove sleep 1 fi ;; post/*) # Rescan the PCI bus to rediscover and re-probe the Wi-Fi card echo 1 > /sys/bus/pci/rescan ;; esac It should apply immediately but might have to reboot if wifi is already borked. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169326 Title: Ubuntu 26.10 Concept - Wifi does not work after sleep [Lenovo Yoga Slim 7x] Status in ubuntu-concept: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Stonking: New Bug description: Ubuntu 26.10 Concept - Wifi does not work after sleep [Lenovo Yoga Slim 7x] Issue with Lenovo Yoga Slim 7x - Snapdragon X Elite. This error is reproducable. I did a fresh clean install of Ubuntu Concept 26.10 (Stonking Stingray Development Branch) using the ISO (I updated the installer during the install). The kernel version installed was 7.> After the install: - i close to lid to put the laptop into sleep - wait 30 seoncs to 5 mins - re-open the lid At this point, the wifi never starts up again. It appears active but does not see any networks. Doing a dmesg, i get the following errors: [ 318.682061] ath12k_wifi7_pci 0004:01:00.0: timeout while waiting for restart complete [ 318.682064] ath12k_wifi7_pci 0004:01:00.0: failed to resume core: -110 [ 318.682066] ath12k_wifi7_pci 0004:01:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110 [ 318.682075] ath12k_wifi7_pci 0004:01:00.0: PM: failed to resume async: error -110 [ 318.684876] OOM killer enabled. [ 318.684877] Restarting tasks: Starting [ 318.685569] Restarting tasks: Done [ 318.685586] efivarfs: resyncing variable state [ 318.792619] efivarfs: finished resyncing variable state [ 318.792684] random: crng reseeded on system resumption [ 318.805146] PM: suspend exit [ 318.838513] audit: type=1400 audit(1790960536.665:291): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=15472 comm="(ubuntu-insigh)" requested="userns_create" target="unprivileged_userns" execpath="/usr/lib/systemd/systemd-executor" [ 318.839115] audit: type=1400 audit(1790960536.666:292): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=15472 comm="(ubuntu-insigh)" capability=21 capname="sys_admin" [ 318.881100] audit: type=1400 audit(1790960536.708:293): apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 profile="unprivileged_userns" name="" pid=15505 comm="systemd-detect-" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 321.884027] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 321.884040] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 321.884047] ath12k_wifi7_pci 0004:01:00.0: failed to set ac override for ARP: -11 [ 321.884051] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 [ 324.892068] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 324.892081] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 324.892088] ath12k_wifi7_pci 0004:01:00.0: failed to enable PMF QOS: -11 [ 324.892093] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 [ 337.821974] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 337.821987] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 337.821994] ath12k_wifi7_pci 0004:01:00.0: failed to enable PMF QOS: -11 [ 337.821999] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 [ 350.809887] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 350.809899] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 350.809906] ath12k_wifi7_pci 0004:01:00.0: failed to enable PMF QOS: -11 [ 350.809910] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 I tried the following to troublesshhot - ran "qcom-firmware-extract" from an updated copy of windows 11 - I tried "systemctl restart NetworkManager" This behavior was not present with my hardware in Ubuntu 26.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-concept/+bug/2169326/+subscriptions

[Bug 2170457] Re: Regression: Intel i915 HDMI flickering and CPU pipe B FIFO underrun with eDP 1368x768 + HDMI 1920x1080@60 after Ubuntu 26.04 upgrade

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170457 Title: Regression: Intel i915 HDMI flickering and CPU pipe B FIFO underrun with eDP 1368x768 + HDMI 1920x1080@60 after Ubuntu 26.04 upgrade Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 26.04.1 LTS, an external HDMI monitor started flickering when used together with the laptop internal display in a specific display mode combination. Hardware: - Dell Latitude 3400 - Intel UHD Graphics 620 / WhiskeyLake-U GT2 [8086:3ea0] - Kernel driver: i915 - X11 session - Xorg modesetting driver + glamor - Ubuntu 26.04.1 LTS - Current kernel: 7.0.0-38-generic Problematic configuration: - Internal eDP-1: 1368x768 @ 60.05 Hz - External HDMI-1: 1920x1080 @ 60 Hz In this configuration, the external HDMI monitor flickers heavily and the kernel logs: i915 0000:00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun This exact setup worked normally before the Ubuntu 26.04 upgrade. The issue is reproducible with multiple hardware combinations: - Tested with 2 different external monitors - Tested with 3 different HDMI cables - Same behavior Tests performed: 1. eDP-1 1368x768 @60 + HDMI 1920x1080 @60 Result: flickering, CPU pipe B FIFO underrun 2. eDP-1 1368x768 @60 + HDMI 1920x1080 @30 Result: stable 3. eDP-1 disabled + HDMI 1920x1080 @60 Result: stable 4. eDP-1 1920x1080 @60 + HDMI 1920x1080 @60 Result: stable 5. eDP-1 1600x900 @60 + HDMI 1920x1080 @60 Result: stable 6. eDP-1 1280x720 @60 + HDMI 1920x1080 @60 Result: stable Changing the internal display scaling mode from "Full aspect" to "Center" does NOT solve the issue. The problematic internal display mode reported by xrandr is: 1368x768 (72.486 MHz) h: 1368 1416 1448 1528 v: 768 771 781 790 refresh: 60.05 Hz The working 1600x900 mode is: 1600x900 (97.866 MHz) h: 1600 1648 1680 1760 v: 900 903 908 926 refresh: 60.05 Hz Historical kernel logs: - Before the distribution upgrade, kernels 6.8.0-139, 6.8.0-142 and 6.8.0-146 were used. - No CPU pipe FIFO underrun was found in the reviewed historical logs for those kernels. - Ubuntu distribution upgrade occurred on 2026-09-30. - Kernel 7.0.0-34-generic was booted afterwards. - First recorded CPU pipe B FIFO underrun appeared on 2026-10-01 while running 7.0.0-34-generic. - The errors continue with 7.0.0-38-generic. Current workaround: - Internal display: 1600x900 @60 - External HDMI display: 1920x1080 @60 Another workaround: - Internal display: 1368x768 @60 - External HDMI display: 1920x1080 @30 Additional observation: Cinnamon stores the problematic display profile and reapplies HDMI 1920x1080@60 after HDMI hotplug, so disconnecting and reconnecting the monitor makes the flickering return. This appears to be a regression in the Intel i915/DRM display pipeline after the Ubuntu 26.04 upgrade, triggered specifically by the eDP 1368x768 mode while HDMI is active at 1920x1080@60. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: sobreiro 11396 F.... wireplumber /dev/snd/seq: sobreiro 11377 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon Date: Sat Oct 10 16:06:18 2026 InstallationDate: Installed on 2026-03-25 (199 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Latitude 3400 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=f2fc313e-7088-4155-9ae8-ba73e7ae9a15 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-01 (10 days ago) dmi.bios.date: 03/26/2025 dmi.bios.release: 1.38 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.38.0 dmi.board.name: 0XWHC2 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.38.0:bd03/26/2025:br1.38:svnDellInc.:pnLatitude3400:pvr:rvnDellInc.:rn0XWHC2:rvrA05:cvnDellInc.:ct10:cvr:sku08BC:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 3400 dmi.product.sku: 08BC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170457/+subscriptions

[Bug 2169181] Re: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060

I experience the same on my system, RX 7800 XT and Ryzen 5 5600, Ubuntu 26.04 + 1440p + 1080p monitor setup It comes out faster and more frequently when I hog the CPU, for example with stress --cpu 12 and moving some windows or enabling and disabling night light. Doesn't happen on weston or x11 session, however its mostly sure a kernel regression, as I tested the latest mainline 7.2.6 and Ubuntu's 7.0.0.34 and everything is fine here. The only different thing is the following kernel log line at startup when booting on the buggy kernel [ 16.477207] amdgpu 0000:2d:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:148 I also tried my Thinkpad L15 which has an AMD APU Pro 5650u, its still present here but less noticeable even with huge CPU load. Found this on amdgpu drm bugzilla https://gitlab.freedesktop.org/drm/amd/-/work_items/5952 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169181 Title: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing intermittent pixel corruption and flickering artifacts in the background/desktop UI after updating to kernel version 7.0.0-38. Behavior:     Random pixels/artifacts briefly flicker in the background from time to time.     This issue was NOT present in kernel 7.0.0-34.     The issue started immediately after updating to kernel 7.0.0-38. CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz GPU: AMD Radeon RX 9060 XT 16 GB[Discrete] P.S. I was planning to upgrade to the 26.10 beta this weekend, but I will stay on Resolute to help resolve this issue with any testing you might need. Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 18:29:50 2026 InstallationDate: Installed on 2026-08-31 (31 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name ProcEnviron:  LANG=es_ES.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=1bdfa414-371c-4c93-9288-8cdc845cb610 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2026 dmi.bios.release: 38.41 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3841 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS 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.:bvr3841:bd02/25/2026:br38.41:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: 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/2169181/+subscriptions

[Bug 2163642] Re: Kernel panic "Attempted to kill the idle task" on AMD Opteron multi-node NUMA under KVM (6.8.0-137)

Hi Radovan, Yes, the stopper panic is definitely a secondary crash from the KVM oops. Notice the faulting address 0xfffb77e9d05d8b4c in kvm_replace_memslot - bit 50 is flipped from the canonical 0xffff range. Once that vCPU thread oopsed and tainted the kernel with 'D', corrupted structures were left behind. Surviving 6 days after an oops on a 4-node NUMA host is actually impressive, but the scheduler eventually trips over it during migrate_swap. The hpilo IO_PAGE_FAULT at 0xbde0e000 is a side effect - pstore ERST tried to save the oops into ACPI reserved memory and AMD-Vi blocked it. On the journal- no need for gigabytes of userspace noise, but pls attach the snippet from those ~4 minutes before the freeze. Curious if any RCU stalls, soft lockups, or MCEs showed up right before the console went down. As for srv05 and srv07, I'd just let them keep running their soak test. But IMHO, 21 days on srv04 vs 3d and 8d without the params speaks for itself. I'd just keep processor.max_cstate=1 idle=nomwait on prod hosts. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163642 Title: Kernel panic "Attempted to kill the idle task" on AMD Opteron multi- node NUMA under KVM (6.8.0-137) Status in linux package in Ubuntu: Confirmed Bug description: **Title:** Kernel panic "Attempted to kill the idle task" on AMD Opteron 6300 series (multi-node NUMA) under KVM load - linux 6.8.0-137-generic (24.04) **Summary:** On 5 out of 5 identical HP ProLiant DL385p Gen8 servers (AMD Opteron 6386 SE, 4 NUMA nodes each, running as KVM/libvirt hypervisors with multiple guest VMs), kernel panics with "Attempted to kill the idle task!" occurred within roughly 1 to 24 hours after upgrading from Ubuntu 22.04 (kernel 5.15.0-187-generic, stable in production for years) to Ubuntu 24.04 (kernel 6.8.0-137-generic) via do-release- upgrade. Pinning the boot kernel back to 5.15.0-187-generic (via GRUB_DEFAULT) while keeping the 24.04 userspace fully resolved the instability on all affected hosts, with no further crashes since. **Hardware:** - HP ProLiant DL385p Gen8, BIOS A28 (03/14/2018) - AMD Opteron 6386 SE, microcode 0x6000852 - 4 NUMA nodes per host - KVM/libvirt hypervisor, 9-20 guest VMs per host under production load (mixed Kubernetes control-plane/worker nodes, haproxy, monitoring, storage services) **Steps to reproduce:** 1. Fresh `do-release-upgrade` from 22.04 (5.15.0-187-generic) to 24.04 (6.8.0-137-generic) on the described hardware 2. Boot into 6.8.0-137-generic with multiple KVM guests running under moderate-to-high, mixed CPU/memory load 3. Panic occurs non-deterministically, anywhere from ~1 hour to ~24 hours after boot; not tied to any single reproducible user action **Observed panic signature (consistent across all 5 affected hosts):** ``` Kernel panic - not syncing: Attempted to kill the idle task! Call Trace: <TASK> ? multi_cpu_stop+0xa0/0x120 ? __pfx_multi_cpu_stop+0x10/0x10 cpu_stopper_thread+0x9c/0x170 ? __pfx_smpboot_thread_fn+0x10/0x10 smpboot_thread_fn+0xe3/0x1e0 kthread+0xf2/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x47/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> ``` One instance on a related host (same hardware) additionally showed `membarrier_private_expedited+0x1cf/0x2d0` in RIP immediately preceding the panic. **Possible related upstream discussion:** A 2018 LKML thread by Matt Fleming (SUSE), "cpu stopper threads and load balancing leads to deadlock" (https://lkml.iu.edu/hypermail/linux/kernel/1804.2/01642.html), describes a closely matching mechanism: a CPU stopper thread entering idle/active load balancing while, concurrently, NUMA balancing on another CPU attempts to migrate a task via `stop_two_cpus()`, resulting in a deadlock over the stopper lock. Given that our affected hosts are multi-node NUMA systems (4 nodes) and the panic call trace centers on `cpu_stopper_thread`/`multi_cpu_stop`, this looks like a strong candidate mechanism, though we cannot confirm whether it is the same unresolved issue, a regression of a past fix, or a new but related bug in 6.8. **Workaround applied:** GRUB kernel pinning to boot `5.15.0-187-generic` while keeping the 24.04 userspace intact (`GRUB_DEFAULT` set to the jammy kernel's advanced boot entry ID, `update-grub`, reboot). All 5 hosts stable since applying this workaround. **Additional diagnostics performed:** - Hardware (BIOS version, CPU model, microcode) verified identical across all 5 affected hosts - Memtester (4GB sample, full test cycle) passed clean on the two hosts tested - HP Integrated Management Log (IML) reviewed on two hosts: one shows a documented Uncorrectable CPU Machine Check Exception from 2020 (Bank 0x04, both physical processors) - possibly a contributing factor for that specific host, but does not explain the same panic signature occurring on hosts without such MCE history - Network/bonding layers (LACP, active-backup) verified healthy and unrelated to the panics - `dmesg`/`journalctl` EDAC output shows no correctable/uncorrectable memory errors logged around panic times on the hosts checked **Please let me know what additional information (full dmesg, kernel config, /proc/cpuinfo, NUMA topology via `numactl --hardware`, etc.) would help diagnose this further.** --- ProblemType: Bug AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Aug 18 15:57 seq crw-rw---- 1 root audio 116, 33 Aug 18 15:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: 20240524 DistroRelease: Ubuntu 24.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL385p Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-137-generic root=UUID=9d93cee9-3b2d-4aff-b422-59c0ba9a1198 ro console=ttyS0,115200n8 console=tty0 vga=normal nomodeset nointremap ProcVersionSignature: Ubuntu 6.8.0-137.137-generic 6.8.12 RelatedPackageVersions: linux-restricted-modules-6.8.0-137-generic N/A linux-backports-modules-6.8.0-137-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image noble Uname: Linux 6.8.0-137-generic x86_64 UpgradeStatus: Upgraded to noble on 2026-08-13 (5 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: HP dmi.bios.version: A28 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrA28:bd03/14/2018:efr2.82:svnHP:pnProLiantDL385pGen8:pvr:cvnHP:ct23:cvr:sku653203-B21: dmi.product.family: ProLiant dmi.product.name: ProLiant DL385p Gen8 dmi.product.sku: 653203-B21 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163642/+subscriptions

[Bug 2169236] Re: HDMI A/V desync on Intel UHD 630 (Comet Lake) since 7.0.0-34, still present on 7.0.0-38

Further testing, 2026-10-10. Another HWE kernel update. After a normal reboot into the new kernel, HDMI A/V was late again (same ~2 s, HDMI only, Aux fine). Switched back to 7.0.0-31: desync still present, same as the 2026-10-02 test. A reboot does not clear it. Full Sony power-off and HDMI unplug for 10 seconds cleared it on the new kernel as well. Same recovery as on 31 and 38. Summary: - First seen after 7.0.0-34. - Reproduced on 34, 38, and the current kernel after a normal reboot. - Once the Sony is in the bad state, it survives reboot and kernel switches (including back to 31). - Cleared on every kernel tested only by a full sink power-off and cable reseat. - 7.0.0-31 is not immune once the link is stuck; it only looked clean on 2026-09-29. This looks like an i915 HDMI bring-up change from 7.0.0-34 that leaves the sink with a sticky A/V offset. The unplug is a recovery, not evidence that the kernel is unrelated. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169236 Title: HDMI A/V desync on Intel UHD 630 (Comet Lake) since 7.0.0-34, still present on 7.0.0-38 Status in linux package in Ubuntu: Incomplete Bug description: Regression on Ubuntu 24.04 HWE kernels (Linux Mint 22.2). Hardware: - Intel CometLake-S GT2 UHD Graphics 630 (8086:9bc8), i915 - HDMI-1 to Sony TV, 1920x1080 - Analog Aux is unaffected Last good: 7.0.0-31-generic First bad: 7.0.0-34-generic Still bad: 7.0.0-38-generic On 34 and 38, HDMI video freezes about 5 seconds at start, then voice is about 2 seconds late. Firefox, Brave, and Celluloid all show it. Aux stays in sync. PipeWire latency offset does not change it. 7.0.0-31 is clean with the same Xorg (2:21.1.12-1ubuntu1.8), so this is not the Xorg update from 2026-09-29. ubuntu-bug linux refused the report: "This does not seem to be an official Linux package" on linux-image-7.0.0-38-generic (Mint). --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: brett 2067 F.... pipewire brett 2070 F.... wireplumber /dev/snd/pcmC0D3p: brett 2067 F...m pipewire /dev/snd/seq: brett 2067 F.... pipewire CRDA: N/A CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CurrentDesktop: i3 DistroRelease: Linux Mint 22.2 InstallationDate: Installed on 2025-12-25 (285 days ago) InstallationMedia: Linux Mint 22.2 "Zara" - Release amd64 20250828 MachineType: Micro-Star International Co., Ltd. MS-7D82 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=8f09b6c5-7d43-4a10-a1a1-8f954eef5146 ro quiet splash ProcVersionSignature: Ubuntu 7.0.0-38.38~24.04.4-generic 7.0.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-38-generic N/A linux-backports-modules-7.0.0-38-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no Tags: zara Uname: Linux 7.0.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/26/2026 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.71 dmi.board.asset.tag: Default string dmi.board.name: PRO H410M-B (MS-7D82) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.71:bd03/26/2026:br5.19:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D82:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROH410M-B(MS-7D82):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D82 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169236/+subscriptions

[Bug 2169181] Re: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060

I have the same problem, which started on 7.0.0.38 with Ubuntu 26.04. a RX 9060 XT and a Samsung TV connected in HDMI as monitor, 4k @ 60Hz. The horizontal "bar" so quickly disappears that it's barely visible. It covers like 50%-70% of the screen width, is usually located near the bottom of the screen, and has a height of 10% of the screen height. It's as if a "cloud" of random pixel was appearing in that zone, for a very, very short time. That happens about once or twice per hour, roughly. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169181 Title: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing intermittent pixel corruption and flickering artifacts in the background/desktop UI after updating to kernel version 7.0.0-38. Behavior:     Random pixels/artifacts briefly flicker in the background from time to time.     This issue was NOT present in kernel 7.0.0-34.     The issue started immediately after updating to kernel 7.0.0-38. CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz GPU: AMD Radeon RX 9060 XT 16 GB[Discrete] P.S. I was planning to upgrade to the 26.10 beta this weekend, but I will stay on Resolute to help resolve this issue with any testing you might need. Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 18:29:50 2026 InstallationDate: Installed on 2026-08-31 (31 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name ProcEnviron:  LANG=es_ES.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=1bdfa414-371c-4c93-9288-8cdc845cb610 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2026 dmi.bios.release: 38.41 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3841 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS 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.:bvr3841:bd02/25/2026:br38.41:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: 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/2169181/+subscriptions

[Bug 2169319] Re: amdgpu: screen flashes at 120/144 Hz on RX 9060 XT (gfx1200), regression 7.0.0-34 -> 7.0.0-38

I have the same problem, which started on 7.0.0.38 with Ubuntu 26.04. a RX 9060 XT and a Samsung TV connected in HDMI as monitor, 4k @ 60Hz. The horizontal "bar" so quickly disappears that it's barely visible. It covers like 50%-70% of the screen width, is usually located near the bottom of the screen, and has a height of 10% of the screen height. It's as if a "cloud" of random pixel was appearing in that zone, for a very, very short time. That happens about once or twice per hour, roughly. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169319 Title: amdgpu: screen flashes at 120/144 Hz on RX 9060 XT (gfx1200), regression 7.0.0-34 -> 7.0.0-38 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to linux-image-7.0.0-38-generic, a DisplayPort monitor shows ~1 ms visual flashes (tearing-like) at 120 Hz and 144 Hz. 7.0.0-34-generic is clean at the same refresh rate with identical userspace. Hardware - GPU: AMD Radeon RX 9060 XT (gfx1200), PCI 1002:7590, driver amdgpu - Display: HWV ZQE-CAA, 3440x1440, 165 Hz native, DP-1, 10 bpc, no DSC - Session: GNOME Wayland (mutter 50.1), Mesa 26.0.8 Symptom - Brief flashes on pointer motion and small damage repaints (typing in a terminal, overview hover, mouse movement). GL apps make it more frequent; it still happens with all GPU apps closed. - Clean at 60 Hz and 100 Hz. Glitches at 120 Hz and 144 Hz. - Clean on the GDM greeter. Regression - 7.0.0-34-generic: clean at 144 Hz. 7.0.0-38-generic: glitches at 144 Hz. - Same mutter, Mesa and monitor on both; only the kernel changed. - A second machine (AMD iGPU, internal panel, 7.0.0-34) is unaffected; it has not run -38 yet. Ruled out (still glitches on -38) - Userspace mismatch after upgrade (rebooted after full-upgrade) - GNOME animations disabled - Hardware cursor plane disabled (MUTTER_DEBUG_DISABLE_HW_CURSORS=1, MUTTER_DEBUG_INHIBIT_HW_CURSOR=1, verified in gnome-shell environ) - Overlay planes (MUTTER_DEBUG_FORCE_KMS_MODE=simple, verified) - Link side: dp1 link_settings (4 lanes, 0x1e = HBR3), DSC state (off), max bpc (10), amdgpu_dm_capabilities and amdgpu_dm_dtn_log are identical between -34 and -38 at 144 Hz. No DP link-training/DSC errors in dmesg on either kernel. Suspect commits (from the linux 7.0.0-38.38 changelog, not bisected) 1. drm/amd/display: consolidate DCN vblank/flip handling onto ... 2. drm/amd/display: Fix DTB DTO updates breaking live pixel rate sources 3. drm/amd/display: Fix mem_type change detection for async flips 4. drm/amd/display: Handle struct drm_plane_state.ignore_damage_clips Attached: dp1-link, dm-capabilities and dtn for both kernels, modes-DP1.txt, monitor-edid-34.txt in all in file ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 18:38:04 2026 InstallationDate: Installed on 2025-02-22 (587 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=tmux-256color XDG_RUNTIME_DIR=<set> SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to resolute on 2026-10-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169319/+subscriptions

[Bug 2170396] Re: Lenovo Legion screen flickering on Kubuntu 26.04 (Fixed by lowering brightness / 165Hz conflict)

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170396 Title: Lenovo Legion screen flickering on Kubuntu 26.04 (Fixed by lowering brightness / 165Hz conflict) Status in linux package in Ubuntu: New Bug description: I installed Kubuntu 26.04 on my Lenovo Legion laptop (NVIDIA graphics) and experienced severe screen flickering. Key behaviors observed: • The panel natively runs at 165.04Hz. • Forcing the refresh rate down to 60Hz via kscreen-doctor temporarily improved the flickering but did not resolve it. • Forcing "Discrete Graphics" in the BIOS resulted in a total black screen upon OS load. • Crucial Hardware Link: Lowering the screen brightness manually to 30% reduces the flickering to minimal/manageable levels, suggesting a power-delivery/backlight voltage or PWM conflict with the modern kernel's power-saving features. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jgw 1549 F.... pipewire jgw 1561 F.... wireplumber /dev/snd/controlC0: jgw 1561 F.... wireplumber /dev/snd/seq: jgw 1549 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Oct 9 19:23:43 2026 InstallationDate: Installed on 2026-10-07 (2 days ago) InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) MachineType: LENOVO 82TF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=3ad3b9bb-66ac-4411-a956-601a55f3254c ro quiet splash pcie_aspm=off acpi_backlight=native PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2025 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: JYCN58WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 16IAH7 dmi.ec.firmware.release: 1.55 dmi.modalias: dmi:bvnLENOVO:bvrJYCN58WW:bd03/03/2025:br1.58:efr1.55:svnLENOVO:pn82TF:pvrLegionS716IAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegionS716IAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionS716IAH7:pfaLegionS716IAH7: dmi.product.family: Legion S7 16IAH7 dmi.product.name: 82TF dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion S7 16IAH7 dmi.product.version: Legion S7 16IAH7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170396/+subscriptions

[Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Your business doesn't need another generic SEO package—it needs a plan that understands your market and speaks to your ideal customers. Web Founders USA is a results-focused Boutique SEO Agency helping businesses strengthen their search presence with tailored optimization and thoughtful strategy. We combine long-tail keyword targeting, topical authority development, content architecture, technical SEO, local search optimization, competitor gap research, internal linking, and relevant backlink building to help your website compete for valuable searches. By aligning search engine optimization with user experience and conversion opportunities, we aim to attract visitors who are genuinely interested in your services. Ready to make your website a stronger source of qualified leads? Contact Web Founders USA today for a personalized SEO strategy built around your business and growth priorities. For more info: https://www.webfoundersusa.com/service/seo- services/boutique-seo/ -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=10000, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x00000008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=10000, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x00000008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia-6.8/6.8.0-1065.68~22.04.1+1)

All autopkgtests for the newly accepted linux-restricted-modules-nvidia-6.8 (6.8.0-1065.68~22.04.1+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/470.256.02-0ubuntu0.22.04.6 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-nvidia-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions