[Bug 2154481] Re: Generic questing kernel oops on bootup with newer Nvidia machines

This bug is awaiting verification that the linux- nvidia-6.17/6.17.0-1024.24 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-noble-linux- nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux- nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'. 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-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154481 Title: Generic questing kernel oops on bootup with newer Nvidia machines Status in linux package in Ubuntu: New Status in linux source package in Questing: New Bug description: The following boot logs were noted on Questing deployment on lubba with questing 6.17.0-29.29 deployment through testfinger: [ 69.979129] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000cc^M [ 69.979141] Mem abort info:^M [ 69.979145] ESR = 0x0000000096000004^M [ 69.979146] EC = 0x25: DABT (current EL), IL = 32 bits^M [ 69.979147] SET = 0, FnV = 0^M [ 69.979148] EA = 0, S1PTW = 0^M [ 69.979148] FSC = 0x04: level 0 translation fault^M [ 69.979149] Data abort info:^M [ 69.979150] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000^M [ 69.979150] CM = 0, WnR = 0, TnD = 0, TagAccess = 0^M [ 69.979151] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0^M [ 69.979152] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000112a9e000^M [ 69.979154] [00000000000000cc] pgd=0000000000000000, p4d=0000000000000000^M [ 69.979158] Internal error: Oops: 0000000096000004 [#1] SMP^M [^[[0;32m OK ^[[0m] Listening on ^[[ 70.055117] Modules linked in: nouveau(+) gpu_sched drm_gpuvm drm_exec drm_ttm_helper ttm dax_hmem cxl_acpi drm_display_helper cxl_port cxl_core ast cec nvidia_cspmu rc_core einj ipmi_ssif(+) i2c_algo_bit arm_smmuv3_pmu arm_cspmu_module arm_spe_pmu uio_pdrv_genirq acpi_power_meter uio mlx5_fwctl acpi_ipmi spi_nor fwctl ipmi_devintf mtd cppc_cpufreq ipmi_msghandler sch_fq_codel efi_pstore dm_multipath nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 linear mlx5_ib ib_uverbs macsec ib_core mlx5_dpll uas polyval_ce usb_storage ghash_ce sm4_ce_gcm sm4_ce_ccm mlx5_core sm4_ce i2c_smbus nvme mlxfw sm4_ce_cipher nvme_core psample sm4 nvme_keyring sm3_ce tls sha3_ce xhci_pci_renesas pci_hyperv_intf nvme_auth i2c_tegra aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher^M [ 70.138368] CPU: 0 UID: 0 PID: 816 Comm: kworker/0:3 Not tainted 6.17.0-29-generic #29-Ubuntu PREEMPT(voluntary) ^M [ 70.148863] Hardware name: /P3880, BIOS 01.02.01 20240207^M [ 70.155180] Workqueue: events work_for_cpu_fn^M [ 70.159639] pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)^M [ 70.166755] pc : bit_entry+0x20/0x160 [nouveau]^M [ 70.171466] lr : nvbios_pmuTe+0x60/0x160 [nouveau]^M [ 70.176422] sp : ffff80008c943740^M [ 70.179804] x29: ffff80008c943740 x28: 0000000000028648 x27: 0000000000000030^M [ 70.187099] x26: 0000000000000180 x25: 0000000000000180 x24: 0000000000000019^M [ 70.194393] x23: ffff80008c9437f7 x22: 0000000000000070 x21: ffff80008c94383f^M [ 70.201688] x20: ffff80008c94383e x19: 0000000000000000 x18: ffff80008c93b0d8^M [ 70.208983] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000^M [ 70.216278] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000^M [ 70.223572] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc70f0fe8a6a8^M [ 70.230866] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000^M [ 70.238161] x5 : ffff0000a4944700 x4 : ffff80008c9437f7 x3 : ffff80008c9437f6^M [ 70.245456] x2 : ffff80008c943792 x1 : 0000000000000070 x0 : 0000000000000000^M [ 70.252752] Call trace:^M [ 70.255246] bit_entry+0x20/0x160 [nouveau] (P)^M [ 70.259929] nvbios_pmuTe+0x60/0x160 [nouveau]^M [ 70.264517] nvbios_pmuEp+0x60/0x120 [nouveau]^M [ 70.269102] nvkm_gsp_fwsec_init+0x90/0x1e0 [nouveau]^M [ 70.274311] nvkm_gsp_fwsec_sb_ctor+0x2c/0x60 [nouveau]^M [ 70.279693] r535_gsp_rm_boot_ctor+0x2c/0x138 [nouveau]^M [ 70.285072] r535_gsp_oneinit+0x258/0x340 [nouveau]^M [ 70.290093] gh100_gsp_oneinit+0x280/0x450 [nouveau]^M [ 70.295200] nvkm_gsp_oneinit+0x2c/0x70 [nouveau]^M [ 70.300040] nvkm_subdev_oneinit_+0x60/0x150 [nouveau]^M [ 70.305327] nvkm_subdev_init_+0x4c/0x190 [nouveau]^M [ 70.310345] nvkm_subdev_init+0x74/0xd8 [nouveau]^M [ 70.315184] nvkm_device_init+0x180/0x298 [nouveau]^M [ 70.320216] nvkm_udevice_init+0x78/0xa0 [nouveau]^M [ 70.325157] nvkm_object_init+0x50/0x200 [nouveau]^M [ 70.330094] nvkm_ioctl_new+0x198/0x280 [nouveau]^M [ 70.334938] nvkm_ioctl+0xd8/0x300 [nouveau]^M [ 70.339335] nvkm_client_ioctl+0x1c/0x48 [nouveau]^M [ 70.344285] nvif_object_ctor+0xf8/0x218 [nouveau]^M [ 70.349225] nvif_device_ctor+0x44/0xf0 [nouveau]^M [ 70.354070] nouveau_drm_device_new+0x1ec/0x438 [nouveau]^M [ 70.359639] nouveau_drm_probe+0xdc/0x250 [nouveau]^M [ 70.364672] local_pci_probe+0x48/0xd8^M [ 70.368505] work_for_cpu_fn+0x28/0x58^M [ 70.372335] process_one_work+0x174/0x428^M [ 70.376432] worker_thread+0x310/0x440^M [ 70.380262] kthread+0x110/0x130^M [ 70.383558] ret_from_fork+0x10/0x20^M [ 70.387215] Code: a9bc7bfd 910003fd a9025bf5 12001c36 (b940cc01) ^M [ 70.393445] ---[ end trace 0000000000000000 ]---^M Similar error was also noted on hinyari with full boot log attached. This causes undefined behavior, where in some cases the kernel boots up as well. The issue was reported upstream: https://lore.kernel.org/all/176698808133.6372.2408917375327107249@copycat/ and the fix has been accepted: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau?h=v7.1-rc5&id=e8b3627bec357698f2d4d6dbf27cdcfa0e9d8715 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154481/+subscriptions

[Bug 2148638] Re: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized.

I checked the attached logs. For config_B (locally built test kernel), the after-replug dmesg does not show the same fatal NVMe failure seen in config_A. In config_B/3-config_B.after_replug.log/dmesg3.log, all three replugged NVMe devices probe and complete queue setup: 10000:01:00.0 -> nvme0, queues ready at line 3611 10000:02:00.0 -> nvme1, queues ready at line 3615 10000:03:00.0 -> nvme2, queues ready at line 3660 So based on the attached dmesg, the locally built test kernel does not reproduce the same NVMe probe/reset/resource-clobbering failure as config_A. If the failure is still seen from userspace, please provide lsblk/nvme list before unplug and after replug, plus any I/O error output. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148638 Title: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: When the CD8P NVMe hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. This issue happens on CD8P NVMe disk and does not happens on bm1743 NVMe disk. CD8P drives are Kaoxia drives The BM1743 drives that work are Samsung devices. Nvme disk detail: CD8P https://lenovopress.lenovo.com/lp1904-thinksystem-cd8p-read-intensive-nvme-pcie-50-ssd bm1743 https://lenovopress.lenovo.com/lp2156-thinksystem-bm1743-read-intensive-nvme-pcie-50-x4-ssd Steps to reproduce: 1.In the UEFI, enable VMD without created RAID disk. 2.Install ubuntu26.04 on M.2 sata disk. 3.use command lsblk to check all NVMEe disk 4.Unplug all NVMe device, then check NVMe device information again via lsblk. 5.plug all NVMe SSD 6.OS reported an error and some of the drives were not recognized. Compare with Ubuntu 24.04: There is no errors messages and all NVMe disks can be recognized after re-plug all NVMe SSD Info: The issue also happens on latest daily build: 0415 This issue only happens on VMD enabled, there is no this issue when vmd feature disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+subscriptions

[Bug 2155617] Re: Backlight device disappears and brightness breaks on kernel 6.17.0-23+ (Lenovo Legion 5 Pro, NVIDIA hybrid graphics)

Hi Vesa Thank you for your information. Could you try the command below to fix the issue? ``` sudo apt update sudo apt install linux-modules-nvidia-570-generic-hwe-24.04 sudo reboot ``` after reboot, please check if modules be loaded, and backlight nodes showup ``` lsmod | grep nvidia ls /sys/class/backlight ``` BR An -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155617 Title: Backlight device disappears and brightness breaks on kernel 6.17.0-23+ (Lenovo Legion 5 Pro, NVIDIA hybrid graphics) Status in linux package in Ubuntu: New Bug description: On Ubuntu 24.04.2 LTS running on a Lenovo Legion 5 Pro 16ACH6H (AMD + NVIDIA RTX 3070 hybrid system), brightness control breaks starting from kernel 6.17.0-23-generic and remains broken on all newer kernels up to 6.17.0-35. The issue is fully reproducible. WORKING KERNEL: - 6.17.0-22-generic - Display session: X11 - NVIDIA proprietary driver in use - Backlight device present: /sys/class/backlight/nvidia_0 - Brightness control works normally BROKEN KERNELS: - 6.17.0-23-generic and newer (tested up to 6.17.0-35) - Wayland or X11 both affected - Backlight directory is empty: /sys/class/backlight/ SYMPTOMS: - Brightness stuck at 100% - No backlight device exposed in sysfs - Mouse cursor shows trailing/ghosting artifacts on Wayland - Display rendering instability EXPECTED BEHAVIOR: - /sys/class/backlight/nvidia_0 should be present - Brightness control should function via NVIDIA DRM backlight interface ACTUAL BEHAVIOR: - No backlight device is registered at all in /sys/class/backlight/ - GNOME brightness controls have no effect HARDWARE: - Lenovo Legion 5 Pro 16ACH6H - AMD Ryzen CPU (iGPU present but not used for display in working kernel) - NVIDIA RTX 3070 Mobile (primary display output via nvidia-drm) - NVIDIA proprietary driver active REGRESSION: - Kernel 6.17.0-22 works correctly - 6.17.0-23 introduces regression and all newer kernels inherit it This appears to be a regression in NVIDIA DRM backlight device registration (fbdev / sysfs exposure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155617/+subscriptions

[Bug 2156421] Re: bug on keyboard keys kernel 7

** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156421 Title: bug on keyboard keys kernel 7 Status in linux package in Ubuntu: Incomplete Bug description: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156421/+subscriptions

[Bug 2157675] Re: Internal microphone not working on Lenovo IdeaPad 3 15ALC6 (82KU) - missing ACP quirk

It's not a ubuntu. ** Changed in: linux (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/2157675 Title: Internal microphone not working on Lenovo IdeaPad 3 15ALC6 (82KU) - missing ACP quirk Status in linux package in Ubuntu: Invalid Bug description: Internal microphone not working on Lenovo IdeaPad 3 15ALC6 (Type 82KU). The AMD ACP coprocessor is present but internal mic capture device never appears. System info: - Product: Lenovo IdeaPad 3 15ALC6 (82KU) - Subsystem Id: 0x17aa38bc - Audio codec: Realtek ALC257 - Kernel: 6.17.0-35-generic - Distro: Linux Mint 22.3 lspci output: 03:00.1 Audio device: AMD/ATI Renoir Radeon High Definition Audio Controller 03:00.5 Multimedia controller: AMD ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) 03:00.6 Audio device: AMD Family 17h/19h HD Audio Controller arecord -l shows only ALC257, no DMIC device. Modules snd_rn_pci_acp3x and snd_sof_amd_acp load successfully but no capture device appears. Fix needed: add DMI quirk entry for product name "82KU" in sound/soc/amd/yc/acp6x-mach.c similar to other IdeaPad models (82SJ, 82TL, 82QF etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157675/+subscriptions

[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot

Same issue with my system. Tried different distros (CachyOS, Mint 22, Ubuntu 22.04, 24.04, 26.04) and all of them gave the same results. In addition, lately this bug is affecting my boot as well, screen stuck after GRUB selection, R9 380 ramping up the fans to 100% and everything frozen, tho i was able to login via SSH, the system itself couldn't even change ttys, only solution was to hard reset. This happened using X11 or wayland, at any DE (tried KDE, Gnome, Cinnamon, XFCE and ChimeraOS using SteamOS interface) Solution was to boot the system with the nomodeset parameter and install another kernel before this was a thing. 6.1.0-060100-generic is wotking fine for the moment, latest 6.1 release (6.1.176) is affected by this bug. Kernel 5.15 was fine too. Hardware specs Ryzen 7 1700 16GB DDR4 2933 ASUS TUF B450M Sapphire Nitro R9 380 4GB -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142389 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: Confirmed Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions

[Bug 2157755] Re: [linux 6.8.0-124-generic] Dentry-cache slab use-after-free under concurrent /proc lookup + process exit on high-density LXD hosts

** 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/2157755 Title: [linux 6.8.0-124-generic] Dentry-cache slab use-after-free under concurrent /proc lookup + process exit on high-density LXD hosts Status in linux package in Ubuntu: New Bug description: **Package:** linux (Ubuntu Noble 24.04 LTS) **Kernel:** 6.8.0-124-generic #124-Ubuntu SMP PREEMPT_DYNAMIC (Ubuntu 6.8.0-124.124, base 6.8.12) **Severity:** High — repeatable hard crash (kernel panic / reboot) on production hosts, ~every 2–6 days --- ## Summary On heavily loaded LXD container hosts running 6.8.0-124-generic, the kernel panics repeatedly with memory corruption localized to the **dentry slab cache**. A captured kdump vmcore shows a **use-after- free**: the dentry slab freelist is overwritten with non-pointer garbage, and concurrent threads doing `/proc` path lookups and process-exit dentry teardown fault on the corrupted objects. The corruption is confirmed by `crash`'s own slab validator (`kmem -s` reports `invalid freepointer` on dentry slabs) and by three CPUs caught mid-fault in the same dentry alloc/free paths in a single core. The same workload on **6.8.0-90-generic does not exhibit the crash** (see A/B test below), which points to a regression in the dentry/procfs path between -90 and -124, or to a latent race newly exposed by changes in that range. --- ## Environment - **Hardware:** Supermicro SYS-611C-TN4R / X13DDW-A, BIOS 2.7 (07/23/2025), dual-socket, 64 logical CPUs, 256 GB RAM - **Root/storage:** OpenZFS (zfs 2.2.2-0ubuntu9.4), kernel tainted `PO` (out-of-tree + proprietary ZFS module) - **Workload:** ~90 LXD system containers (managed WordPress hosting); very high concurrent fork/exit and `/proc` scanning from per-container nginx / php-fpm / mariadbd / redis plus host-side monitoring (`ps`), backups (`tar`) - **Crash cadence:** every ~2–6 days; uptime at this capture was 8 days - **EDAC/MCE:** clean (`ras-mc-ctl --summary/--errors` show no memory or PCIe errors; IPMI SEL clean apart from PSU/chassis noise) — not a hardware memory fault --- ## Impact Each event is a hard kernel panic. With `panic_on_oops=1` / `panic=10` the host self-reboots, but every crash is a full outage of ~90 tenant containers. The corruption surfaces in unrelated subsystems (dentry teardown, dentry alloc, socket/pid allocation) because it is a slab freelist UAF — the faulting site is never the bug site, which makes it look like random instability until the dump is examined. --- ## Crash analysis (from kdump vmcore, full matching dbgsym) Panic task and primary oops: ``` PANIC: "Oops: 0000 [#1] PREEMPT SMP NOPTI" COMMAND: "ps" CPU: 37 [exception RIP: dentry_unlink_inode+251] (NULL deref; RAX/RDX/RSI/RDI = 0) #8 dentry_unlink_inode #9 __dentry_kill #10 shrink_dentry_list #11 shrink_dcache_parent #12 d_invalidate #13 lookup_fast #14 walk_component #15 path_lookupat #16 filename_lookup #17 vfs_statx #18 vfs_fstatat #19 __do_sys_newfstatat ``` The corrupted dentry is a procfs pid entry — `/proc/<pid>/cmdline`: ``` struct dentry { d_name.name = "cmdline" d_iname = "cmdline" d_inode = 0x0 <-- already unlinked d_op = pid_dentry_operations d_lockref.count = -128 (0xffffff80) <-- refcount already driven negative } ``` `crash`'s slab validator independently flags the dentry cache as corrupt (no `slub_debug` was active at capture — this is structural freelist validation): ``` kmem: dentry: slab: ffd8d770cc2fe300 invalid freepointer: 7d6cf1f4997700d6 kmem: dentry: slab: ffd8d770cc1abe00 invalid freepointer: 7d6cf1f494205b56 kmem: kmalloc-rcl-64: slab: ffd8d770cc26a700 invalid freepointer: 55ab8f7b3288b69a ``` Three CPUs were simultaneously in dentry alloc/free paths at panic — the race, in one snapshot: | CPU | Task | Operation | Fault | |-----|------|-----------|-------| | 37 | ps | dentry teardown: `dentry_unlink_inode ← __dentry_kill ← shrink_dentry_list ← d_invalidate ← lookup_fast` (`/proc` stat walk) | NULL deref on already-freed dentry (panicked first) | | 4 | ps | dentry teardown: `dentry_unlink_inode ← __dentry_kill ← dput ← lookup_fast ← open_last_lookups ← openat` | same fault site; spinning in `native_queued_spin_lock_slowpath` | | 45 | tar | dentry **allocation**: `kmem_cache_alloc_lru ← __d_alloc ← d_alloc_parallel ← __lookup_slow` (stat walk) | GPF on poisoned freelist pointer; R14 = dentry cache addr | The `tar` GPF register state shows the poisoned pointer being consumed from the dentry slab: ``` [exception RIP: kmem_cache_alloc_lru+221] general protection fault (non-canonical address) RAX: 627117ed820fc609 RDI: 627117ed820fc5a9 <-- garbage freelist pointer R14: ff1a80bec01f6800 <-- dentry kmem_cache ``` This matches earlier pstore-only captures of the same host, where the first event was consistently a GPF in `kmem_cache_alloc_lru` on a non- canonical freelist pointer reached via `__d_alloc` / `alloc_pid` / `sock_alloc_file` — all dentry/slab allocations off the fork/exit hot paths. --- ## What is ruled out - **Not ZFS.** All ZFS caches (`zfs_znode_cache`, `dnode_t`, `dmu_buf_impl_t`, `arc_buf_*`) are intact in `kmem -s` — no `invalid freepointer` — despite millions of live objects. ZFS appears only as a passing frame on the clone path. (Kernel is ZFS-tainted; noted for completeness, but the corrupted cache is core VFS `dentry`, not any ZFS slab.) - **Not AppArmor notification CVEs (USN-8373-1 / CVE-2026-47326..47328).** `apparmor_auditcache` is clean/empty; the AppArmor notification interface is not in active use on these hosts (no `aa-notify` consumer, `features/policy/notify` empty). The fault is in core procfs/VFS dentry handling (`pid_dentry_operations`), unrelated to AppArmor. - **Not hardware.** EDAC/MCE/SEL clean; corruption is structurally consistent (always dentry slab, always teardown/alloc paths), not the random scatter of failing DIMMs. --- ## A/B test (kernel version isolation) Two near-identical heavily loaded hosts that both crashed on -124: - **Host A (vps232):** kept on **6.8.0-124**, kdump-armed, used to capture this vmcore. - **Host B (vps193):** rolled back to **6.8.0-90-generic**, same workload (~90 containers), as control. Expected discriminator within one crash interval: if Host B on -90 stays up while Host A on -124 keeps crashing, the regression is localized to the -90→-124 range. (Result will be added as a follow-up comment.) Note: 6.8.0-124.124 is the newest generic kernel currently published for Noble, so there is no forward kernel to test against — rollback to -90 is the only available containment. --- ## Reproduction conditions Not yet reduced to a minimal reproducer, but reliably reproduced in production by: - High logical-CPU-count host (64) with high process density (~90 LXD containers) - Sustained concurrent `/proc` traversal (host monitoring running `ps`/stat loops) **plus** continuous process churn (per-container php-fpm/nginx fork+exit) **plus** filesystem tree walks (`tar` backups) - i.e. heavy concurrent `__d_alloc` (lookup) and `__dentry_kill`/`proc_flush_pid` (exit + invalidate) against the shared dentry cache Mean time to corruption: ~2–6 days of normal production load. --- ## Artifacts available on request - Full kdump vmcore (`/var/crash/...`, ~17 GB, PARTIAL DUMP via makedumpfile) captured against `linux-image-unsigned-6.8.0-124-generic-dbgsym` 6.8.0-124.124 (matching build-id) - `crash` session output: `bt`, `bt -a` (all 64 CPUs), `kmem -s`, `kmem -S dentry`, `struct dentry` of the corrupted object, `log` - Five prior pstore dmesg captures from the same host showing the recurring signature - apport-collected host/config data (will attach via `ubuntu-bug linux`) ## Planned follow-up Host A is being rebooted with `slub_debug=FZP` to catch the corrupting write **at the bad free** (red-zone/poison validation), which should name the exact freeing path. That trace will be attached as a follow- up comment once the next event is captured. Full 17 GB kdump vmcore (PARTIAL DUMP, makedumpfile) retained on the affected host, captured against linux-image- unsigned-6.8.0-124-generic-dbgsym 6.8.0-124.124 (matching build-id). Available to the assigned engineer on request 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: zfs AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Jun 21 19:29 seq crw-rw---- 1 root audio 116, 33 Jun 21 19:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sun Jun 21 20:43:01 2026 InstallationDate: Installed on 2025-12-01 (202 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 003: ID 0557:9241 ATEN International Co., Ltd SMCI HID KM Bus 001 Device 004: ID 0b1f:03ee Insyde Software Corp. RNDIS/Ethernet Gadget Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Supermicro SYS-611C-TN4R PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-124-generic root=UUID=3e867032-21c4-416e-b45f-a17d1dae6788 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M panic_on_oops=1 panic=10 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.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.7 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: X13DDW-A dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.7:bd07/23/2025:br5.32:svnSupermicro:pnSYS-611C-TN4R:pvr0123456789:rvnSupermicro:rnX13DDW-A:rvr1.01:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: Family dmi.product.name: SYS-611C-TN4R dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157755/+subscriptions

[Bug 2157755] [NEW] [linux 6.8.0-124-generic] Dentry-cache slab use-after-free under concurrent /proc lookup + process exit on high-density LXD hosts

Public bug reported: **Package:** linux (Ubuntu Noble 24.04 LTS) **Kernel:** 6.8.0-124-generic #124-Ubuntu SMP PREEMPT_DYNAMIC (Ubuntu 6.8.0-124.124, base 6.8.12) **Severity:** High — repeatable hard crash (kernel panic / reboot) on production hosts, ~every 2–6 days --- ## Summary On heavily loaded LXD container hosts running 6.8.0-124-generic, the kernel panics repeatedly with memory corruption localized to the **dentry slab cache**. A captured kdump vmcore shows a **use-after- free**: the dentry slab freelist is overwritten with non-pointer garbage, and concurrent threads doing `/proc` path lookups and process- exit dentry teardown fault on the corrupted objects. The corruption is confirmed by `crash`'s own slab validator (`kmem -s` reports `invalid freepointer` on dentry slabs) and by three CPUs caught mid-fault in the same dentry alloc/free paths in a single core. The same workload on **6.8.0-90-generic does not exhibit the crash** (see A/B test below), which points to a regression in the dentry/procfs path between -90 and -124, or to a latent race newly exposed by changes in that range. --- ## Environment - **Hardware:** Supermicro SYS-611C-TN4R / X13DDW-A, BIOS 2.7 (07/23/2025), dual-socket, 64 logical CPUs, 256 GB RAM - **Root/storage:** OpenZFS (zfs 2.2.2-0ubuntu9.4), kernel tainted `PO` (out-of-tree + proprietary ZFS module) - **Workload:** ~90 LXD system containers (managed WordPress hosting); very high concurrent fork/exit and `/proc` scanning from per-container nginx / php-fpm / mariadbd / redis plus host-side monitoring (`ps`), backups (`tar`) - **Crash cadence:** every ~2–6 days; uptime at this capture was 8 days - **EDAC/MCE:** clean (`ras-mc-ctl --summary/--errors` show no memory or PCIe errors; IPMI SEL clean apart from PSU/chassis noise) — not a hardware memory fault --- ## Impact Each event is a hard kernel panic. With `panic_on_oops=1` / `panic=10` the host self-reboots, but every crash is a full outage of ~90 tenant containers. The corruption surfaces in unrelated subsystems (dentry teardown, dentry alloc, socket/pid allocation) because it is a slab freelist UAF — the faulting site is never the bug site, which makes it look like random instability until the dump is examined. --- ## Crash analysis (from kdump vmcore, full matching dbgsym) Panic task and primary oops: ``` PANIC: "Oops: 0000 [#1] PREEMPT SMP NOPTI" COMMAND: "ps" CPU: 37 [exception RIP: dentry_unlink_inode+251] (NULL deref; RAX/RDX/RSI/RDI = 0) #8 dentry_unlink_inode #9 __dentry_kill #10 shrink_dentry_list #11 shrink_dcache_parent #12 d_invalidate #13 lookup_fast #14 walk_component #15 path_lookupat #16 filename_lookup #17 vfs_statx #18 vfs_fstatat #19 __do_sys_newfstatat ``` The corrupted dentry is a procfs pid entry — `/proc/<pid>/cmdline`: ``` struct dentry { d_name.name = "cmdline" d_iname = "cmdline" d_inode = 0x0 <-- already unlinked d_op = pid_dentry_operations d_lockref.count = -128 (0xffffff80) <-- refcount already driven negative } ``` `crash`'s slab validator independently flags the dentry cache as corrupt (no `slub_debug` was active at capture — this is structural freelist validation): ``` kmem: dentry: slab: ffd8d770cc2fe300 invalid freepointer: 7d6cf1f4997700d6 kmem: dentry: slab: ffd8d770cc1abe00 invalid freepointer: 7d6cf1f494205b56 kmem: kmalloc-rcl-64: slab: ffd8d770cc26a700 invalid freepointer: 55ab8f7b3288b69a ``` Three CPUs were simultaneously in dentry alloc/free paths at panic — the race, in one snapshot: | CPU | Task | Operation | Fault | |-----|------|-----------|-------| | 37 | ps | dentry teardown: `dentry_unlink_inode ← __dentry_kill ← shrink_dentry_list ← d_invalidate ← lookup_fast` (`/proc` stat walk) | NULL deref on already-freed dentry (panicked first) | | 4 | ps | dentry teardown: `dentry_unlink_inode ← __dentry_kill ← dput ← lookup_fast ← open_last_lookups ← openat` | same fault site; spinning in `native_queued_spin_lock_slowpath` | | 45 | tar | dentry **allocation**: `kmem_cache_alloc_lru ← __d_alloc ← d_alloc_parallel ← __lookup_slow` (stat walk) | GPF on poisoned freelist pointer; R14 = dentry cache addr | The `tar` GPF register state shows the poisoned pointer being consumed from the dentry slab: ``` [exception RIP: kmem_cache_alloc_lru+221] general protection fault (non-canonical address) RAX: 627117ed820fc609 RDI: 627117ed820fc5a9 <-- garbage freelist pointer R14: ff1a80bec01f6800 <-- dentry kmem_cache ``` This matches earlier pstore-only captures of the same host, where the first event was consistently a GPF in `kmem_cache_alloc_lru` on a non- canonical freelist pointer reached via `__d_alloc` / `alloc_pid` / `sock_alloc_file` — all dentry/slab allocations off the fork/exit hot paths. --- ## What is ruled out - **Not ZFS.** All ZFS caches (`zfs_znode_cache`, `dnode_t`, `dmu_buf_impl_t`, `arc_buf_*`) are intact in `kmem -s` — no `invalid freepointer` — despite millions of live objects. ZFS appears only as a passing frame on the clone path. (Kernel is ZFS-tainted; noted for completeness, but the corrupted cache is core VFS `dentry`, not any ZFS slab.) - **Not AppArmor notification CVEs (USN-8373-1 / CVE-2026-47326..47328).** `apparmor_auditcache` is clean/empty; the AppArmor notification interface is not in active use on these hosts (no `aa-notify` consumer, `features/policy/notify` empty). The fault is in core procfs/VFS dentry handling (`pid_dentry_operations`), unrelated to AppArmor. - **Not hardware.** EDAC/MCE/SEL clean; corruption is structurally consistent (always dentry slab, always teardown/alloc paths), not the random scatter of failing DIMMs. --- ## A/B test (kernel version isolation) Two near-identical heavily loaded hosts that both crashed on -124: - **Host A (vps232):** kept on **6.8.0-124**, kdump-armed, used to capture this vmcore. - **Host B (vps193):** rolled back to **6.8.0-90-generic**, same workload (~90 containers), as control. Expected discriminator within one crash interval: if Host B on -90 stays up while Host A on -124 keeps crashing, the regression is localized to the -90→-124 range. (Result will be added as a follow-up comment.) Note: 6.8.0-124.124 is the newest generic kernel currently published for Noble, so there is no forward kernel to test against — rollback to -90 is the only available containment. --- ## Reproduction conditions Not yet reduced to a minimal reproducer, but reliably reproduced in production by: - High logical-CPU-count host (64) with high process density (~90 LXD containers) - Sustained concurrent `/proc` traversal (host monitoring running `ps`/stat loops) **plus** continuous process churn (per-container php-fpm/nginx fork+exit) **plus** filesystem tree walks (`tar` backups) - i.e. heavy concurrent `__d_alloc` (lookup) and `__dentry_kill`/`proc_flush_pid` (exit + invalidate) against the shared dentry cache Mean time to corruption: ~2–6 days of normal production load. --- ## Artifacts available on request - Full kdump vmcore (`/var/crash/...`, ~17 GB, PARTIAL DUMP via makedumpfile) captured against `linux-image-unsigned-6.8.0-124-generic-dbgsym` 6.8.0-124.124 (matching build-id) - `crash` session output: `bt`, `bt -a` (all 64 CPUs), `kmem -s`, `kmem -S dentry`, `struct dentry` of the corrupted object, `log` - Five prior pstore dmesg captures from the same host showing the recurring signature - apport-collected host/config data (will attach via `ubuntu-bug linux`) ## Planned follow-up Host A is being rebooted with `slub_debug=FZP` to catch the corrupting write **at the bad free** (red-zone/poison validation), which should name the exact freeing path. That trace will be attached as a follow-up comment once the next event is captured. Full 17 GB kdump vmcore (PARTIAL DUMP, makedumpfile) retained on the affected host, captured against linux-image-unsigned-6.8.0-124-generic- dbgsym 6.8.0-124.124 (matching build-id). Available to the assigned engineer on request 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: zfs AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Jun 21 19:29 seq crw-rw---- 1 root audio 116, 33 Jun 21 19:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sun Jun 21 20:43:01 2026 InstallationDate: Installed on 2025-12-01 (202 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 003: ID 0557:9241 ATEN International Co., Ltd SMCI HID KM Bus 001 Device 004: ID 0b1f:03ee Insyde Software Corp. RNDIS/Ethernet Gadget Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Supermicro SYS-611C-TN4R PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-124-generic root=UUID=3e867032-21c4-416e-b45f-a17d1dae6788 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M panic_on_oops=1 panic=10 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.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.7 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: X13DDW-A dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.7:bd07/23/2025:br5.32:svnSupermicro:pnSYS-611C-TN4R:pvr0123456789:rvnSupermicro:rnX13DDW-A:rvr1.01:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: Family dmi.product.name: SYS-611C-TN4R dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "vps232-panic-dmesg.txt.gz" https://bugs.launchpad.net/bugs/2157755/+attachment/5978295/+files/vps232-panic-dmesg.txt.gz -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157755 Title: [linux 6.8.0-124-generic] Dentry-cache slab use-after-free under concurrent /proc lookup + process exit on high-density LXD hosts Status in linux package in Ubuntu: New Bug description: **Package:** linux (Ubuntu Noble 24.04 LTS) **Kernel:** 6.8.0-124-generic #124-Ubuntu SMP PREEMPT_DYNAMIC (Ubuntu 6.8.0-124.124, base 6.8.12) **Severity:** High — repeatable hard crash (kernel panic / reboot) on production hosts, ~every 2–6 days --- ## Summary On heavily loaded LXD container hosts running 6.8.0-124-generic, the kernel panics repeatedly with memory corruption localized to the **dentry slab cache**. A captured kdump vmcore shows a **use-after- free**: the dentry slab freelist is overwritten with non-pointer garbage, and concurrent threads doing `/proc` path lookups and process-exit dentry teardown fault on the corrupted objects. The corruption is confirmed by `crash`'s own slab validator (`kmem -s` reports `invalid freepointer` on dentry slabs) and by three CPUs caught mid-fault in the same dentry alloc/free paths in a single core. The same workload on **6.8.0-90-generic does not exhibit the crash** (see A/B test below), which points to a regression in the dentry/procfs path between -90 and -124, or to a latent race newly exposed by changes in that range. --- ## Environment - **Hardware:** Supermicro SYS-611C-TN4R / X13DDW-A, BIOS 2.7 (07/23/2025), dual-socket, 64 logical CPUs, 256 GB RAM - **Root/storage:** OpenZFS (zfs 2.2.2-0ubuntu9.4), kernel tainted `PO` (out-of-tree + proprietary ZFS module) - **Workload:** ~90 LXD system containers (managed WordPress hosting); very high concurrent fork/exit and `/proc` scanning from per-container nginx / php-fpm / mariadbd / redis plus host-side monitoring (`ps`), backups (`tar`) - **Crash cadence:** every ~2–6 days; uptime at this capture was 8 days - **EDAC/MCE:** clean (`ras-mc-ctl --summary/--errors` show no memory or PCIe errors; IPMI SEL clean apart from PSU/chassis noise) — not a hardware memory fault --- ## Impact Each event is a hard kernel panic. With `panic_on_oops=1` / `panic=10` the host self-reboots, but every crash is a full outage of ~90 tenant containers. The corruption surfaces in unrelated subsystems (dentry teardown, dentry alloc, socket/pid allocation) because it is a slab freelist UAF — the faulting site is never the bug site, which makes it look like random instability until the dump is examined. --- ## Crash analysis (from kdump vmcore, full matching dbgsym) Panic task and primary oops: ``` PANIC: "Oops: 0000 [#1] PREEMPT SMP NOPTI" COMMAND: "ps" CPU: 37 [exception RIP: dentry_unlink_inode+251] (NULL deref; RAX/RDX/RSI/RDI = 0) #8 dentry_unlink_inode #9 __dentry_kill #10 shrink_dentry_list #11 shrink_dcache_parent #12 d_invalidate #13 lookup_fast #14 walk_component #15 path_lookupat #16 filename_lookup #17 vfs_statx #18 vfs_fstatat #19 __do_sys_newfstatat ``` The corrupted dentry is a procfs pid entry — `/proc/<pid>/cmdline`: ``` struct dentry { d_name.name = "cmdline" d_iname = "cmdline" d_inode = 0x0 <-- already unlinked d_op = pid_dentry_operations d_lockref.count = -128 (0xffffff80) <-- refcount already driven negative } ``` `crash`'s slab validator independently flags the dentry cache as corrupt (no `slub_debug` was active at capture — this is structural freelist validation): ``` kmem: dentry: slab: ffd8d770cc2fe300 invalid freepointer: 7d6cf1f4997700d6 kmem: dentry: slab: ffd8d770cc1abe00 invalid freepointer: 7d6cf1f494205b56 kmem: kmalloc-rcl-64: slab: ffd8d770cc26a700 invalid freepointer: 55ab8f7b3288b69a ``` Three CPUs were simultaneously in dentry alloc/free paths at panic — the race, in one snapshot: | CPU | Task | Operation | Fault | |-----|------|-----------|-------| | 37 | ps | dentry teardown: `dentry_unlink_inode ← __dentry_kill ← shrink_dentry_list ← d_invalidate ← lookup_fast` (`/proc` stat walk) | NULL deref on already-freed dentry (panicked first) | | 4 | ps | dentry teardown: `dentry_unlink_inode ← __dentry_kill ← dput ← lookup_fast ← open_last_lookups ← openat` | same fault site; spinning in `native_queued_spin_lock_slowpath` | | 45 | tar | dentry **allocation**: `kmem_cache_alloc_lru ← __d_alloc ← d_alloc_parallel ← __lookup_slow` (stat walk) | GPF on poisoned freelist pointer; R14 = dentry cache addr | The `tar` GPF register state shows the poisoned pointer being consumed from the dentry slab: ``` [exception RIP: kmem_cache_alloc_lru+221] general protection fault (non-canonical address) RAX: 627117ed820fc609 RDI: 627117ed820fc5a9 <-- garbage freelist pointer R14: ff1a80bec01f6800 <-- dentry kmem_cache ``` This matches earlier pstore-only captures of the same host, where the first event was consistently a GPF in `kmem_cache_alloc_lru` on a non- canonical freelist pointer reached via `__d_alloc` / `alloc_pid` / `sock_alloc_file` — all dentry/slab allocations off the fork/exit hot paths. --- ## What is ruled out - **Not ZFS.** All ZFS caches (`zfs_znode_cache`, `dnode_t`, `dmu_buf_impl_t`, `arc_buf_*`) are intact in `kmem -s` — no `invalid freepointer` — despite millions of live objects. ZFS appears only as a passing frame on the clone path. (Kernel is ZFS-tainted; noted for completeness, but the corrupted cache is core VFS `dentry`, not any ZFS slab.) - **Not AppArmor notification CVEs (USN-8373-1 / CVE-2026-47326..47328).** `apparmor_auditcache` is clean/empty; the AppArmor notification interface is not in active use on these hosts (no `aa-notify` consumer, `features/policy/notify` empty). The fault is in core procfs/VFS dentry handling (`pid_dentry_operations`), unrelated to AppArmor. - **Not hardware.** EDAC/MCE/SEL clean; corruption is structurally consistent (always dentry slab, always teardown/alloc paths), not the random scatter of failing DIMMs. --- ## A/B test (kernel version isolation) Two near-identical heavily loaded hosts that both crashed on -124: - **Host A (vps232):** kept on **6.8.0-124**, kdump-armed, used to capture this vmcore. - **Host B (vps193):** rolled back to **6.8.0-90-generic**, same workload (~90 containers), as control. Expected discriminator within one crash interval: if Host B on -90 stays up while Host A on -124 keeps crashing, the regression is localized to the -90→-124 range. (Result will be added as a follow-up comment.) Note: 6.8.0-124.124 is the newest generic kernel currently published for Noble, so there is no forward kernel to test against — rollback to -90 is the only available containment. --- ## Reproduction conditions Not yet reduced to a minimal reproducer, but reliably reproduced in production by: - High logical-CPU-count host (64) with high process density (~90 LXD containers) - Sustained concurrent `/proc` traversal (host monitoring running `ps`/stat loops) **plus** continuous process churn (per-container php-fpm/nginx fork+exit) **plus** filesystem tree walks (`tar` backups) - i.e. heavy concurrent `__d_alloc` (lookup) and `__dentry_kill`/`proc_flush_pid` (exit + invalidate) against the shared dentry cache Mean time to corruption: ~2–6 days of normal production load. --- ## Artifacts available on request - Full kdump vmcore (`/var/crash/...`, ~17 GB, PARTIAL DUMP via makedumpfile) captured against `linux-image-unsigned-6.8.0-124-generic-dbgsym` 6.8.0-124.124 (matching build-id) - `crash` session output: `bt`, `bt -a` (all 64 CPUs), `kmem -s`, `kmem -S dentry`, `struct dentry` of the corrupted object, `log` - Five prior pstore dmesg captures from the same host showing the recurring signature - apport-collected host/config data (will attach via `ubuntu-bug linux`) ## Planned follow-up Host A is being rebooted with `slub_debug=FZP` to catch the corrupting write **at the bad free** (red-zone/poison validation), which should name the exact freeing path. That trace will be attached as a follow- up comment once the next event is captured. Full 17 GB kdump vmcore (PARTIAL DUMP, makedumpfile) retained on the affected host, captured against linux-image- unsigned-6.8.0-124-generic-dbgsym 6.8.0-124.124 (matching build-id). Available to the assigned engineer on request 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: zfs AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Jun 21 19:29 seq crw-rw---- 1 root audio 116, 33 Jun 21 19:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sun Jun 21 20:43:01 2026 InstallationDate: Installed on 2025-12-01 (202 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 003: ID 0557:9241 ATEN International Co., Ltd SMCI HID KM Bus 001 Device 004: ID 0b1f:03ee Insyde Software Corp. RNDIS/Ethernet Gadget Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Supermicro SYS-611C-TN4R PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-124-generic root=UUID=3e867032-21c4-416e-b45f-a17d1dae6788 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M panic_on_oops=1 panic=10 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.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.7 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: X13DDW-A dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.7:bd07/23/2025:br5.32:svnSupermicro:pnSYS-611C-TN4R:pvr0123456789:rvnSupermicro:rnX13DDW-A:rvr1.01:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: Family dmi.product.name: SYS-611C-TN4R dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157755/+subscriptions

[Bug 2088733]

Maybe it's time to submit the quirk for the next kernel release, unless there are further tests to be done. Here, even with the updated kernel and firmware, the issue persists. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2088733 Title: low CPU frequency after wake up AMD Ryzen Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After wake up I can see at least once a week issue with CPU frequency not going up. When running: $ watch lscpu -e=CPU,MHZ standard output looks like: CPU MHZ 0 400.0000 1 1383.2480 2 400.0000 3 400.0000 4 400.0000 5 2699.7561 6 1288.0500 7 400.0000 8 400.0000 9 400.0000 10 400.0000 11 400.0000 12 3244.0720 13 400.0000 14 400.0000 15 1295.9050 while when the issue occurs, I can't see 600 Mhz or higher values in the same graph. Which also means that response time of computer is much lower and everything feels lazy. Restart fixes the issue or plug power cable off and in again. My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16 My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024 OS version: Ubuntu 24.04.1 LTS My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC I know about one more person with same machine type with the issue and there is also this question on askubuntu which says there is third person with this issue. https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up- in-ubuntu-24-04-1 This bug looks pretty similar however should be fixed already, so creating new one https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2088733/+subscriptions

[Bug 2157741] [NEW] [Dell Latitude 7280][Intel HD 620] Black screen and system freeze after display power-off or suspend; fixed by i915.enable_dc=0

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