[Bug 2172736] Re: Ubuntu 26.04: NVIDIA DKMS failure leaves kernel 7.0.0-42 without initramfs, causing VFS panic on reboot

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/2172736 Title: Ubuntu 26.04: NVIDIA DKMS failure leaves kernel 7.0.0-42 without initramfs, causing VFS panic on reboot Status in linux package in Ubuntu: Confirmed Bug description: # Kernel 7.0.0-42 installed without initramfs after NVIDIA DKMS failure, causing VFS kernel panic on two systems ### Summary After upgrading to kernel `7.0.0-42-generic` on Ubuntu 26.04, two independent systems became unable to boot the new kernel, both failing with: ``` Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ``` Investigation revealed that `/boot/vmlinuz-7.0.0-42-generic` was present on both systems, but the corresponding `/boot/initrd.img-7.0.0-42-generic` was missing. Both machines encountered an NVIDIA DKMS compilation failure during the kernel update. This appears to have interrupted the kernel post- installation process before initramfs generation could complete. Both systems remain bootable using their previous kernels. ### Affected systems **System 1 — Desktop** - Ubuntu 26.04 - CPU: Intel Core i7-13700F - GPU: NVIDIA GeForce RTX 4070 - NVIDIA driver: 615.71.10 - Failing kernel: 7.0.0-42-generic - Working fallback: 7.0.0-34-generic **System 2 — Laptop** - Ubuntu 26.04 - Model: Lenovo Yoga Pro 7 14IMH9 - GPU: NVIDIA GeForce RTX 4050 - NVIDIA driver: 615.71.10 - Failing kernel: 7.0.0-42-generic - Working fallback: 7.0.0-38-generic Both systems use NVIDIA's official CUDA APT repository. ### Steps to reproduce 1. Start with a working Ubuntu 26.04 installation using NVIDIA 615.71.10 (`nvidia-driver-open` and `nvidia-dkms-open`). 2. Upgrade to kernel `7.0.0-42-generic` through APT. 3. NVIDIA DKMS fails to compile against the updated kernel. 4. The kernel package's post-installation script exits unsuccessfully. 5. Reboot into the newly installed kernel. 6. The system encounters a VFS kernel panic. This sequence occurred independently on both systems. ### Relevant installation errors During the kernel update: ``` Autoinstall of module nvidia/615.71.10 for kernel 7.0.0-42-generic (x86_64) Building module(s).........(bad exit status: 2) Error! Bad return status for module build on kernel: 7.0.0-42-generic (x86_64) Autoinstall on 7.0.0-42-generic succeeded for module(s) kvmfr. Autoinstall on 7.0.0-42-generic failed for module(s) nvidia(10). Error! One or more modules failed to install during autoinstall. run-parts: /etc/kernel/postinst.d/dkms exited with return code 1 dpkg: error processing package linux-image-7.0.0-42-generic (--configure): old linux-image-7.0.0-42-generic package postinst maintainer script subprocess failed with exit status 1 ``` The underlying NVIDIA compilation error, reproduced on both systems, is: ``` ././common/inc/nv-linux.h:1270:34: error: field ‘cxlds’ has incomplete type 1270 | struct cxl_dev_state cxlds; | ^~~~~ ``` The NVIDIA compatibility issue has been reported separately: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1433 ### Missing initramfs On the desktop: ``` /boot/initrd.img-7.0.0-34-generic present /boot/vmlinuz-7.0.0-34-generic present /boot/vmlinuz-7.0.0-42-generic present /boot/initrd.img-7.0.0-42-generic missing ``` On the laptop: ``` /boot/initrd.img-7.0.0-38-generic present /boot/vmlinuz-7.0.0-38-generic present /boot/vmlinuz-7.0.0-42-generic present /boot/initrd.img-7.0.0-42-generic missing ``` On the laptop, `dpkg --audit` also reports: ``` Packages unpacked but not configured: nvidia-driver-open Packages half-configured: linux-image-7.0.0-42-generic nvidia-dkms-open ``` ### Expected behaviour A third-party DKMS compilation failure should not leave the system attempting to boot a kernel without the initramfs required to mount its root filesystem. Ideally, the kernel installation process should either: - Generate the initramfs despite the third-party DKMS failure, allowing the kernel to boot without the affected module; or - Prevent the incomplete kernel installation from becoming the default boot option, retaining the previously working kernel. ### Actual behaviour The NVIDIA DKMS failure causes `/etc/kernel/postinst.d/dkms` to exit with status 1, interrupting the kernel package configuration. The new kernel image remains present, but its initramfs is missing. On reboot, both machines attempt to boot the new kernel and panic because the root filesystem cannot be mounted. Recovery requires manually selecting a previous kernel through GRUB. ### Additional observations The issue has been independently reproduced on two systems with different NVIDIA GPUs and different working fallback kernels. This suggests the problem is not hardware-specific. Although the initial failure originates in NVIDIA's out-of-tree module, the resulting unbootable kernel appears to expose an error- handling or ordering problem in Ubuntu's kernel installation hooks. The main concern of this report is not the NVIDIA compilation incompatibility itself, but the fact that this failure can leave Ubuntu unable to boot normally after an otherwise routine kernel update. ### Possibly related bug This may be related to Launchpad bug #2141741, which describes a similar failure where a DKMS error interrupts kernel installation, leaving the initramfs missing. Although the symptoms appear similar, this report concerns Ubuntu 26.04, kernel 7.0.0-42-generic, and NVIDIA 615.71.10. I have reproduced the issue on two independent machines. https://bugs.launchpad.net/bugs/2141741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172736/+subscriptions

[Bug 2172737] [NEW] Fallos SATA READ FPDMA QUEUED en Dell Inspiron 14-3467 con kernel 7.0.0-38; mitigados al desactivar NCQ

Public bug reported: ## Descripción del problema ### 1. Equipo afectado **Equipo:** Dell Inspiron 14-3467 **Sistema operativo:** Ubuntu 26.04.1 LTS **Kernel:** 7.0.0-38-generic **Controladora SATA:** Intel Sunrise Point-LP SATA Controller **Identificador PCI:** 8086:9d03 (rev 21) **Modo de almacenamiento:** AHCI **SSD:** Western Digital WD Green SATA de 480 GB **Sistema de archivos:** EXT4 ### 2. Descripción del fallo Después de instalar Ubuntu 26.04.1 LTS y realizar actualizaciones del sistema, experimenté problemas recurrentes de arranque. El sistema ingresaba en modo de emergencia debido a errores de lectura del almacenamiento y fallos en la comprobación del sistema de archivos. Los registros del kernel mostraban repetidamente: - `failed command: READ FPDMA QUEUED` - `ATA bus error` - `SError: { Proto TrStaTrns UnrecFIS }` - `hardreset failed` - `reset failed, giving up` Estas fallas provocaron corrupción del sistema de archivos EXT4 y dificultades para iniciar Ubuntu. ### 3. Diagnóstico realizado Se ejecutaron las pruebas de diagnóstico ePSA de Dell, incluida la prueba corta del SSD, que finalizó satisfactoriamente. Los atributos SMART reportaron un estado general correcto, temperatura de 37 °C y cero sectores reasignados. Posteriormente, utilizando Ubuntu desde una memoria USB, se realizó una lectura secuencial completa del SSD de 480 GB mediante `dd`, sin errores y con una velocidad promedio de aproximadamente 508 MB/s. Sin embargo, durante una verificación del sistema de archivos mediante `e2fsck`, volvieron a presentarse errores de comunicación SATA, operaciones READ FPDMA QUEUED fallidas y errores de entrada/salida. ### 4. Solución temporal aplicada Se realizó una prueba iniciando Ubuntu desde una memoria USB con el siguiente parámetro del kernel: `libata.force=noncq` Se confirmó que NCQ estaba desactivado mediante: `cat /sys/block/sda/device/queue_depth` Resultado: `1` Al repetir la comprobación EXT4 con NCQ desactivado, el proceso finalizó sin reproducir los errores SATA anteriores. Posteriormente se reparó el sistema de archivos mediante `e2fsck` y se realizó una nueva comprobación satisfactoria. El parámetro se incorporó permanentemente a GRUB: `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=noncq"` Después de aplicar el cambio, Ubuntu inició correctamente en dos arranques consecutivos. Los registros consultados mediante `dmesg` no mostraron nuevos errores SATA. ### 5. Observación adicional El sistema reporta un tamaño máximo de solicitud de entrada/salida de 4096 KB: `cat /sys/block/sda/queue/max_sectors_kb` Resultado: `4096` Se identificó un reporte posiblemente 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: steve-leon 2662 F.... wireplumber /dev/snd/seq: steve-leon 2656 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 22:53:42 2026 InstallationDate: Installed on 2026-10-27 (6 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Dell Inc. Inspiron 14-3467 ProcEnviron: LANG=es_ES.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-38-generic root=UUID=1839957c-beac-4177-864d-5f4e74090c00 ro quiet splash libata.force=noncq 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: 05/06/2021 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.1 dmi.board.name: 0M0Y79 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.1:bd05/06/2021:br2.14:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0M0Y79:rvrA00:cvnDellInc.:ct9:cvr:sku0789:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172737 Title: Fallos SATA READ FPDMA QUEUED en Dell Inspiron 14-3467 con kernel 7.0.0-38; mitigados al desactivar NCQ Status in linux package in Ubuntu: New Bug description: ## Descripción del problema ### 1. Equipo afectado **Equipo:** Dell Inspiron 14-3467 **Sistema operativo:** Ubuntu 26.04.1 LTS **Kernel:** 7.0.0-38-generic **Controladora SATA:** Intel Sunrise Point-LP SATA Controller **Identificador PCI:** 8086:9d03 (rev 21) **Modo de almacenamiento:** AHCI **SSD:** Western Digital WD Green SATA de 480 GB **Sistema de archivos:** EXT4 ### 2. Descripción del fallo Después de instalar Ubuntu 26.04.1 LTS y realizar actualizaciones del sistema, experimenté problemas recurrentes de arranque. El sistema ingresaba en modo de emergencia debido a errores de lectura del almacenamiento y fallos en la comprobación del sistema de archivos. Los registros del kernel mostraban repetidamente: - `failed command: READ FPDMA QUEUED` - `ATA bus error` - `SError: { Proto TrStaTrns UnrecFIS }` - `hardreset failed` - `reset failed, giving up` Estas fallas provocaron corrupción del sistema de archivos EXT4 y dificultades para iniciar Ubuntu. ### 3. Diagnóstico realizado Se ejecutaron las pruebas de diagnóstico ePSA de Dell, incluida la prueba corta del SSD, que finalizó satisfactoriamente. Los atributos SMART reportaron un estado general correcto, temperatura de 37 °C y cero sectores reasignados. Posteriormente, utilizando Ubuntu desde una memoria USB, se realizó una lectura secuencial completa del SSD de 480 GB mediante `dd`, sin errores y con una velocidad promedio de aproximadamente 508 MB/s. Sin embargo, durante una verificación del sistema de archivos mediante `e2fsck`, volvieron a presentarse errores de comunicación SATA, operaciones READ FPDMA QUEUED fallidas y errores de entrada/salida. ### 4. Solución temporal aplicada Se realizó una prueba iniciando Ubuntu desde una memoria USB con el siguiente parámetro del kernel: `libata.force=noncq` Se confirmó que NCQ estaba desactivado mediante: `cat /sys/block/sda/device/queue_depth` Resultado: `1` Al repetir la comprobación EXT4 con NCQ desactivado, el proceso finalizó sin reproducir los errores SATA anteriores. Posteriormente se reparó el sistema de archivos mediante `e2fsck` y se realizó una nueva comprobación satisfactoria. El parámetro se incorporó permanentemente a GRUB: `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=noncq"` Después de aplicar el cambio, Ubuntu inició correctamente en dos arranques consecutivos. Los registros consultados mediante `dmesg` no mostraron nuevos errores SATA. ### 5. Observación adicional El sistema reporta un tamaño máximo de solicitud de entrada/salida de 4096 KB: `cat /sys/block/sda/queue/max_sectors_kb` Resultado: `4096` Se identificó un reporte posiblemente 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: steve-leon 2662 F.... wireplumber /dev/snd/seq: steve-leon 2656 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 22:53:42 2026 InstallationDate: Installed on 2026-10-27 (6 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Dell Inc. Inspiron 14-3467 ProcEnviron: LANG=es_ES.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-38-generic root=UUID=1839957c-beac-4177-864d-5f4e74090c00 ro quiet splash libata.force=noncq 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: 05/06/2021 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.1 dmi.board.name: 0M0Y79 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.1:bd05/06/2021:br2.14:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0M0Y79:rvrA00:cvnDellInc.:ct9:cvr:sku0789:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172737/+subscriptions

[Bug 2141741] Re: 55-initrd.install silently exits 0 when initrd missing causing undetectable kernel panic on NVMe systems

I've encountered what appears to be a similar issue on Ubuntu 26.04 with kernel 7.0.0-42-generic. In my case, NVIDIA 615.71.10 fails to compile through DKMS, interrupting kernel post-installation and leaving the new kernel without its initramfs. This results in a VFS kernel panic on reboot. I've reproduced the complete failure on two independent systems and filed a separate bug report #2172736 with detailed logs and system information. This may be related to the issue described here, although the kernel version and failing DKMS module differ. I'll link the new bug report here for cross-reference. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172736 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2141741 Title: 55-initrd.install silently exits 0 when initrd missing causing undetectable kernel panic on NVMe systems Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in grub2 package in Debian: New Bug description: [ Impact ] When a kernel postinst hook fails (e.g. DKMS module build failure), the kernel package remains half-configured: vmlinuz is installed and /usr/lib/linux/triggers/<version> is present, but no matching initrd is generated. A subsequent update-grub invocation (such as during removal of an older kernel) scans /boot and generates a boot menuentry for the incomplete kernel without an initrd line. On systems where storage drivers (NVMe, SATA, SAS) are built as modules, booting this entry causes an immediate, undetectable kernel panic (VFS: Unable to mount root fs on unknown-block(0,0)). [ Fix ] In /etc/grub.d/10_linux, when inspecting a kernel where no initrd was found (test -z "${initrd_real}"), check if a pending kernel trigger marker exists in /usr/lib/linux/triggers/${version} or /usr/lib/linux/triggers/${alt_version}. If the trigger marker is present, skip generating a boot menuentry for that kernel image. This prevents update-grub from publishing unbootable kernels to grub.cfg. [ Test Plan ] 1. Simulate an incomplete kernel installation: sudo touch /boot/vmlinuz-9.9.0-test-generic sudo touch /usr/lib/linux/triggers/9.9.0-test-generic sudo rm -f /boot/initrd.img-9.9.0-test-generic 2. Run sudo update-grub. 3. Verify behavior: - Without fix: GRUB outputs "Found linux image: /boot/vmlinuz-9.9.0-test-generic" and writes a stanza lacking an initrd line. - With fix: GRUB outputs "Skipping linux image with pending post-installation trigger and no initrd: /boot/vmlinuz-9.9.0-test-generic", and no stanza is generated. 4. Clean up test files (sudo rm -f /boot/vmlinuz-9.9.0-test-generic /usr/lib/linux/triggers/9.9.0-test-generic) and verify standard installed kernels generate valid boot entries. [ Where problems could occur ] The check only triggers when both conditions are met: initrd_real is empty AND a trigger marker exists in /usr/lib/linux/triggers/. Custom kernels intentionally configured without an initrd do not have markers under /usr/lib/linux/triggers/ and continue to work as before. If a kernel postinst script fails to clean up its trigger marker after a successful run, that kernel would be skipped until the stale marker is removed. [ Other Info ] - Debian BTS bug: https://bugs.debian.org/1151014 - Development series (stonking): debdiff prepared against 2.14-2ubuntu3 (version 2.14-2ubuntu4). - Stable SRU (noble): debdiff prepared against 2.12-1ubuntu7.3 (version 2.12-1ubuntu7.4). - PPA test builds: ppa:steelf/ppa (grub2 2.14-2ubuntu4~ppa1, grub2 2.12-1ubuntu7.4~ppa1). --- [ Original Report ] ENVIRONMENT: - Ubuntu 24.04 Noble (HWE kernel) - systemd version: 255 (255.4-1ubuntu8.10) - Kernel: 6.17.0-14-generic - Storage: NVMe SSD - File: /usr/lib/kernel/install.d/55-initrd.install - Package owner: systemd (confirmed via dpkg -S) BUG: When initrd generation fails or is skipped during kernel installation, 55-initrd.install detects the missing initrd but exits 0 (success) instead of exit 1 (failure). Relevant code in 55-initrd.install (line 26): if [ -e "$INITRD_SRC" ]; then ln -fs "$INITRD_SRC" "$KERNEL_INSTALL_STAGING_AREA" else echo "$INITRD_SRC does not exist, not installing an initrd" fi exit 0 <- BUG IS HERE This silent success causes GRUB to write a boot entry for a kernel with no initrd, with zero warning to the user. HOW THIS CAUSES KERNEL PANIC: Ubuntu's kernel config has CONFIG_BLK_DEV_NVME=m meaning the NVMe storage driver exists ONLY as a module inside initramfs. Without initramfs: - NVMe driver never loads - Kernel cannot see any storage device - Results in: VFS: Unable to mount root fs on unknown-block(0,0) - KERNEL PANIC on every boot - silent, no warning given HOW I TRIGGERED THIS: virtualbox-dkms 7.0.16 (dfsg) fails to build for kernel 6.17 due to missing VBox/cdefs.h header. DKMS exits code 11. run-parts stops alphabetically - 'd' (dkms) runs before 'i' (initramfs-tools) - so initramfs is never generated. 55-initrd.install then silently exits 0 -> GRUB creates unbootable boot entry -> KERNEL PANIC on reboot. This failed silently 3 days in a row (Feb 11, 12, 13 2026) confirmed in /var/log/dpkg.log and /var/log/apt/term.log. PROPOSED FIX: Change line 26 of 55-initrd.install from: exit 0 to: exit 1 When initrd is missing, this should be a HARD FAILURE not a silent warning. This would cause apt to report the error visibly and prevent GRUB from creating an unbootable boot entry. RELATED BUG: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2136499 (virtualbox-dkms FTBFS triggers this silent failure) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2141741/+subscriptions

[Bug 2172736] [NEW] Ubuntu 26.04: NVIDIA DKMS failure leaves kernel 7.0.0-42 without initramfs, causing VFS panic on reboot

Public bug reported: # Kernel 7.0.0-42 installed without initramfs after NVIDIA DKMS failure, causing VFS kernel panic on two systems ### Summary After upgrading to kernel `7.0.0-42-generic` on Ubuntu 26.04, two independent systems became unable to boot the new kernel, both failing with: ``` Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ``` Investigation revealed that `/boot/vmlinuz-7.0.0-42-generic` was present on both systems, but the corresponding `/boot/initrd.img-7.0.0-42-generic` was missing. Both machines encountered an NVIDIA DKMS compilation failure during the kernel update. This appears to have interrupted the kernel post- installation process before initramfs generation could complete. Both systems remain bootable using their previous kernels. ### Affected systems **System 1 — Desktop** - Ubuntu 26.04 - CPU: Intel Core i7-13700F - GPU: NVIDIA GeForce RTX 4070 - NVIDIA driver: 615.71.10 - Failing kernel: 7.0.0-42-generic - Working fallback: 7.0.0-34-generic **System 2 — Laptop** - Ubuntu 26.04 - Model: Lenovo Yoga Pro 7 14IMH9 - GPU: NVIDIA GeForce RTX 4050 - NVIDIA driver: 615.71.10 - Failing kernel: 7.0.0-42-generic - Working fallback: 7.0.0-38-generic Both systems use NVIDIA's official CUDA APT repository. ### Steps to reproduce 1. Start with a working Ubuntu 26.04 installation using NVIDIA 615.71.10 (`nvidia-driver-open` and `nvidia-dkms-open`). 2. Upgrade to kernel `7.0.0-42-generic` through APT. 3. NVIDIA DKMS fails to compile against the updated kernel. 4. The kernel package's post-installation script exits unsuccessfully. 5. Reboot into the newly installed kernel. 6. The system encounters a VFS kernel panic. This sequence occurred independently on both systems. ### Relevant installation errors During the kernel update: ``` Autoinstall of module nvidia/615.71.10 for kernel 7.0.0-42-generic (x86_64) Building module(s).........(bad exit status: 2) Error! Bad return status for module build on kernel: 7.0.0-42-generic (x86_64) Autoinstall on 7.0.0-42-generic succeeded for module(s) kvmfr. Autoinstall on 7.0.0-42-generic failed for module(s) nvidia(10). Error! One or more modules failed to install during autoinstall. run-parts: /etc/kernel/postinst.d/dkms exited with return code 1 dpkg: error processing package linux-image-7.0.0-42-generic (--configure): old linux-image-7.0.0-42-generic package postinst maintainer script subprocess failed with exit status 1 ``` The underlying NVIDIA compilation error, reproduced on both systems, is: ``` ././common/inc/nv-linux.h:1270:34: error: field ‘cxlds’ has incomplete type 1270 | struct cxl_dev_state cxlds; | ^~~~~ ``` The NVIDIA compatibility issue has been reported separately: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1433 ### Missing initramfs On the desktop: ``` /boot/initrd.img-7.0.0-34-generic present /boot/vmlinuz-7.0.0-34-generic present /boot/vmlinuz-7.0.0-42-generic present /boot/initrd.img-7.0.0-42-generic missing ``` On the laptop: ``` /boot/initrd.img-7.0.0-38-generic present /boot/vmlinuz-7.0.0-38-generic present /boot/vmlinuz-7.0.0-42-generic present /boot/initrd.img-7.0.0-42-generic missing ``` On the laptop, `dpkg --audit` also reports: ``` Packages unpacked but not configured: nvidia-driver-open Packages half-configured: linux-image-7.0.0-42-generic nvidia-dkms-open ``` ### Expected behaviour A third-party DKMS compilation failure should not leave the system attempting to boot a kernel without the initramfs required to mount its root filesystem. Ideally, the kernel installation process should either: - Generate the initramfs despite the third-party DKMS failure, allowing the kernel to boot without the affected module; or - Prevent the incomplete kernel installation from becoming the default boot option, retaining the previously working kernel. ### Actual behaviour The NVIDIA DKMS failure causes `/etc/kernel/postinst.d/dkms` to exit with status 1, interrupting the kernel package configuration. The new kernel image remains present, but its initramfs is missing. On reboot, both machines attempt to boot the new kernel and panic because the root filesystem cannot be mounted. Recovery requires manually selecting a previous kernel through GRUB. ### Additional observations The issue has been independently reproduced on two systems with different NVIDIA GPUs and different working fallback kernels. This suggests the problem is not hardware-specific. Although the initial failure originates in NVIDIA's out-of-tree module, the resulting unbootable kernel appears to expose an error-handling or ordering problem in Ubuntu's kernel installation hooks. The main concern of this report is not the NVIDIA compilation incompatibility itself, but the fact that this failure can leave Ubuntu unable to boot normally after an otherwise routine kernel update. ### Possibly related bug This may be related to Launchpad bug #2141741, which describes a similar failure where a DKMS error interrupts kernel installation, leaving the initramfs missing. Although the symptoms appear similar, this report concerns Ubuntu 26.04, kernel 7.0.0-42-generic, and NVIDIA 615.71.10. I have reproduced the issue on two independent machines. https://bugs.launchpad.net/bugs/2141741 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Kernel 7.0.0-42 installed without initramfs after NVIDIA DKMS failure, causing VFS kernel panic on two systems + Ubuntu 26.04: NVIDIA DKMS failure leaves kernel 7.0.0-42 without initramfs, causing VFS panic on reboot -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172736 Title: Ubuntu 26.04: NVIDIA DKMS failure leaves kernel 7.0.0-42 without initramfs, causing VFS panic on reboot Status in linux package in Ubuntu: New Bug description: # Kernel 7.0.0-42 installed without initramfs after NVIDIA DKMS failure, causing VFS kernel panic on two systems ### Summary After upgrading to kernel `7.0.0-42-generic` on Ubuntu 26.04, two independent systems became unable to boot the new kernel, both failing with: ``` Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ``` Investigation revealed that `/boot/vmlinuz-7.0.0-42-generic` was present on both systems, but the corresponding `/boot/initrd.img-7.0.0-42-generic` was missing. Both machines encountered an NVIDIA DKMS compilation failure during the kernel update. This appears to have interrupted the kernel post- installation process before initramfs generation could complete. Both systems remain bootable using their previous kernels. ### Affected systems **System 1 — Desktop** - Ubuntu 26.04 - CPU: Intel Core i7-13700F - GPU: NVIDIA GeForce RTX 4070 - NVIDIA driver: 615.71.10 - Failing kernel: 7.0.0-42-generic - Working fallback: 7.0.0-34-generic **System 2 — Laptop** - Ubuntu 26.04 - Model: Lenovo Yoga Pro 7 14IMH9 - GPU: NVIDIA GeForce RTX 4050 - NVIDIA driver: 615.71.10 - Failing kernel: 7.0.0-42-generic - Working fallback: 7.0.0-38-generic Both systems use NVIDIA's official CUDA APT repository. ### Steps to reproduce 1. Start with a working Ubuntu 26.04 installation using NVIDIA 615.71.10 (`nvidia-driver-open` and `nvidia-dkms-open`). 2. Upgrade to kernel `7.0.0-42-generic` through APT. 3. NVIDIA DKMS fails to compile against the updated kernel. 4. The kernel package's post-installation script exits unsuccessfully. 5. Reboot into the newly installed kernel. 6. The system encounters a VFS kernel panic. This sequence occurred independently on both systems. ### Relevant installation errors During the kernel update: ``` Autoinstall of module nvidia/615.71.10 for kernel 7.0.0-42-generic (x86_64) Building module(s).........(bad exit status: 2) Error! Bad return status for module build on kernel: 7.0.0-42-generic (x86_64) Autoinstall on 7.0.0-42-generic succeeded for module(s) kvmfr. Autoinstall on 7.0.0-42-generic failed for module(s) nvidia(10). Error! One or more modules failed to install during autoinstall. run-parts: /etc/kernel/postinst.d/dkms exited with return code 1 dpkg: error processing package linux-image-7.0.0-42-generic (--configure): old linux-image-7.0.0-42-generic package postinst maintainer script subprocess failed with exit status 1 ``` The underlying NVIDIA compilation error, reproduced on both systems, is: ``` ././common/inc/nv-linux.h:1270:34: error: field ‘cxlds’ has incomplete type 1270 | struct cxl_dev_state cxlds; | ^~~~~ ``` The NVIDIA compatibility issue has been reported separately: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1433 ### Missing initramfs On the desktop: ``` /boot/initrd.img-7.0.0-34-generic present /boot/vmlinuz-7.0.0-34-generic present /boot/vmlinuz-7.0.0-42-generic present /boot/initrd.img-7.0.0-42-generic missing ``` On the laptop: ``` /boot/initrd.img-7.0.0-38-generic present /boot/vmlinuz-7.0.0-38-generic present /boot/vmlinuz-7.0.0-42-generic present /boot/initrd.img-7.0.0-42-generic missing ``` On the laptop, `dpkg --audit` also reports: ``` Packages unpacked but not configured: nvidia-driver-open Packages half-configured: linux-image-7.0.0-42-generic nvidia-dkms-open ``` ### Expected behaviour A third-party DKMS compilation failure should not leave the system attempting to boot a kernel without the initramfs required to mount its root filesystem. Ideally, the kernel installation process should either: - Generate the initramfs despite the third-party DKMS failure, allowing the kernel to boot without the affected module; or - Prevent the incomplete kernel installation from becoming the default boot option, retaining the previously working kernel. ### Actual behaviour The NVIDIA DKMS failure causes `/etc/kernel/postinst.d/dkms` to exit with status 1, interrupting the kernel package configuration. The new kernel image remains present, but its initramfs is missing. On reboot, both machines attempt to boot the new kernel and panic because the root filesystem cannot be mounted. Recovery requires manually selecting a previous kernel through GRUB. ### Additional observations The issue has been independently reproduced on two systems with different NVIDIA GPUs and different working fallback kernels. This suggests the problem is not hardware-specific. Although the initial failure originates in NVIDIA's out-of-tree module, the resulting unbootable kernel appears to expose an error- handling or ordering problem in Ubuntu's kernel installation hooks. The main concern of this report is not the NVIDIA compilation incompatibility itself, but the fact that this failure can leave Ubuntu unable to boot normally after an otherwise routine kernel update. ### Possibly related bug This may be related to Launchpad bug #2141741, which describes a similar failure where a DKMS error interrupts kernel installation, leaving the initramfs missing. Although the symptoms appear similar, this report concerns Ubuntu 26.04, kernel 7.0.0-42-generic, and NVIDIA 615.71.10. I have reproduced the issue on two independent machines. https://bugs.launchpad.net/bugs/2141741 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172736/+subscriptions

[Bug 2170904] Re: Regression: System hangs on resume from suspend with 7.0.0-38-generic, works correctly with 7.0.0-34-generic

Hi Changwei, Just following up from my post a few weeks ago - any updates worth sharing? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170904 Title: Regression: System hangs on resume from suspend with 7.0.0-38-generic, works correctly with 7.0.0-34-generic Status in linux package in Ubuntu: Incomplete Bug description: I'm raising this bug to report an issue (possible regression) in the 7.0.0-38 kernel that causes resume from suspend to fail. Relevant details below, and extensive logs attached. Hardware: - NVIDIA GTX 1080 - Zorin OS 18.1 (based on Ubuntu Noble) - NVIDIA 580.178.04 Regression: - Suspend/resume works on 7.0.0-34 - Suspend/resume fails on 7.0.0-38 Observed behavior: - System enters suspend - Journal shows "PM: suspend entry (deep)" - System never resumes - Requires hard reset Testing performed: - Booted into 7.0.0-34 - suspend/resume work as-expected - Boot into 7.0.0-38 - suspend works, fails to resume - Boot into 24.04 live USB - suspend/resume work (though other, unrelated, issues are present) Regression: Yes Known-good kernel: 7.0.0-34-generic Known-bad kernel: 7.0.0-38-generic Hardware: NVIDIA GTX 1080 Tests performed: - deep suspend: fails - s2idle suspend: fails - identical hardware and userspace - previous kernel resumes correctly Result: Regression introduced between 7.0.0-34 and 7.0.0-38. Expected behavior: - Resume successfully from suspend on 7.0.0-38 as on 7.0.0-34 --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kadar 2105 F.... wireplumber /dev/snd/controlC1: kadar 2105 F.... wireplumber /dev/snd/seq: kadar 2102 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: zorin:GNOME DistroRelease: Zorin OS 18 InstallationDate: Installed on 2026-01-06 (286 days ago) InstallationMedia: Zorin-OS 18 Core 64bit MachineType: MSI MS-7977 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-34-generic root=UUID=a972fa59-1d1b-479e-90bb-237a51eafd14 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 7.0.0-34.34~24.04.1-generic 7.0.14 RelatedPackageVersions: linux-restricted-modules-7.0.0-34-generic N/A linux-backports-modules-7.0.0-34-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: noble Uname: Linux 7.0.0-34-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 06/26/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M5 (MS-7977) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd06/26/2018:br5.12:svnMSI:pnMS-7977:pvr1.0:rvnMSI:rnZ170AGAMINGM5(MS-7977):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7977 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170904/+subscriptions

[Bug 2172730] Re: Ubuntu 26.04 — Intel AX211 iwlwifi intermittent internet packet loss on home Wi-Fi, hotspot works

** 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/2172730 Title: Ubuntu 26.04 — Intel AX211 iwlwifi intermittent internet packet loss on home Wi-Fi, hotspot works Status in linux package in Ubuntu: New Bug description: I am experiencing severe intermittent internet connectivity problems on Ubuntu 26.04 with an Intel Wi-Fi 6E AX211 adapter using the iwlwifi driver. I had no problems on this computer using the same wi-fi network until approximately 1 month ago, when this problem was detected. Expected behavior: Internet connectivity should remain stable when connected to my home Wi-Fi network. Actual behavior: Wi-Fi remains associated with the access point. The local gateway (192.168.0.1) responds reliably, with 0% packet loss in extended testing. Internet connectivity intermittently fails, with packet loss ranging from approximately 13% to 100%. Sometimes the first 10–40 ping packets are lost, followed by a period of successful responses. When i restart ping with ping -c 120 1.1.1.1, packets are lost again at the beginning. DNS resolution can take over 30 seconds. HTTPS connections sometimes time out. The same computer works normally when connected to a mobile phone hotspot or on other wi fi networks, so this might be related to specific network (device). Other computers on the same home Wi-Fi work normally. Hardware and software: Ubuntu 26.04 Intel Wi-Fi 6E AX211 Driver: iwlwifi Firmware reported: 89.123cf747.0 Kernels tested: 7.0.0-34, 7.0.0-38, 7.0.0-42 Both 2.4 GHz and 5 GHz home wireless networks are affected. Troubleshooting performed: Restarted the home router without improvement. Tested multiple Ubuntu kernels. Tested different DNS servers. Disabled and restored Wi-Fi power saving. Tested a randomized MAC address. Checked routing tables and firewall configuration. Confirmed no duplicate IPv4 address during ARP probing. Confirmed local gateway connectivity remains stable during internet outages. Compared available Intel firmware package revisions; firmware files were identical. Additional observations: The issue appeared recently. Kernel logs contain iwlwifi messages including Unhandled alg: 0x703 and 0x400703, although their relationship to the connectivity problem is unknown. Please investigate whether this is an Intel AX211 driver/firmware compatibility issue or a network-stack regression affecting communication with certain access points. Related issues: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162998 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: gabert 7064 F.... wireplumber /dev/snd/seq: gabert 7056 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 20:25:28 2026 InstallationDate: Installed on 2025-03-03 (608 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: Dell Inc. Precision 3591 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-7.0.0-42-generic root=UUID=103e3baa-cc98-4cfb-9c43-1e78ac0e0124 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-03 (29 days ago) dmi.bios.date: 07/09/2026 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.1 dmi.board.name: 0VC7JN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnDellInc.:bvr1.25.1:bd07/09/2026:br1.25:efr1.23:svnDellInc.:pnPrecision3591:pvr:rvnDellInc.:rn0VC7JN:rvrA00:cvnDellInc.:ct10:cvr:sku0CBB:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 3591 dmi.product.sku: 0CBB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172730/+subscriptions

[Bug 2172674] Re: ES8336 codec audio stops after first stream (Hardware fails to wake up on Kernel 7.0.0)

Update (Suspend Trigger Identified): I wanted to add an update because I have isolated the exact trigger for this deadlock. After more testing, I can confirm this happens 100% of the time after the system enters auto-suspend (for example, after unplugging the laptop and leaving it idle). When the laptop wakes up, the hardware is completely wedged. dmesg shows PM: suspend exit right before the audio dies. Proposed Workaround: Since the deadlock is strictly triggered by the suspend/resume cycle, preventing the system from suspending entirely (via XFCE Power Manager) bypasses the bug—the hardware never loses power, so it never goes to sleep. I have applied this setting to both the AC and battery profiles and am currently running it successfully. This strongly suggests the failure happens when the kernel tries to wake the ES8336 codec back up. If the system does suspend, a full reboot remains the only way to recover the audio. I have updated the GitHub documentation linked in my original description to reflect this new finding. Thank you for looking into this. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172674 Title: ES8336 codec audio stops after first stream (Hardware fails to wake up on Kernel 7.0.0) Status in linux package in Ubuntu: New Bug description: This is my first kernel bug report, so I apologize if my terminology isn't perfect, but I have done a lot of testing to isolate this issue. Hardware: Intel N95 Laptop (Dixmau brand), ES8336 Codec (ACPI ID: ESSX8336). OS: Xubuntu 26.04.1 LTS (Kernel 7.0.0). The Issue: On this kernel, the first audio stream after boot works perfectly. However, when that stream stops, the hardware goes into a sleep state and fails to wake up. The next audio stream is completely silent. The volume meters move, but no sound comes out. Only a full reboot fixes it. Historical Context (24.04.5 LTS): On the previous LTS, this hardware wasn't recognized at all out of the box (it only showed "Dummy Output"). I had to manually force the system to recognize the ES8336 card. Once forced, it worked perfectly across multiple streams. It seems the new kernel recognizes the card better, but the new power management is breaking it. The Evidence (Raw ALSA Test): To prove this wasn't just a PipeWire/software issue, I stopped the audio services entirely and used raw ALSA (speaker-test -D plughw:0,0). The test produced silence after the failure, proving the hardware is stuck at the kernel level, not in the user software. lsmod confirms the snd_soc_es8336 driver is loaded. The Workaround: To stop the hardware from sleeping and breaking, I run a silent audio stream in the background. Keeping the device "awake" prevents the deadlock: pacat --playback --device=alsa_output.pci-0000_00_1f.3-platform-sof-essx8336.stereo-fallback /dev/zero Full Transparency: I used an AI assistant to help me parse the terminal logs, understand the power-management issue and structure this description. The full, unedited debugging process, command history, and AI disclosure are documented here: https://github.com/abdellahi-beirouck/linux-audio-debugging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172674/+subscriptions

[Bug 2172702] [NEW] Kernel panic in __run_timers (timer list corruption) when launching Thunderbird on Alder Lake-N, 7.3.0-9 and 7.3.0-10

Public bug reported: Ubuntu 26.10, kernels 7.3.0-9-generic and 7.3.0-10-generic. Hardware: Teclast laptop (DMI "Teclast Default string", BIOS tPAD3.05 04/10/2024) GPU: Intel Alder Lake-N iGPU (8086:46d2), i915, GuC 70.49.4, GuC submission enabled Wi-Fi: Realtek RTL8821CE (rtw88_8821ce) PROBLEM Launching Thunderbird (snap) causes a kernel panic ("Fatal exception in interrupt") a few seconds later, nearly every time. It also happened once while using Brave (snap). EFI pstore has kept the logs of more than a dozen crashes since 2026-10-13; the 13 I checked all have the same signature. The same symptom continues after updating to 7.3.0-10-generic. STEPS TO REPRODUCE 1. Boot 7.3.0-9-generic or 7.3.0-10-generic. 2. Launch Thunderbird. 3. The system panics within a few seconds. CRASH SIGNATURE (pstore, 7.3.0-9-generic) WARNING: kernel/workqueue.c:2432 at __queue_work+0x422/0x540, CPU#1: gfxtest/5832 delayed_work_timer_fn+0x19/0x30 call_timer_fn+0x30/0x160 __run_timers+0x1c0/0x2b0 run_timer_softirq+0x8a/0x100 handle_softirqs+0xd7/0x340 ... BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor write access in kernel mode Oops: 0002 [#1] SMP NOPTI RIP: 0010:__run_timers+0x1e9/0x2b0 RAX: dead000000000122 RDX: 0000000000000000 R13: ffff8d0243bc2a88 Kernel panic - not syncing: Fatal exception in interrupt Across crashes the oops RIP is __run_timers+0x1e1, +0x1e9 or +0x1f1. In detach_timer() the timer being removed already has entry.next == LIST_POISON2 and entry.pprev == NULL: a timer that was already detached is still linked in the timer wheel. R13 in the oops is exactly 0x20 after RBX in the preceding WARN (ffff8d0243bc2a68), so it appears to be the timer of the same delayed_work. This looks like a delayed_work being freed or re-initialized while still pending (use-after-free). The task running at the time was "gfxtest", a short-lived process that appears to be started by Thunderbird at launch to probe the GPU. That makes i915 a suspect, but it is not confirmed. ALREADY TESTED (crash still happens) - Airplane mode (Wi-Fi off) - options rtw88_pci disable_aspm=1 - LIBGL_ALWAYS_SOFTWARE=1 thunderbird NOT TESTED YET - Booting with nomodeset - An older kernel The full pstore log of the latest crash is attached. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-10-generic 7.3.0-10.10 ProcVersionSignature: Ubuntu 7.3.0-10.10-generic 7.3.0 Uname: Linux 7.3.0-10-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: henry-crisbeth 2984 F.... wireplumber /dev/snd/seq: henry-crisbeth 2980 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 09:27:35 2026 InstallationDate: Installed on 2025-06-23 (496 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 062a:9013 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 003: ID b349:b181 KYT-240222-A USB Camera Bus 001 Device 004: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Teclast Default string ProcEnviron: LANG=es_ES.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.3.0-10-generic root=UUID=01057e0e-86fe-4455-994c-88065f563a6d ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to stonking on 2026-09-29 (33 days ago) dmi.bios.date: 04/10/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: tPAD3.05 dmi.board.asset.tag: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrtPAD3.05:bd04/10/2024:br5.27:svnTeclast:pnDefaultstring:pvrDefaultstring:rvn:rn:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuF1P2_A1:pfa: dmi.product.name: Default string dmi.product.sku: F1P2_A1 dmi.product.version: Default string dmi.sys.vendor: Teclast ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug stonking third-party-packages wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172702 Title: Kernel panic in __run_timers (timer list corruption) when launching Thunderbird on Alder Lake-N, 7.3.0-9 and 7.3.0-10 Status in linux package in Ubuntu: New Bug description: Ubuntu 26.10, kernels 7.3.0-9-generic and 7.3.0-10-generic. Hardware: Teclast laptop (DMI "Teclast Default string", BIOS tPAD3.05 04/10/2024) GPU: Intel Alder Lake-N iGPU (8086:46d2), i915, GuC 70.49.4, GuC submission enabled Wi-Fi: Realtek RTL8821CE (rtw88_8821ce) PROBLEM Launching Thunderbird (snap) causes a kernel panic ("Fatal exception in interrupt") a few seconds later, nearly every time. It also happened once while using Brave (snap). EFI pstore has kept the logs of more than a dozen crashes since 2026-10-13; the 13 I checked all have the same signature. The same symptom continues after updating to 7.3.0-10-generic. STEPS TO REPRODUCE 1. Boot 7.3.0-9-generic or 7.3.0-10-generic. 2. Launch Thunderbird. 3. The system panics within a few seconds. CRASH SIGNATURE (pstore, 7.3.0-9-generic) WARNING: kernel/workqueue.c:2432 at __queue_work+0x422/0x540, CPU#1: gfxtest/5832 delayed_work_timer_fn+0x19/0x30 call_timer_fn+0x30/0x160 __run_timers+0x1c0/0x2b0 run_timer_softirq+0x8a/0x100 handle_softirqs+0xd7/0x340 ... BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor write access in kernel mode Oops: 0002 [#1] SMP NOPTI RIP: 0010:__run_timers+0x1e9/0x2b0 RAX: dead000000000122 RDX: 0000000000000000 R13: ffff8d0243bc2a88 Kernel panic - not syncing: Fatal exception in interrupt Across crashes the oops RIP is __run_timers+0x1e1, +0x1e9 or +0x1f1. In detach_timer() the timer being removed already has entry.next == LIST_POISON2 and entry.pprev == NULL: a timer that was already detached is still linked in the timer wheel. R13 in the oops is exactly 0x20 after RBX in the preceding WARN (ffff8d0243bc2a68), so it appears to be the timer of the same delayed_work. This looks like a delayed_work being freed or re-initialized while still pending (use-after-free). The task running at the time was "gfxtest", a short-lived process that appears to be started by Thunderbird at launch to probe the GPU. That makes i915 a suspect, but it is not confirmed. ALREADY TESTED (crash still happens) - Airplane mode (Wi-Fi off) - options rtw88_pci disable_aspm=1 - LIBGL_ALWAYS_SOFTWARE=1 thunderbird NOT TESTED YET - Booting with nomodeset - An older kernel The full pstore log of the latest crash is attached. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-10-generic 7.3.0-10.10 ProcVersionSignature: Ubuntu 7.3.0-10.10-generic 7.3.0 Uname: Linux 7.3.0-10-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: henry-crisbeth 2984 F.... wireplumber /dev/snd/seq: henry-crisbeth 2980 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 09:27:35 2026 InstallationDate: Installed on 2025-06-23 (496 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 062a:9013 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 003: ID b349:b181 KYT-240222-A USB Camera Bus 001 Device 004: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Teclast Default string ProcEnviron: LANG=es_ES.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.3.0-10-generic root=UUID=01057e0e-86fe-4455-994c-88065f563a6d ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to stonking on 2026-09-29 (33 days ago) dmi.bios.date: 04/10/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: tPAD3.05 dmi.board.asset.tag: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrtPAD3.05:bd04/10/2024:br5.27:svnTeclast:pnDefaultstring:pvrDefaultstring:rvn:rn:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuF1P2_A1:pfa: dmi.product.name: Default string dmi.product.sku: F1P2_A1 dmi.product.version: Default string dmi.sys.vendor: Teclast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172702/+subscriptions

[Bug 2172697] [NEW] It freezes, and you have to turn it off by holding down the button.

Public bug reported: It freezes, and you have to turn it off by holding down the button. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: user 4288 F.... wireplumber  /dev/snd/controlC0: user 4288 F.... wireplumber  /dev/snd/seq: user 4282 F.... pipewire CasperMD5CheckMismatches: ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 09:18:39 2026 InstallationDate: Installed on 2026-07-08 (116 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS System Product Name 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-7.0.0-42-generic root=UUID=c2d76319-0e27-466b-9df3-275f79fefd35 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: 12/09/2025 dmi.bios.release: 28.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2803 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING Z590-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.:bvr2803:bd12/09/2025:br28.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGZ590-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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Description changed: It freezes, and you have to turn it off by holding down the button. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC1: hossien 4288 F.... wireplumber - /dev/snd/controlC0: hossien 4288 F.... wireplumber - /dev/snd/seq: hossien 4282 F.... pipewire +  USER PID ACCESS COMMAND +  /dev/snd/controlC1: user 4288 F.... wireplumber +  /dev/snd/controlC0: user 4288 F.... wireplumber +  /dev/snd/seq: user 4282 F.... pipewire CasperMD5CheckMismatches: ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 09:18:39 2026 InstallationDate: Installed on 2026-07-08 (116 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS System Product Name ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> +  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-7.0.0-42-generic root=UUID=c2d76319-0e27-466b-9df3-275f79fefd35 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: 12/09/2025 dmi.bios.release: 28.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2803 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING Z590-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.:bvr2803:bd12/09/2025:br28.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGZ590-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 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172697 Title: It freezes, and you have to turn it off by holding down the button. Status in linux package in Ubuntu: New Bug description: It freezes, and you have to turn it off by holding down the button. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: user 4288 F.... wireplumber  /dev/snd/controlC0: user 4288 F.... wireplumber  /dev/snd/seq: user 4282 F.... pipewire CasperMD5CheckMismatches: ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 09:18:39 2026 InstallationDate: Installed on 2026-07-08 (116 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS System Product Name 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-7.0.0-42-generic root=UUID=c2d76319-0e27-466b-9df3-275f79fefd35 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: 12/09/2025 dmi.bios.release: 28.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2803 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING Z590-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.:bvr2803:bd12/09/2025:br28.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGZ590-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/2172697/+subscriptions

[Bug 2172370] Re: HP OMEN Gaming Laptop 16-ap0xxx (board 8E35): internal microphone missing on AMD ACP 1022:15e2 rev 0x62

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/2172370 Title: HP OMEN Gaming Laptop 16-ap0xxx (board 8E35): internal microphone missing on AMD ACP 1022:15e2 rev 0x62 Status in linux package in Ubuntu: Confirmed Bug description: [Impact] On the HP OMEN Gaming Laptop 16-ap0xxx (DMI board 8E35, BIOS F.13) the internal digital microphone array does not appear at all with the Ubuntu 26.04 kernel (7.0.0-42-generic). Only the headset-jack input is offered, so the laptop has no built-in mic for calls or dictation. The audio coprocessor is AMD ACP 1022:15e2 revision 0x62 (RPL). With the stock kernel it is claimed by snd_rpl_pci_acp6x, which has no DMIC support, and the yc driver (snd_pci_acp6x / snd_soc_acp6x_mach) neither accepts revision 0x62 nor carries a DMI quirk for this board, so no "acp6x" DMIC capture card is created. [Fix] Both pieces are in mainline since v7.1:   df4148a5a3cf18ee6e13e262079130b169ee51ac     ASoC: Add DMIC support for the AMD RPL platform   d63c219b7ff39f897da10c160a2edef76320f16c     ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in     quirk table Possibly related, in v7.3 (resume path of the same driver):   2a31b5378c6db9c4a8d399e5d10d32cd4b732bef     ASoC: amd: yc: disable MSI on resume The linux-oem-26.04 kernel (7.0.0-1017) already carries d63c219b, but not df4148a5, so the microphone still does not work there either. Please consider cherry-picking these into the resolute kernel. [Test Plan] 1. On an affected machine with the stock kernel, run `arecord -l` and    `wpctl status`: no "acp6x" / "DMIC capture" card and no "Digital    Microphone" source. 2. Boot a kernel with the commits above. `arecord -l` should list    "acp6x ... DMIC capture dmic-hifi-0", `dmesg` should show "acp_yc_mach    ...: Enabling ACP DMIC support via DMI", and a "Digital Microphone"    source should record speech. 3. Suspend and resume, then record again. The microphone should still    capture audio. Verified so far on this machine: steps 1 and 2 behave as described, using an out-of-tree build of the yc driver with the equivalent changes. After a suspend/resume the DMIC capture fails with "pcm_read: read error: Input/output error" until the PCI device is unbound and rebound; I have not confirmed that 2a31b537 resolves that part, and no IO_PAGE_FAULT was logged for the device. [Where problems could occur] df4148a5 lets the yc driver handle ACP revision 0x62, which on other RPL machines is currently left to snd_rpl_pci_acp6x; a regression would show up as a missing or misbehaving internal microphone on other AMD RPL laptops. d63c219b is a DMI table entry and only affects this product line. 2a31b537 only changes the system-resume path of the yc driver. [Other info] Hardware: HP OMEN Gaming Laptop 16-ap0xxx, board 8E35, BIOS F.13,           AMD ACP [1022:15e2] rev 62, Realtek ALC245 Kernel: Ubuntu 7.0.0-42.42-generic 7.0.14 (26.04.1 LTS) Logs: The attached omen-8e35-logs.tar.gz contains the three requested logs: - version.log (cat /proc/version_signature) - lspci-vnvn.log (sudo lspci -vnvn) - omen-8e35-mic-logs.txt (DMI, audio PCI devices and drivers, dkms status, arecord -l, wpctl sources, and acp/dmic kernel messages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172370/+subscriptions

[Bug 2170426] Re: Livelock between arc_prune and zfs_zget() hangs ZFS on large pools (fixed upstream, openzfs#19266)

Requested information attached. It was collected with "apport-cli -f --save" (for linux and zfsutils-linux) on a clean Ubuntu 26.04 install that reproduces the hang: linux-image-7.0.0-34-generic 7.0.0-34.34, zfsutils-linux 2.4.1-1ubuntu5.1. The production host where it first happened can't upload directly. The zfsutils-linux report and the reproducer follow in the next two comments. zfs-livelock-reproducer.tar.gz holds the reproducer and results behind the Test Plan above. On the stock module, igrab() fails 1.5M+ times per 10 s and the arc_prune thread blocks in zfs_znode_hold_enter <- zfs_zinactive <- ... <- prune_icache_sb. With the two upstream commits that drops to about 100 per 10 s. This isn't hardware- or driver-specific. It's a logic bug in module/os/linux/zfs (zfs_prune() / zfs_zget()), fixed upstream by e95c55285dc8 and 98527e086f0d, which cherry-pick cleanly onto 2.4.1. Setting both tasks back to Confirmed. ** Attachment added: "apport-cli -f -p linux --save (clean 26.04 VM, 7.0.0-34-generic)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170426/+attachment/6014073/+files/linux.apport -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170426 Title: Livelock between arc_prune and zfs_zget() hangs ZFS on large pools (fixed upstream, openzfs#19266) Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Impact] On Ubuntu 26.04 (zfs-linux 2.4.1-1ubuntu5.1, kernel 7.0.0-34-generic) a pool with many cached inodes and many concurrent lookups can livelock inside ZFS. On one of our NAS hosts (509 TB pool, about 16M cached inodes, NFS/rsync readers) this caused load above 1100, about 1000 stuck tasks, zero pool I/O for about 2 hours, and a forced power cycle. Cause: 1. When dnode_size exceeds arc_dnode_limit, the ARC asks every dataset to prune a large share of its cached dnodes. 2. zfs_prune() passes that whole count to a single super_cache_scan() call. The kernel's own reclaim (do_shrink_slab) works in shrinker->batch chunks of 1024; this call instead marks hundreds of thousands to millions of inodes I_FREEING up front and evicts them one at a time on the single arc_prune thread. 3. Every lookup that lands on one of those inodes fails igrab() in zfs_zget() and retries with "cond_resched(); goto again;", a busy loop that takes and drops the znode hold locks on every pass. 4. Hundreds of spinning lookups starve the evicting thread of CPU and of those locks. Eviction stalls, so the lookups never finish. The fix was merged upstream unchanged on 2026-10-09 (reviewed by Brian Behlendorf; closes openzfs/zfs#19266, PR #19275): - e95c55285dc8 "Linux: Feed the superblock shrinker in batches from zfs_prune()" - 98527e086f0d "Linux: Sleep instead of spinning when zfs_zget() races eviction" (delay(1) instead of cond_resched(), as xfs_iget() does) Both are Linux-only (41 lines added, 6 removed), change no on-disk format, ioctl or tunable, and apply cleanly to 2.4.1-1ubuntu5.1. [Test Plan] Setup: a 26.04 VM with 24 vCPUs and the ARC capped at 24 GiB; 8M files in 4000 directories (xattr=sa, atime on); 1024-2048 threads doing readdir + stat in a loop, plus a 40 GB streaming read to churn the ARC. Optionally amplify with zfs_arc_dnode_reduce_percent=100. Measure failed igrab retries (bpftrace on zfs_zget), inodes evicted per 10 s, and threads making no progress. Our results, stock vs patched: - failed igrab retries per 10 s: 1.5M -> about 100 - slowest 10 s window for the evictor: 504 inodes evicted (stalled) -> 195k - tasks waiting on znode hold locks: 206 -> 0 - worst stat(): 25.9 s -> 7.4 s zfs-test sanity.run: 826 of 827 tests give the same result on both; the one difference passed on the patched module. Write-path churn at default tunables showed no regression. The patched module has run in production on the affected host since 2026-10-08. [Where problems could occur] - Pruning now happens in shrinker->batch chunks, so a prune request makes more super_cache_scan() calls. The total number of objects scanned is unchanged. - A lookup that races eviction now sleeps one tick instead of yielding, which could add latency on that rare path. Measured p99.9 latency was unchanged. - A regression would show up as slower inode reclaim under memory pressure, or as higher latency for lookups of inodes that are being evicted. [Other Info] - The kernel's linux-main-modules-zfs-* packages are built from the kernel's own copy of zfs, so the linux source package needs the two patches as well. - Upstream issue: https://github.com/openzfs/zfs/issues/19266 - Upstream PR: https://github.com/openzfs/zfs/pull/19275 - Commits: https://github.com/openzfs/zfs/commit/e95c55285dc889ba945483361701c2ac22d47e58 and https://github.com/openzfs/zfs/commit/98527e086f0df6dd3845edac29f3e19866ac61f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170426/+subscriptions

[Bug 2172684] Re: zpool online with the pool GUID oopses in vdev_reopen and hangs ZFS until reboot

** 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/2172684 Title: zpool online with the pool GUID oopses in vdev_reopen and hangs ZFS until reboot Status in linux package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: [Impact] On Ubuntu 26.04, zpool online with the pool GUID as the device name dereferences NULL in vdev_reopen(). The command dies with "Killed". The dead thread still holds SCL_STATE_ALL as writer, so txg_sync and later zpool commands block in D state until a hard reset. The pool imported normally after the reset, and a later scrub was clean. Admins can reach this by copying what zpool status prints. After zpool import -d /dev/disk/by-uuid/<uuid>, zpool status shows the disk under the pool GUID, because blkid's UUID for a zfs_member is the pool GUID. Passing that name to zpool online -e triggers the crash. The other names we tried for the disk (sdb, /dev/sdb, /dev/sdb1, the full by- uuid path, the leaf GUID) fail with ordinary errors. ZED reached the same oops once, as Comm: agents, with autoexpand=on and no zpool online running, right after a re-import through by-uuid. The trigger has not been isolated. Upstream report: https://github.com/openzfs/zfs/issues/19659 Regression from upstream commit 5caeef02fa53 (RAID-Z expansion), first in 2.3.0, which removed the non-leaf check from vdev_online(). [Affected versions] resolute, 2.4.1-1ubuntu5.1: reproduced on kernel 7.0.0-38.38. The zfs.ko in linux-main-modules-zfs-7.0.0-42-generic has the same version and srcversion (0BF563C747C51B92C058D78), so the current kernel carries the same code. stonking and tenacious, 2.4.4-1ubuntu4: upstream 2.4.4 has the same vdev_online() code (read, not run). noble, 2.2.2-0ubuntu9.5: not affected. Tested; it returns "operation not supported on this type of pool" with no oops. The loaded module ships in linux-main-modules-zfs-* (source linux- main-signed). Its srcversion matches zfs-dkms 2.4.1-1ubuntu5.1 built against the same kernel, so the fix probably needs a kernel build as well as zfs-linux. [Test Plan] zpool create -f -o ashift=12 ncdata /dev/sdX partprobe -s U=$(blkid -o value -s UUID /dev/sdX1) zpool get -H -o value guid ncdata # same value as $U zpool export ncdata zpool import -d /dev/disk/by-uuid/"$U" ncdata zpool status ncdata # the disk is shown as $U zpool online -e ncdata "$U" Before the fix: "Killed", the oops below, and zpool list hangs. After the fix: "cannot expand <guid>: operation not supported on this type of pool", exit 1, and the pool stays responsive. In our run the disk had been grown to 3 TB with autoexpand=off, and the pool had non-default properties. Neither is used on this code path. RAID-Z check, because the removed check was dropped for this feature: zpool create rz raidz1 <f1> <f2> <f3> zpool attach rz raidz1-0 <f4> zpool wait -t raidz_expand rz zpool online -e rz raidz1-0 # must return 0 [Proposed fix] Reject only the root vdev. The old non-leaf check can't simply go back, because spa_raidz_expand_thread() calls vdev_online() with a top-level RAID-Z vdev's GUID. Upstream has not reviewed this yet. --- a/module/zfs/vdev.c +++ b/module/zfs/vdev.c @@ -4447,6 +4447,14 @@ if ((vd = spa_lookup_by_guid(spa, guid, B_TRUE)) == NULL) return (spa_vdev_state_exit(spa, NULL, SET_ERROR(ENODEV))); + /* + * The root vdev has no vdev_top to reopen. This is reachable from + * userland, since a numeric device name is looked up as a GUID and the + * root vdev's GUID is the pool GUID. + */ + if (vd == rvd) + return (spa_vdev_state_exit(spa, NULL, SET_ERROR(ENOTSUP))); + wasoffline = (vd->vdev_offline || vd->vdev_tmpoffline); oldstate = vd->vdev_state; Tested with zfs-dkms 2.4.1-1ubuntu5.1 plus this patch on kernel 7.0.0-38. The test plan's crash becomes the error above, and the RAID-Z check passes. [Where problems could occur] The patch only changes the root vdev case, which currently oopses. Any mistake would show up in zpool online or at the end of a RAID-Z expansion. [Other Info] First reported from VMware guests after growing the data disk. Reproduced in a QEMU guest (TCG, PVSCSI, VMware SMBIOS strings, no disk serial or VPD IDs), not on ESXi. BUG: unable to handle page fault for address: 00000000000033e0 #PF: supervisor read access in kernel mode Oops: Oops: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 2352 Comm: zpool Tainted: P O 7.0.0-38-generic #38-Ubuntu PREEMPT(lazy) RIP: 0010:vdev_reopen+0x15/0x1a0 [zfs] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 CR2: 00000000000033e0 Call Trace: vdev_online+0xc8/0x540 [zfs] zfs_ioc_vdev_set_state+0x86/0x1b0 [zfs] zfsdev_ioctl_common+0x8e3/0x9d0 [zfs] zfsdev_ioctl+0x54/0xe0 [zfs] __x64_sys_ioctl+0xa3/0x100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172684/+subscriptions

[Bug 2162038] Re: [SRU] Fix incorrect GTT calculation on the APU systems

This bug is awaiting verification that the linux-gke/7.0.0-1010.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-gke' to 'verification-done- resolute-linux-gke'. If the problem still exists, change the tag 'verification-needed-resolute-linux-gke' to 'verification-failed- resolute-linux-gke'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-gke-v2 verification-needed-resolute-linux-gke -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162038 Title: [SRU] Fix incorrect GTT calculation on the APU systems Status in linux package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: New Status in linux source package in Resolute: Fix Committed Status in linux-oem-7.0 source package in Resolute: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2162038 [ Impact ] On AMD APU systems, there are few ways to tweak memory being used by the amdgpu driver. Notably: - VRAM size can be tweaked by: UMA carveout by the BIOS/sysfs interfaces. - GTT size can be tweaked by module parameters in the TTM module. Currently, the mechanisms above works independently. However, on APU systems, because total physical memory is shared among the above and is partitioned into them, the calculation needs to take the total physical memory into account. Otherwise the driver would be double- booking physical memory, leading to issues like [1]. [ Fix ] Cherry-pick the following commit: - drm/amdgpu: cap GTT size to physical RAM on APUs[2] [ Test Plan ] - Boot into the kernel with a large non-carveout memory space (~512MB out of 64G total memory) and accordingly set a large GTT (~48GB) via the ttm module parameter (ttm.pages_limit=12582912). - Lower the non-carveout memory space in BIOS/sysfs by increasing the UMA Frame Buffer Size (VRAM) to 48GB and reboot. - The previously set GTT value (~48GB) should be capped to the non-carveout space, showing the following message:     [ 5.096745] amdgpu 0000:c3:00.0: 49152M of VRAM memory ready     [ 5.096753] amdgpu 0000:c3:00.0: Capping GTT to 14654M to not exceed available system memory For reference, previously it shows: [ 4.980841] amdgpu 0000:c3:00.0: 49152M of VRAM memory ready [ 4.980843] amdgpu 0000:c3:00.0: 49152M of GTT memory ready. [ Where the problems could occur ] Because the old driver is double-counting memory sizes, a user with this update may feel that memory become less, when in fact that memory is double-counted and never exists. This impacts memory calculation on GTT for APU systems. [ Additional Information ] [1] https://github.com/ROCm/ROCm/issues/6004 [2] https://lore.kernel.org/amd-gfx/20260727194207.176803-1-harkirat.gill@amd.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162038/+subscriptions