Public bug reported: I am using Kubuntu on a Dell Latitude 7280 with Intel HD Graphics 620. Without any kernel workaround, the internal display does not turn back on after either DPMS display power-off or system suspend. Symptoms: * The screen remains completely black. * Ctrl+Alt+F2/F3/F4 does not switch to a virtual console. * The system appears unresponsive. * The only way to recover is to hold the power button and force a shutdown. Hardware and software: * Computer: Dell Latitude 7280 * BIOS: 1.41.3 * GPU: Intel Corporation Kaby Lake-U GT2 [HD Graphics 620] * Graphics driver: i915 * Main tested kernel: 7.0.0-22-generic * Also reproduced with: 6.17.0-35-generic * Desktop: KDE Plasma * Reproduced under both Wayland and X11 Steps to reproduce with display power management: 1. Boot normally without i915.enable_dc=0. 2. Run: xset dpms force off 3. Try to wake the display using the keyboard or mouse. Actual result: The internal display remains black and the system has to be forcibly powered off. Steps to reproduce with suspend: 1. Boot normally without i915.enable_dc=0. 2. Run: sudo systemctl suspend 3. Press the power button to resume. Actual result: The system does not resume correctly. The screen remains black and the machine appears frozen. Tests already performed: * Tested both suspend modes: deep and s2idle. * Tested i915.enable_psr=0: no improvement. * Tested kernels 7.0.0-22-generic and 6.17.0-35-generic: the issue occurred with both. * BIOS is already updated to version 1.41.3. * Reproduced with both KDE Plasma Wayland and Plasma X11. A previous boot log contained: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A The following kernel parameter fixes both problems: i915.enable_dc=0 After adding it to the kernel command line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0" the internal display powers off and wakes correctly, and suspend/resume also works correctly. The current value is confirmed with: cat /sys/module/i915/parameters/enable_dc which returns: 0 This suggests that Intel Display C-States are involved in the failure. Please let me know if further i915 debugging information or additional kernel logs are required. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: antonio 1699 F.... pipewire antonio 1703 F.... wireplumber /dev/snd/pcmC0D0p: antonio 1699 F...m pipewire /dev/snd/seq: antonio 1699 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 21 17:29:49 2026 InstallationDate: Installed on 2025-12-16 (187 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Latitude 7280 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=42d7b726-4f01-417b-99a5-9d693e647797 ro quiet splash i915.enable_dc=0 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) WifiSyslog: dmi.bios.date: 02/09/2025 dmi.bios.release: 1.41 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.41.3 dmi.board.name: 0KK5D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.41.3:bd02/09/2025:br1.41:svnDellInc.:pnLatitude7280:pvr:rvnDellInc.:rn0KK5D1:rvrA00:cvnDellInc.:ct10:cvr:sku079F:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 7280 dmi.product.sku: 079F dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157741 Title: [Dell Latitude 7280][Intel HD 620] Black screen and system freeze after display power-off or suspend; fixed by i915.enable_dc=0 Status in linux package in Ubuntu: New Bug description: I am using Kubuntu on a Dell Latitude 7280 with Intel HD Graphics 620. Without any kernel workaround, the internal display does not turn back on after either DPMS display power-off or system suspend. Symptoms: * The screen remains completely black. * Ctrl+Alt+F2/F3/F4 does not switch to a virtual console. * The system appears unresponsive. * The only way to recover is to hold the power button and force a shutdown. Hardware and software: * Computer: Dell Latitude 7280 * BIOS: 1.41.3 * GPU: Intel Corporation Kaby Lake-U GT2 [HD Graphics 620] * Graphics driver: i915 * Main tested kernel: 7.0.0-22-generic * Also reproduced with: 6.17.0-35-generic * Desktop: KDE Plasma * Reproduced under both Wayland and X11 Steps to reproduce with display power management: 1. Boot normally without i915.enable_dc=0. 2. Run: xset dpms force off 3. Try to wake the display using the keyboard or mouse. Actual result: The internal display remains black and the system has to be forcibly powered off. Steps to reproduce with suspend: 1. Boot normally without i915.enable_dc=0. 2. Run: sudo systemctl suspend 3. Press the power button to resume. Actual result: The system does not resume correctly. The screen remains black and the machine appears frozen. Tests already performed: * Tested both suspend modes: deep and s2idle. * Tested i915.enable_psr=0: no improvement. * Tested kernels 7.0.0-22-generic and 6.17.0-35-generic: the issue occurred with both. * BIOS is already updated to version 1.41.3. * Reproduced with both KDE Plasma Wayland and Plasma X11. A previous boot log contained: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A The following kernel parameter fixes both problems: i915.enable_dc=0 After adding it to the kernel command line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0" the internal display powers off and wakes correctly, and suspend/resume also works correctly. The current value is confirmed with: cat /sys/module/i915/parameters/enable_dc which returns: 0 This suggests that Intel Display C-States are involved in the failure. Please let me know if further i915 debugging information or additional kernel logs are required. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: antonio 1699 F.... pipewire antonio 1703 F.... wireplumber /dev/snd/pcmC0D0p: antonio 1699 F...m pipewire /dev/snd/seq: antonio 1699 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 21 17:29:49 2026 InstallationDate: Installed on 2025-12-16 (187 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Latitude 7280 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=42d7b726-4f01-417b-99a5-9d693e647797 ro quiet splash i915.enable_dc=0 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) WifiSyslog: dmi.bios.date: 02/09/2025 dmi.bios.release: 1.41 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.41.3 dmi.board.name: 0KK5D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.41.3:bd02/09/2025:br1.41:svnDellInc.:pnLatitude7280:pvr:rvnDellInc.:rn0KK5D1:rvrA00:cvnDellInc.:ct10:cvr:sku079F:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 7280 dmi.product.sku: 079F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157741/+subscriptions
воскресенье
[Bug 2157721] Re: package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: ...
dkms autoinstall on 6.8.0-124-generic/x86_64 failed for anbox-binder(10) -------------------------------------------- This is not a bug with Ubuntu or the kernel. This is a problem with a non-Ubuntu program (anbox). ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157721 Title: package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: ... Status in Ubuntu: Invalid Bug description: Similiar bug happens every boot. Ubuntu itself is not affected visibly. (Debug information should be included). package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück Translated EN: »installed linux-headers-6.8.0-124-generic package post-installation script subprocess returned error exit status 11 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-124-generic 6.8.0-124.124 ProcVersionSignature: Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11 Uname: Linux 6.11.0-19-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: leander 5101 F.... pipewire /dev/snd/controlC1: leander 5106 F.... wireplumber /dev/snd/controlC0: leander 5106 F.... wireplumber CasperMD5CheckResult: pass Date: Sat Jun 20 10:44:41 2026 ErrorMessage: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück InstallationDate: Installed on 2025-03-15 (463 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=238592be-4ab6-4339-b982-b4033344d418 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2020 dmi.bios.release: 1.26 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.26 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.18 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.26:bd03/03/2020:br1.26:efr3.18:svnHewlett-Packard:pnHPZBook17G2:pvrA3009CD10303:rvnHewlett-Packard:rn2255:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:skuG6Z40AV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z40AV dmi.product.version: A3009CD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2157721/+subscriptions
суббота
[Bug 2157721] [NEW] package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: ...
Public bug reported: Similiar bug happens every boot. Ubuntu itself is not affected visibly. (Debug information should be included). package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück Translated EN: »installed linux-headers-6.8.0-124-generic package post- installation script subprocess returned error exit status 11 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-124-generic 6.8.0-124.124 ProcVersionSignature: Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11 Uname: Linux 6.11.0-19-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: leander 5101 F.... pipewire /dev/snd/controlC1: leander 5106 F.... wireplumber /dev/snd/controlC0: leander 5106 F.... wireplumber CasperMD5CheckResult: pass Date: Sat Jun 20 10:44:41 2026 ErrorMessage: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück InstallationDate: Installed on 2025-03-15 (463 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=238592be-4ab6-4339-b982-b4033344d418 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2020 dmi.bios.release: 1.26 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.26 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.18 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.26:bd03/03/2020:br1.26:efr3.18:svnHewlett-Packard:pnHPZBook17G2:pvrA3009CD10303:rvnHewlett-Packard:rn2255:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:skuG6Z40AV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z40AV dmi.product.version: A3009CD10303 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157721 Title: package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: ... Status in linux package in Ubuntu: New Bug description: Similiar bug happens every boot. Ubuntu itself is not affected visibly. (Debug information should be included). package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück Translated EN: »installed linux-headers-6.8.0-124-generic package post-installation script subprocess returned error exit status 11 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-124-generic 6.8.0-124.124 ProcVersionSignature: Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11 Uname: Linux 6.11.0-19-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: leander 5101 F.... pipewire /dev/snd/controlC1: leander 5106 F.... wireplumber /dev/snd/controlC0: leander 5106 F.... wireplumber CasperMD5CheckResult: pass Date: Sat Jun 20 10:44:41 2026 ErrorMessage: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück InstallationDate: Installed on 2025-03-15 (463 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=238592be-4ab6-4339-b982-b4033344d418 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-124-generic 6.8.0-124.124 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.8.0-124-generic«-Unterprozess gab den Fehlerwert 11 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2020 dmi.bios.release: 1.26 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.26 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.18 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.26:bd03/03/2020:br1.26:efr3.18:svnHewlett-Packard:pnHPZBook17G2:pvrA3009CD10303:rvnHewlett-Packard:rn2255:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:skuG6Z40AV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z40AV dmi.product.version: A3009CD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157721/+subscriptions
[Bug 2141198] Re: Suspend failure with mt7925e after kernel upgrade
Confirming this on a noble base with a couple of additional data points. Hardware: Framework 13 AMD (Ryzen AI 9 HX 370), Pop!_OS 24.04 (noble base), COSMIC/Wayland. WiFi: MediaTek RZ717, **device ID `14c3:0717`** — most reports on this bug cite `14c3:7925`, so the same `mt7925e` resume hang affects the 0717 variant too. Symptom: after s2idle resume the display returns but input devices are dead, requiring a hard reset. The standard isolation confirms the driver as the cause here as well: nmcli radio wifi off sudo modprobe -r mt7925e sudo rtcwake -m mem -s 20 # -> clean resume with working keyboard/touchpad Additional finding not mentioned in the existing reports: **hibernate is affected too**, not just s2idle. With `mt7925e` loaded, hibernate enters but never resumes (hard reset); with the module unloaded across the cycle, hibernate save/restore works. So this isn't specific to the s2idle path — it's the driver failing on resume regardless of the sleep type. Workaround in use: a `systemd-sleep` hook (`/usr/lib/systemd/system-sleep/`) that unloads `mt7925e` on `pre` and reloads on `post`, which covers suspend, hibernate, and suspend-then-hibernate in one place. Same idea as the script already posted here, just generalized to all sleep types. Caveat for triage: I'm on the System76 7.0.x kernel line, **not** a stock Ubuntu kernel, and I have not bisected against current mainline — so I can't say whether this is already fixed upstream (some fixes reportedly landed ~6.15.3) or is a missing backport. Flagging the System76 kernel explicitly in case that puts it out of scope for this package; the device-ID and hibernate data points may still be useful for the broader picture. Related: kernel Bugzilla #219825 and #220395. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2141198 Title: Suspend failure with mt7925e after kernel upgrade Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: Last night, I updated to kernel 6.8.0-100.100 from kernel 6.8.0-94.96 and immediately shut down the computer. Today I booted the computer, read some things for a few minutes and tried to suspend, which failed repeatedly. I had no such problem in the previous kernel. journalctl reported the following lines as the source of the problem: Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: Message 00020007 (seq 5) timeout Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend+0x0/0x2e0 [mt7925e] returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: failed to suspend async: error -110 Feb 07 12:02:24 pm-cpp kernel: PM: Some devices failed to suspend, or early wake event detected I am able to suspend by shutting down wifi and removing the mt7925e and related kernel modules: sudo nano /usr/lib/systemd/system-sleep/mt7925e-sleep #!/bin/sh case "$1/$2" in pre/*) /usr/bin/nmcli radio wifi off >/dev/null 2>&1 || true /usr/sbin/modprobe -r mt7925e mt76_connac_lib mt76 >/dev/null 2>&1 || true ;; post/*) /usr/sbin/modprobe mt7925e >/dev/null 2>&1 || true /usr/bin/nmcli radio wifi on >/dev/null 2>&1 || true ;; esac exit 0 The above, however, may give me problems resuming remote connections. An alternative is to return to my older kernel, but that loses security updates, I presume. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-100-generic 6.8.0-100.100 ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12 Uname: Linux 6.8.0-100-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: pm 3631 F.... wireplumber /dev/snd/pcmC1D0p: pm 3629 F...m pipewire /dev/snd/controlC0: pm 3631 F.... wireplumber /dev/snd/seq: pm 3629 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 7 12:59:42 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (413 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro quiet cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot splash resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=1 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-100-generic N/A linux-backports-modules-6.8.0-100-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.23 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2025 dmi.bios.release: 22.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2207 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 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.:bvr2207:bd07/18/2025:br22.7:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141198/+subscriptions
[Bug 2141198] Re: Suspend failure with mt7925e after kernel upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2141198 Title: Suspend failure with mt7925e after kernel upgrade Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: Last night, I updated to kernel 6.8.0-100.100 from kernel 6.8.0-94.96 and immediately shut down the computer. Today I booted the computer, read some things for a few minutes and tried to suspend, which failed repeatedly. I had no such problem in the previous kernel. journalctl reported the following lines as the source of the problem: Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: Message 00020007 (seq 5) timeout Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend+0x0/0x2e0 [mt7925e] returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: failed to suspend async: error -110 Feb 07 12:02:24 pm-cpp kernel: PM: Some devices failed to suspend, or early wake event detected I am able to suspend by shutting down wifi and removing the mt7925e and related kernel modules: sudo nano /usr/lib/systemd/system-sleep/mt7925e-sleep #!/bin/sh case "$1/$2" in pre/*) /usr/bin/nmcli radio wifi off >/dev/null 2>&1 || true /usr/sbin/modprobe -r mt7925e mt76_connac_lib mt76 >/dev/null 2>&1 || true ;; post/*) /usr/sbin/modprobe mt7925e >/dev/null 2>&1 || true /usr/bin/nmcli radio wifi on >/dev/null 2>&1 || true ;; esac exit 0 The above, however, may give me problems resuming remote connections. An alternative is to return to my older kernel, but that loses security updates, I presume. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-100-generic 6.8.0-100.100 ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12 Uname: Linux 6.8.0-100-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: pm 3631 F.... wireplumber /dev/snd/pcmC1D0p: pm 3629 F...m pipewire /dev/snd/controlC0: pm 3631 F.... wireplumber /dev/snd/seq: pm 3629 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 7 12:59:42 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (413 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro quiet cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot splash resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=1 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-100-generic N/A linux-backports-modules-6.8.0-100-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.23 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2025 dmi.bios.release: 22.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2207 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 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.:bvr2207:bd07/18/2025:br22.7:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141198/+subscriptions
[Bug 2141198] Re: Suspend failure with mt7925e after kernel upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2141198 Title: Suspend failure with mt7925e after kernel upgrade Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: Last night, I updated to kernel 6.8.0-100.100 from kernel 6.8.0-94.96 and immediately shut down the computer. Today I booted the computer, read some things for a few minutes and tried to suspend, which failed repeatedly. I had no such problem in the previous kernel. journalctl reported the following lines as the source of the problem: Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: Message 00020007 (seq 5) timeout Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend+0x0/0x2e0 [mt7925e] returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110 Feb 07 12:02:24 pm-cpp kernel: mt7925e 0000:83:00.0: PM: failed to suspend async: error -110 Feb 07 12:02:24 pm-cpp kernel: PM: Some devices failed to suspend, or early wake event detected I am able to suspend by shutting down wifi and removing the mt7925e and related kernel modules: sudo nano /usr/lib/systemd/system-sleep/mt7925e-sleep #!/bin/sh case "$1/$2" in pre/*) /usr/bin/nmcli radio wifi off >/dev/null 2>&1 || true /usr/sbin/modprobe -r mt7925e mt76_connac_lib mt76 >/dev/null 2>&1 || true ;; post/*) /usr/sbin/modprobe mt7925e >/dev/null 2>&1 || true /usr/bin/nmcli radio wifi on >/dev/null 2>&1 || true ;; esac exit 0 The above, however, may give me problems resuming remote connections. An alternative is to return to my older kernel, but that loses security updates, I presume. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-100-generic 6.8.0-100.100 ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12 Uname: Linux 6.8.0-100-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: pm 3631 F.... wireplumber /dev/snd/pcmC1D0p: pm 3629 F...m pipewire /dev/snd/controlC0: pm 3631 F.... wireplumber /dev/snd/seq: pm 3629 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 7 12:59:42 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (413 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro quiet cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot splash resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=1 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-100-generic N/A linux-backports-modules-6.8.0-100-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.23 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2025 dmi.bios.release: 22.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2207 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 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.:bvr2207:bd07/18/2025:br22.7:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141198/+subscriptions
[Bug 2157666] Re: After I suspend my PC, after a while it didn't interrupt the sleep mode but it's on
** Summary changed: - After I suspend my PC, after a while it didn't interrupt the suspension but it's on + After I suspend my PC, after a while it didn't interrupt the sleep mode but it's on -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157666 Title: After I suspend my PC, after a while it didn't interrupt the sleep mode but it's on Status in linux package in Ubuntu: New Bug description: Hello I was in Ubuntu MATE 24.04 LTS and after I suspend my pc, after 1 hour I opened my laptop and the screen was completely off and just the power button was enlighted, the keyboard was off too. So I had to force the shut-down. An user told me to do this commands (log.txt) and since I was in s3 deep (kernel: PM: suspend entry (deep)) I had to do these steps and I confirm the problem disappeared: sudo nano /etc/default/grub then I had to add near GRUB_CMDLINE_LINUX_DEFAULT in the quotes: "mem_sleep_default=s2idle" and since I use radeon I had to add always in the quotes "radeon.dpm=0" Then sudo update-grub I don't know if it is a solution or a workaround and if can be part of a new update of Ubuntu for my machine, but the problem is gone. My PC is a Lenovo B575e; GPU: AMD ATI Radeon HD 7310; CPU: AMD E1-1500 APU (2) @ 1.480GHz; 8GB of RAM ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-124-generic 6.8.0-124.124 ProcVersionSignature: Ubuntu 6.8.0-124.124-generic 6.8.12 Uname: Linux 6.8.0-124-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu-mate.seed ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.183.01-0ubuntu0.22.04.1_i386.deb ./pool/universe/u/ubiquity-slideshow-ubuntu/oem-config-slideshow-ubuntu-mate_181.1_all.deb CasperMD5CheckResult: fail CurrentDesktop: MATE Date: Fri Jun 19 22:01:26 2026 InstallationDate: Installed on 2026-06-15 (4 days ago) InstallationMedia: Ubuntu-MATE 22.04.5 LTS "Jammy Jellyfish" - Release amd64 (20240911.1) MachineType: LENOVO 36852BG ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-124-generic root=UUID=4cab68f6-e1b9-40fc-8168-0a1a63fd3e75 ro quiet splash amd_iommu=off 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-124-generic N/A linux-backports-modules-6.8.0-124-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2026-06-15 (4 days ago) dmi.bios.date: 12/26/2012 dmi.bios.release: 1.6 dmi.bios.vendor: LENOVO dmi.bios.version: HPET68WW(1.06) dmi.board.asset.tag: Not Available dmi.board.name: 36852BG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHPET68WW(1.06):bd12/26/2012:br1.6:svnLENOVO:pn36852BG:pvrLenovoB575e:rvnLENOVO:rn36852BG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3685: dmi.product.family: Lenovo B575e dmi.product.name: 36852BG dmi.product.sku: LENOVO_MT_3685 dmi.product.version: Lenovo B575e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157666/+subscriptions
пятница
[Bug 2157682] Re: iwlwifi AX211 Microcode SW error on kernel 7.0 (regression from 6.17 / Ubuntu 25.10)
** Attachment added: "Last crash log (journalctl -k -b -1)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157682/+attachment/5978147/+files/last-crash.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157682 Title: iwlwifi AX211 Microcode SW error on kernel 7.0 (regression from 6.17 / Ubuntu 25.10) Status in linux package in Ubuntu: New Bug description: SUMMARY iwlwifi (Intel Wi-Fi 6E AX211) firmware crashes repeatedly with "Microcode SW error detected. Restarting 0x0." on kernel 7.0 (Ubuntu 26.04 LTS). Regression: the same hardware was fully stable on Ubuntu 25.10 (kernel 6.17). The crash makes the machine unusable within minutes of normal use, and is reliably triggered by network activity (mainly fetching mail in Thunderbird on multiple accounts). HARDWARE - Laptop: Lenovo Yoga Slim 6 14IAP8 (machine type 82WU) - CPU: Intel Alder Lake (12th gen, hybrid) - Wi-Fi: Intel Wi-Fi 6E AX211 160MHz (PCI 0000:00:14.3) - Detected crf-id 0x400410, cnv-id 0x80400 - BIOS: Lenovo KTCN39WW (2023-08-18) SOFTWARE - Ubuntu 26.04 LTS (upgraded from 25.10) - Affected kernels: 7.0.0-22-generic AND 7.0.0-15-generic (both crash identically) - Wi-Fi firmware: 89.123cf747.0 so-a0-gf-a0-89.ucode (op_mode iwlmvm) - linux-firmware: 20260319.git217ca6e4.1ubuntu (latest available) CRASH SIGNATURE iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. WARNING: drivers/net/wireless/intel/iwlwifi/iwl-trans.h:1097 at iwl_pcie_irq_handle_error+0x1ba/0x200 [iwlwifi] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE Also observed just before the crash: iwlwifi 0000:00:14.3: [0] Got MSI-X interrupt before we have Rx queues "REGRESSION" : SOME DETAILS - Ubuntu 25.10 with kernel 6.17.0-x: STABLE, no Wi-Fi crashes. - After upgrade to Ubuntu 26.04 (kernel 7.0.0-x): crashes within minutes, every session. - Identical crash on both 7.0.0-15 and 7.0.0-22, so it is not specific to a single 7.0 build. WORKAROUNDS TESTED (none resolved the crash) - intel_iommu=off : removed the accompanying DMAR/IOMMU faults from the log, but the iwlwifi Microcode SW error still occurs. - iommu=pt : same result (DMAR faults gone, Wi-Fi crash remains). - modprobe options iwlwifi power_save=0 uapsd_disable=1 11n_disable=8 : no effect on the crash. - Booting the older installed kernel (7.0.0-15): same crash. The DMAR/IOMMU faults therefore appear to be a side effect, not the root cause. The root cause is the iwlwifi/firmware initialization failure (IML/ROM error, FSEQ_ERROR_CODE) on the 7.0 kernel. EXPECTED Wi-Fi remains stable under normal use, as it did on kernel 6.17 (Ubuntu 25.10). ACTUAL Repeated iwlwifi microcode crashes, Wi-Fi drops and full system instability within minutes. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: nicolas 5182 F.... pipewire nicolas 5202 F.... wireplumber /dev/snd/seq: nicolas 5182 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 03:38:54 2026 InstallationDate: Installed on 2025-02-06 (498 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: LENOVO 82WU ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=3b9eac6f-0152-405e-9800-5d424a52c8ed ro quiet splash iommu=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-19 (32 days ago) dmi.bios.date: 08/18/2023 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: KTCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 6 14IAP8 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrKTCN39WW:bd08/18/2023:br1.39:efr1.39:svnLENOVO:pn82WU:pvrYogaSlim614IAP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrYogaSlim614IAP8:skuLENOVO_MT_82WU_BU_idea_FM_YogaSlim614IAP8:pfaYogaSlim614IAP8: dmi.product.family: Yoga Slim 6 14IAP8 dmi.product.name: 82WU dmi.product.sku: LENOVO_MT_82WU_BU_idea_FM_Yoga Slim 6 14IAP8 dmi.product.version: Yoga Slim 6 14IAP8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157682/+subscriptions
[Bug 2157682] Re: iwlwifi AX211 Microcode SW error on kernel 7.0 (regression from 6.17 / Ubuntu 25.10)
** Description changed: SUMMARY iwlwifi (Intel Wi-Fi 6E AX211) firmware crashes repeatedly with "Microcode SW error detected. Restarting 0x0." on kernel 7.0 (Ubuntu 26.04 LTS). Regression: the same hardware was fully stable on Ubuntu 25.10 (kernel 6.17). The crash makes the machine unusable within minutes of normal use, and is reliably triggered by network - activity (e.g. fetching mail in Thunderbird). + activity (mainly fetching mail in Thunderbird on multiple accounts). HARDWARE - Laptop: Lenovo Yoga Slim 6 14IAP8 (machine type 82WU) - CPU: Intel Alder Lake (12th gen, hybrid) - Wi-Fi: Intel Wi-Fi 6E AX211 160MHz (PCI 0000:00:14.3) - - Detected crf-id 0x400410, cnv-id 0x80400 + - Detected crf-id 0x400410, cnv-id 0x80400 - BIOS: Lenovo KTCN39WW (2023-08-18) SOFTWARE - Ubuntu 26.04 LTS (upgraded from 25.10) - Affected kernels: 7.0.0-22-generic AND 7.0.0-15-generic - (both crash identically) + (both crash identically) - Wi-Fi firmware: 89.123cf747.0 so-a0-gf-a0-89.ucode (op_mode iwlmvm) - linux-firmware: 20260319.git217ca6e4.1ubuntu (latest available) CRASH SIGNATURE iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. WARNING: drivers/net/wireless/intel/iwlwifi/iwl-trans.h:1097 - at iwl_pcie_irq_handle_error+0x1ba/0x200 [iwlwifi] + at iwl_pcie_irq_handle_error+0x1ba/0x200 [iwlwifi] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE Also observed just before the crash: iwlwifi 0000:00:14.3: [0] Got MSI-X interrupt before we have Rx queues - REGRESSION DETAILS + "REGRESSION" : SOME DETAILS - Ubuntu 25.10 with kernel 6.17.0-x: STABLE, no Wi-Fi crashes. - After upgrade to Ubuntu 26.04 (kernel 7.0.0-x): crashes within - minutes, every session. + minutes, every session. - Identical crash on both 7.0.0-15 and 7.0.0-22, so it is not - specific to a single 7.0 build. + specific to a single 7.0 build. WORKAROUNDS TESTED (none resolved the crash) - intel_iommu=off : removed the accompanying DMAR/IOMMU faults from - the log, but the iwlwifi Microcode SW error still occurs. + the log, but the iwlwifi Microcode SW error still occurs. - iommu=pt : same result (DMAR faults gone, Wi-Fi crash remains). - modprobe options iwlwifi power_save=0 uapsd_disable=1 11n_disable=8 : - no effect on the crash. + no effect on the crash. - Booting the older installed kernel (7.0.0-15): same crash. The DMAR/IOMMU faults therefore appear to be a side effect, not the root cause. The root cause is the iwlwifi/firmware initialization failure (IML/ROM error, FSEQ_ERROR_CODE) on the 7.0 kernel. EXPECTED Wi-Fi remains stable under normal use, as it did on kernel 6.17 (Ubuntu 25.10). ACTUAL Repeated iwlwifi microcode crashes, Wi-Fi drops and full system instability within minutes. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC0: nicolas 5182 F.... pipewire - nicolas 5202 F.... wireplumber - /dev/snd/seq: nicolas 5182 F.... pipewire + USER PID ACCESS COMMAND + /dev/snd/controlC0: nicolas 5182 F.... pipewire + nicolas 5202 F.... wireplumber + /dev/snd/seq: nicolas 5182 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 03:38:54 2026 InstallationDate: Installed on 2025-02-06 (498 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: LENOVO 82WU ProcEnviron: - LANG=fr_FR.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> + LANG=fr_FR.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=3b9eac6f-0152-405e-9800-5d424a52c8ed ro quiet splash iommu=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-19 (32 days ago) dmi.bios.date: 08/18/2023 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: KTCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 6 14IAP8 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrKTCN39WW:bd08/18/2023:br1.39:efr1.39:svnLENOVO:pn82WU:pvrYogaSlim614IAP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrYogaSlim614IAP8:skuLENOVO_MT_82WU_BU_idea_FM_YogaSlim614IAP8:pfaYogaSlim614IAP8: dmi.product.family: Yoga Slim 6 14IAP8 dmi.product.name: 82WU dmi.product.sku: LENOVO_MT_82WU_BU_idea_FM_Yoga Slim 6 14IAP8 dmi.product.version: Yoga Slim 6 14IAP8 dmi.sys.vendor: LENOVO -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157682 Title: iwlwifi AX211 Microcode SW error on kernel 7.0 (regression from 6.17 / Ubuntu 25.10) Status in linux package in Ubuntu: New Bug description: SUMMARY iwlwifi (Intel Wi-Fi 6E AX211) firmware crashes repeatedly with "Microcode SW error detected. Restarting 0x0." on kernel 7.0 (Ubuntu 26.04 LTS). Regression: the same hardware was fully stable on Ubuntu 25.10 (kernel 6.17). The crash makes the machine unusable within minutes of normal use, and is reliably triggered by network activity (mainly fetching mail in Thunderbird on multiple accounts). HARDWARE - Laptop: Lenovo Yoga Slim 6 14IAP8 (machine type 82WU) - CPU: Intel Alder Lake (12th gen, hybrid) - Wi-Fi: Intel Wi-Fi 6E AX211 160MHz (PCI 0000:00:14.3) - Detected crf-id 0x400410, cnv-id 0x80400 - BIOS: Lenovo KTCN39WW (2023-08-18) SOFTWARE - Ubuntu 26.04 LTS (upgraded from 25.10) - Affected kernels: 7.0.0-22-generic AND 7.0.0-15-generic (both crash identically) - Wi-Fi firmware: 89.123cf747.0 so-a0-gf-a0-89.ucode (op_mode iwlmvm) - linux-firmware: 20260319.git217ca6e4.1ubuntu (latest available) CRASH SIGNATURE iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. WARNING: drivers/net/wireless/intel/iwlwifi/iwl-trans.h:1097 at iwl_pcie_irq_handle_error+0x1ba/0x200 [iwlwifi] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE Also observed just before the crash: iwlwifi 0000:00:14.3: [0] Got MSI-X interrupt before we have Rx queues "REGRESSION" : SOME DETAILS - Ubuntu 25.10 with kernel 6.17.0-x: STABLE, no Wi-Fi crashes. - After upgrade to Ubuntu 26.04 (kernel 7.0.0-x): crashes within minutes, every session. - Identical crash on both 7.0.0-15 and 7.0.0-22, so it is not specific to a single 7.0 build. WORKAROUNDS TESTED (none resolved the crash) - intel_iommu=off : removed the accompanying DMAR/IOMMU faults from the log, but the iwlwifi Microcode SW error still occurs. - iommu=pt : same result (DMAR faults gone, Wi-Fi crash remains). - modprobe options iwlwifi power_save=0 uapsd_disable=1 11n_disable=8 : no effect on the crash. - Booting the older installed kernel (7.0.0-15): same crash. The DMAR/IOMMU faults therefore appear to be a side effect, not the root cause. The root cause is the iwlwifi/firmware initialization failure (IML/ROM error, FSEQ_ERROR_CODE) on the 7.0 kernel. EXPECTED Wi-Fi remains stable under normal use, as it did on kernel 6.17 (Ubuntu 25.10). ACTUAL Repeated iwlwifi microcode crashes, Wi-Fi drops and full system instability within minutes. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: nicolas 5182 F.... pipewire nicolas 5202 F.... wireplumber /dev/snd/seq: nicolas 5182 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 03:38:54 2026 InstallationDate: Installed on 2025-02-06 (498 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: LENOVO 82WU ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=3b9eac6f-0152-405e-9800-5d424a52c8ed ro quiet splash iommu=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-19 (32 days ago) dmi.bios.date: 08/18/2023 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: KTCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 6 14IAP8 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrKTCN39WW:bd08/18/2023:br1.39:efr1.39:svnLENOVO:pn82WU:pvrYogaSlim614IAP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrYogaSlim614IAP8:skuLENOVO_MT_82WU_BU_idea_FM_YogaSlim614IAP8:pfaYogaSlim614IAP8: dmi.product.family: Yoga Slim 6 14IAP8 dmi.product.name: 82WU dmi.product.sku: LENOVO_MT_82WU_BU_idea_FM_Yoga Slim 6 14IAP8 dmi.product.version: Yoga Slim 6 14IAP8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157682/+subscriptions
[Bug 2157683] [NEW] DMAR: [DMA Read NO_PASID] Request device [8b:00.0] fault addr 0xffffe000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear
Public bug reported: On an Intel platform where VT-d is brought up in scalable mode, the kdump/kexec crash kernel faults on legitimate device DMA. The Intel IOMMU has no present translation for the physical addresses devices use for DMA in the crash kernel, so driver fails to operate. This makes kdump unreliable: the crash kernel cannot complete normal device init / vmcore capture. The failure is NOT specific to one driver -- two unrelated vendors' drivers fail identically on the same machine (a storage HBA and a Broadcom bnx2x NIC), both with the same scalable-mode DMAR fault. Disabling the IOMMU in the crash kernel (intel_iommu=off) fully resolves it (20/20 kdump iterations pass). Representative fault (storage HBA at 0000:8b:00.0): DMAR: DRHD: handling fault status reg 2 DMAR: [DMA Read NO_PASID] Request device [8b:00.0] fault addr 0xffffe000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear "SM:" + fault reason 0x71 indicates VT-d scalable mode and a not-present first-level paging entry for the requested address. ENVIRONMENT -------------------------------------------------------------------------------- OS: Ubuntu 24.04.4 LTS (Noble) Kernel (reproduces): 6.8.0-117-generic #117-Ubuntu SMP PREEMPT_DYNAMIC Arch: x86_64 System: HPE ProLiant DL380 Gen11 (Intel platform, VT-d) BIOS: 2.80 (also reproduced after update to 2.82) IOMMU: Intel VT-d, scalable mode active (see fault reason 0x71 / SM:) Crash tooling: kdump-tools (kexec crash kernel) Devices observed failing in crash kernel: - Storage HBA at PCI 0000:8b:00.0 (vendor driver "smartxlr") - Broadcom NIC at PCI 0000:23:00.1 (driver "bnx2x") IMPACT / SEVERITY -------------------------------------------------------------------------------- High. kdump is effectively non-functional on affected platforms because devices that need DMA during crash-kernel boot fail. Reproduced with two independent DMA-capable devices, so the impact is general, not device-specific. STEPS TO REPRODUCE -------------------------------------------------------------------------------- On an HPE ProLiant DL380 Gen11 (or any platform that enables Intel VT-d scalable mode) running Ubuntu 24.04.4 with linux 6.8.0-117-generic and kdump-tools: 1. Configure and enable kdump (kdump-tools). 2. Trigger a kernel crash, e.g.: echo 1 > /proc/sys/kernel/sysrq echo c > /proc/sysrq-trigger 3. Watch the crash-kernel console (serial/SOL). Note: an active I/O workload is NOT required. The original report had storage I/O running at crash time, but the failure also reproduces with no I/O workload. EXPECTED RESULT -------------------------------------------------------------------------------- With Intel VT-d enabled (scalable mode), the kdump crash kernel can perform device DMA -- either by carrying over the prior kernel's translations or safely re-establishing them -- so drivers initialize and the vmcore is captured. ACTUAL RESULT -------------------------------------------------------------------------------- The crash kernel's IOMMU has no present translation for device DMA buffers (fault reason 0x71, scalable mode). DMA is blocked and DMA-capable drivers fail. EVIDENCE -------------------------------------------------------------------------------- 1) The IOMMU fault address equals the exact physical address the driver passed. A debug build of the storage driver logged the buffer physaddr it hands the controller for its SIS->PQI init command, immediately before the fault: XlrInitSisBaseStructAddress(): BufferPhysAddress 0xffffe000 ... XlrSisSendSyncCmd(): command 0000001b Params[1]=0xffffe000 ... DMAR: DRHD: handling fault status reg 2 DMAR: [DMA Read NO_PASID] Request device [8b:00.0] fault addr 0xffffe000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear Driver passes 0xffffe000; IOMMU faults on 0xffffe000. The address is valid; the crash kernel simply has no present translation for it. 2) A second, unrelated device (bnx2x NIC) faults identically in the crash kernel: DMAR: [DMA Read NO_PASID] Request device [23:00.1] fault addr 0xff6b8000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear bnx2x: [bnx2x_issue_dmae_with_comp:563(ens2f1)]DMAE timeout! bnx2x: [bnx2x_write_dmae:611(ens2f1)]DMAE returned failure -1 ... (repeats for >90 s) ... bnx2x: [bnx2x_send_final_clnup:1423(ens2f1)]FW final cleanup did not succeed bnx2x: [bnx2x_panic_dump:929(ens2f1)]begin crash dump ---------------- Same fault reason (0x71, SM:), different vendor. Rules out a driver-specific defect; points at platform VT-d translation state in the crash kernel. 3) Disabling the IOMMU in the crash kernel resolves it. Adding intel_iommu=off to the CRASH KERNEL command line only (production kernel unchanged): 20 iterations run, 20 passed, 0 failed. 4) Does not reproduce on other kernels / platforms (same driver + same test): - Lenovo ThinkSystem SR650 V3, Ubuntu 24.04.4, 6.17.0-x-generic (HWE) -- PASS - HPE ProLiant DL385 Gen10 Plus, Debian 13, 6.12.x -- PASS - HPE ProLiant DL380 Gen10 Plus, Ubuntu 24.04.4, 6.8.0-124-generic -- PASS Consistent with a scalable-mode crash-kernel handling gap that depends on the platform enabling VT-d scalable mode. Notably 6.17 passes, suggesting a fix may already exist upstream that needs backporting to the Ubuntu 6.8 GA kernel. WORKAROUND -------------------------------------------------------------------------------- Append intel_iommu=off to the CRASH KERNEL command line only (kdump-tools): edit KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools (or /etc/default/grub.d/kdump-tools.cfg), then reload: sudo kdump-config unload && sudo kdump-config load Confirmed: 20/20 kdump iterations pass. This affects only the crash kernel; the production kernel keeps VT-d enabled. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157683 Title: DMAR: [DMA Read NO_PASID] Request device [8b:00.0] fault addr 0xffffe000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear Status in linux package in Ubuntu: New Bug description: On an Intel platform where VT-d is brought up in scalable mode, the kdump/kexec crash kernel faults on legitimate device DMA. The Intel IOMMU has no present translation for the physical addresses devices use for DMA in the crash kernel, so driver fails to operate. This makes kdump unreliable: the crash kernel cannot complete normal device init / vmcore capture. The failure is NOT specific to one driver -- two unrelated vendors' drivers fail identically on the same machine (a storage HBA and a Broadcom bnx2x NIC), both with the same scalable-mode DMAR fault. Disabling the IOMMU in the crash kernel (intel_iommu=off) fully resolves it (20/20 kdump iterations pass). Representative fault (storage HBA at 0000:8b:00.0): DMAR: DRHD: handling fault status reg 2 DMAR: [DMA Read NO_PASID] Request device [8b:00.0] fault addr 0xffffe000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear "SM:" + fault reason 0x71 indicates VT-d scalable mode and a not-present first-level paging entry for the requested address. ENVIRONMENT -------------------------------------------------------------------------------- OS: Ubuntu 24.04.4 LTS (Noble) Kernel (reproduces): 6.8.0-117-generic #117-Ubuntu SMP PREEMPT_DYNAMIC Arch: x86_64 System: HPE ProLiant DL380 Gen11 (Intel platform, VT-d) BIOS: 2.80 (also reproduced after update to 2.82) IOMMU: Intel VT-d, scalable mode active (see fault reason 0x71 / SM:) Crash tooling: kdump-tools (kexec crash kernel) Devices observed failing in crash kernel: - Storage HBA at PCI 0000:8b:00.0 (vendor driver "smartxlr") - Broadcom NIC at PCI 0000:23:00.1 (driver "bnx2x") IMPACT / SEVERITY -------------------------------------------------------------------------------- High. kdump is effectively non-functional on affected platforms because devices that need DMA during crash-kernel boot fail. Reproduced with two independent DMA-capable devices, so the impact is general, not device-specific. STEPS TO REPRODUCE -------------------------------------------------------------------------------- On an HPE ProLiant DL380 Gen11 (or any platform that enables Intel VT-d scalable mode) running Ubuntu 24.04.4 with linux 6.8.0-117-generic and kdump-tools: 1. Configure and enable kdump (kdump-tools). 2. Trigger a kernel crash, e.g.: echo 1 > /proc/sys/kernel/sysrq echo c > /proc/sysrq-trigger 3. Watch the crash-kernel console (serial/SOL). Note: an active I/O workload is NOT required. The original report had storage I/O running at crash time, but the failure also reproduces with no I/O workload. EXPECTED RESULT -------------------------------------------------------------------------------- With Intel VT-d enabled (scalable mode), the kdump crash kernel can perform device DMA -- either by carrying over the prior kernel's translations or safely re-establishing them -- so drivers initialize and the vmcore is captured. ACTUAL RESULT -------------------------------------------------------------------------------- The crash kernel's IOMMU has no present translation for device DMA buffers (fault reason 0x71, scalable mode). DMA is blocked and DMA-capable drivers fail. EVIDENCE -------------------------------------------------------------------------------- 1) The IOMMU fault address equals the exact physical address the driver passed. A debug build of the storage driver logged the buffer physaddr it hands the controller for its SIS->PQI init command, immediately before the fault: XlrInitSisBaseStructAddress(): BufferPhysAddress 0xffffe000 ... XlrSisSendSyncCmd(): command 0000001b Params[1]=0xffffe000 ... DMAR: DRHD: handling fault status reg 2 DMAR: [DMA Read NO_PASID] Request device [8b:00.0] fault addr 0xffffe000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear Driver passes 0xffffe000; IOMMU faults on 0xffffe000. The address is valid; the crash kernel simply has no present translation for it. 2) A second, unrelated device (bnx2x NIC) faults identically in the crash kernel: DMAR: [DMA Read NO_PASID] Request device [23:00.1] fault addr 0xff6b8000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear bnx2x: [bnx2x_issue_dmae_with_comp:563(ens2f1)]DMAE timeout! bnx2x: [bnx2x_write_dmae:611(ens2f1)]DMAE returned failure -1 ... (repeats for >90 s) ... bnx2x: [bnx2x_send_final_clnup:1423(ens2f1)]FW final cleanup did not succeed bnx2x: [bnx2x_panic_dump:929(ens2f1)]begin crash dump ---------------- Same fault reason (0x71, SM:), different vendor. Rules out a driver-specific defect; points at platform VT-d translation state in the crash kernel. 3) Disabling the IOMMU in the crash kernel resolves it. Adding intel_iommu=off to the CRASH KERNEL command line only (production kernel unchanged): 20 iterations run, 20 passed, 0 failed. 4) Does not reproduce on other kernels / platforms (same driver + same test): - Lenovo ThinkSystem SR650 V3, Ubuntu 24.04.4, 6.17.0-x-generic (HWE) -- PASS - HPE ProLiant DL385 Gen10 Plus, Debian 13, 6.12.x -- PASS - HPE ProLiant DL380 Gen10 Plus, Ubuntu 24.04.4, 6.8.0-124-generic -- PASS Consistent with a scalable-mode crash-kernel handling gap that depends on the platform enabling VT-d scalable mode. Notably 6.17 passes, suggesting a fix may already exist upstream that needs backporting to the Ubuntu 6.8 GA kernel. WORKAROUND -------------------------------------------------------------------------------- Append intel_iommu=off to the CRASH KERNEL command line only (kdump-tools): edit KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools (or /etc/default/grub.d/kdump-tools.cfg), then reload: sudo kdump-config unload && sudo kdump-config load Confirmed: 20/20 kdump iterations pass. This affects only the crash kernel; the production kernel keeps VT-d enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157683/+subscriptions
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
This fixed it for me: sudo apt install linux-oem-26.04 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Triaged Status in linux source package in Resolute: Triaged Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2157590] [NEW] Mic Mute LED not working on HP Laptop 15-fc0xxx (Board 8B2F) / Realtek ALC236
Public bug reported: Hello, I am running Ubuntu 26.04 on an HP Laptop 15-fc0xxx (Ryzen 3 7320U platform) and the physical microphone mute LED (on the F8 key) does not toggle or illuminate when the mic mute hotkey is pressed, even though the software mutes correctly. The standard 'hda::micmute' node is entirely missing from /sys/class/leds/. Here are the system details gathered from troubleshooting: - OS: Ubuntu 26.04 LTS - Kernel: 7.0.0-22-generic - Audio Codec: Realtek ALC236 (Subsystem Id: 0x103c8b2f) - Board ID: HP 8B2F (SKU: 946T5EA#UUG) Testing with evtest shows that 'HP WMI hotkeys' successfully registers EV_KEY / KEY_MICMUTE (code 248) on keypress, but the corresponding LED is not hooked up via the hp-wmi driver for this specific motherboard revision. Please consider adding a quirk mapping for Subsystem 0x103c8b2f / Board 8B2F to enable the mic mute LED trigger. Thank you! ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 26.04 alc236 alsa-driver amd-acp hp-wmi micmute-led ** Tags added: 26.04 alc236 alsa-driver hp-wmi micmute-led -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157590 Title: Mic Mute LED not working on HP Laptop 15-fc0xxx (Board 8B2F) / Realtek ALC236 Status in linux package in Ubuntu: New Bug description: Hello, I am running Ubuntu 26.04 on an HP Laptop 15-fc0xxx (Ryzen 3 7320U platform) and the physical microphone mute LED (on the F8 key) does not toggle or illuminate when the mic mute hotkey is pressed, even though the software mutes correctly. The standard 'hda::micmute' node is entirely missing from /sys/class/leds/. Here are the system details gathered from troubleshooting: - OS: Ubuntu 26.04 LTS - Kernel: 7.0.0-22-generic - Audio Codec: Realtek ALC236 (Subsystem Id: 0x103c8b2f) - Board ID: HP 8B2F (SKU: 946T5EA#UUG) Testing with evtest shows that 'HP WMI hotkeys' successfully registers EV_KEY / KEY_MICMUTE (code 248) on keypress, but the corresponding LED is not hooked up via the hp-wmi driver for this specific motherboard revision. Please consider adding a quirk mapping for Subsystem 0x103c8b2f / Board 8B2F to enable the mic mute LED trigger. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157590/+subscriptions
[Bug 2157584] Re: Kernel NULL pointer dereference in __queue_work via delayed_work_timer_fn on 7.0.0-22-generic (Ubuntu 26.04)
The crash matches a known workqueue state-machine bug fixed upstream by commit a7488f089bdfa87c4fef1744d4dca9f4f8b46f8b ("workqueue: Release PENDING in __queue_work() drain/destroy reject path"), authored by Breno Leitao, applied by Tejun Heo to wq/for-7.1-fixes on 2026-05-08, merged mainline via wq-for-7.1-rc3-fixes pull (2026-05-13). The bug: when delayed_work_timer_fn() -> __queue_work() hits the __WQ_DESTROYING | __WQ_DRAINING reject path, it WARNs and returns without clearing WORK_STRUCT_PENDING, leaving the work in an inconsistent state (PENDING=1, PWQ=0, entry empty). This matches our observed sequence: the WARNING at 17:44:49 was the reject path firing, and the NULL pointer dereference at 19:06:42 was the downstream consequence. An AUTOSEL backport to 7.0 stable was posted 2026-05-20 but has not landed in any released 7.0.x point release through 7.0.12 (2026-06-09) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157584 Title: Kernel NULL pointer dereference in __queue_work via delayed_work_timer_fn on 7.0.0-22-generic (Ubuntu 26.04) Status in linux package in Ubuntu: New Bug description: Package: linux Affects: Ubuntu 26.04 (resolute) Description A QEMU/KVM virtio guest running Ubuntu 26.04 with kernel 7.0.0-22-generic froze completely. The guest agent stopped responding, SSH timed out, and the VM required a virsh reset to recover. Investigation of the previous boot's journal revealed a kernel NULL pointer dereference in __queue_work, preceded by a WARNING at the same location on a separate occasion earlier in the same boot. This matches a known upstream workqueue use-after-free / NULL- deref pattern where delayed work is queued to a workqueue that has been destroyed (wq->cpu_pwq nullified), causing a NULL pointer dereference when the delayed timer fires and calls delayed_work_timer_fn -> __queue_work. Steps to reproduce Not reliably reproducible. The crash occurs when a delayed_work timer fires after the owning workqueue has been destroyed. The VM had been running for ~2 days under mixed workload (GNOME desktop, Docker containers with nftables/wireguard networking, JetBrains IDEs). Kernel version Linux ubuntu-dev-2024 7.0.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Mon May 25 15:54:34 UTC 2026 x86_64 GNU/Linux Package: linux-image-7.0.0-22-generic 7.0.0-22.22 Hardware QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2025.11-3ubuntu8 04/09/2026 16 vCPUs, 20GB RAM, virtio-blk + virtio-net + virtiofs + virtio-gpu Kernel command line BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=25a32e36-0866-4e02-b7ef-0703c8b6d784 ro zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=30 splash plymouth crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M Timeline 1. 17:44:49 — WARNING at kernel/workqueue.c:2350 on CPUs 4, 11, 8 (swapper/idle). VM continued running. 2. 19:06:42 — BUG: kernel NULL pointer dereference on CPUs 9 and 1 (swapper/idle). VM froze. Oops trace (19:06:42 event) BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page CPU: 9 UID: 0 PID: 0 Comm: swapper/9 Tainted: G W 7.0.0-22-generic #22-Ubuntu PREEMPT(lazy) Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2025.11-3ubuntu8 04/09/2026 RIP: 0010:__queue_work.part.0+0x190/0x390 Code: ... <0f> 0b e9 65 ff ff ff ... RSP: 0018:ffffcce10016cdd8 EFLAGS: 00010003 RAX: ffff8c35a542f2c0 RBX: ffff8c35a542f2b8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffcce10016ce10 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff8c392bab2680 R13: 0000000000002000 R14: ffff8c34c0386c00 R15: ffff8c34c0389200 FS: 0000000000000000(0000) GS:ffff8c3980880000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000072ea901a3fb8 CR3: 0000000199a02000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <IRQ> __queue_work+0x39/0xc0 ? __pfx_delayed_work_timer_fn+0x10/0x10 delayed_work_timer_fn+0x19/0x30 call_timer_fn+0x30/0x170 ? __pfx_delayed_work_timer_fn+0x10/0x10 __run_timers+0x1af/0x2c0 run_timer_softirq+0x8a/0x100 handle_softirqs+0xe1/0x360 __irq_exit_rcu+0x100/0x120 irq_exit_rcu+0xe/0x20 sysvec_apic_timer_interrupt+0x9f/0xd0 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1b/0x20 RIP: 0010:pv_native_safe_halt+0xb/0x10 ... arch_cpu_idle+0x9/0x10 default_idle_call+0x2f/0x130 cpuidle_idle_call+0x114/0x1f0 do_idle+0x94/0xf0 cpu_startup_entry+0x29/0x30 start_secondary+0x125/0x180 ? soft_restart_cpu+0x14/0x14 common_startup_64+0x13e/0x141 </TASK> ---[ end trace 0000000000000000 ]--- A second identical oops was logged simultaneously on CPU 1. WARNING trace (17:44:49 event, same boot, earlier) WARNING: kernel/workqueue.c:2350 at __queue_work.part.0+0x190/0x390, CPU#4: swapper/4/0 WARNING: kernel/workqueue.c:2350 at __queue_work.part.0+0x190/0x390, CPU#11: swapper/11/0 WARNING: kernel/workqueue.c:2350 at __queue_work.part.0+0x190/0x390, CPU#8: swapper/8/0 Modules linked in: nft_ct, wireguard, libcurve25519, ip6_udp_tunnel, udp_tunnel, nf_conntrack_netlink, xt_nat, xt_tcpudp, veth, xt_multiport, xt_conntrack, xt_MASQUERADE, xfrm_user, xfrm_algo, xt_set, ip_set, nft_chain_nat, nf_nat, nf_conntrack, nf_defrag_ipv6, nf_defrag_ipv4, nft_compat, nf_tables, virtiofs, serio_raw, vmw_vsock_virtio_transport, virtio_dma_buf, vsock, virtio_rng, autofs4, libahci, netconsole, virtio_gpu, psmouse, hid_generic, ahci, usbhid, hid Analysis The crash occurs in the timer interrupt path during CPU idle: 1. CPU is idle (pv_native_safe_halt / do_idle) 2. APIC timer interrupt fires 3. __run_timers expires a delayed_work timer 4. delayed_work_timer_fn calls __queue_work 5. __queue_work dereferences a NULL pointer (pwq/pool is NULL) The Tainted [W] flag confirms a prior WARN at the same code path. The simultaneous occurrence on two CPUs suggests a race condition during workqueue teardown — a delayed_work timer fires after the workqueue's cpu_pwq has been nullified by destroy_workqueue(). This matches the upstream pattern described in: - Tim Van Patten's patch "workqueue: Prevent delayed work UAF kernel panic" (June 2024): LKML — adds NULL check for pwq/pool in __queue_work - Tejun Heo's response and removal of WARN_ON_ONCE(!wq) (March 2026): GitHub mirror Related bugs - Launchpad #2068103 — same pattern on kernel 6.8.0-35 (workqueue.c:1790) - bugzilla.kernel.org #218288 — same pattern on kernel 6.6 (workqueue.c:1638) Availability of fix Kernel 7.0.0-26.26 is in resolute-proposed and includes upstream stable releases v7.0.1 through v7.0.6. It is unclear whether the workqueue UAF fix is included in those stable releases. The guest currently has 7.0.0-22.22 installed with no upgradable kernel in updates/security. Workaround None known. Rebooting after a virsh reset recovers the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157584/+subscriptions