Following up on the upstream submission requested above: The ARL004 fix has now been submitted upstream to linux-pci and linux-kernel: [PATCH] PCI: vmd: Enable interrupt ordering quirk for Arrow Lake Message-ID: <20260910200539.10862-1-gvozd188@mail.ru> Date: 2026-09-10 The patch is publicly archived on the Linux PCI mailing list and has also passed Sashiko's automated review with no regressions reported. This patch links back to Launchpad bug #2166325 and has been tested on the affected Intel VMD 8086:ad0b hardware. Since the requested upstream submission has now been completed, could the Ubuntu kernel task please be reconsidered rather than left as Won't Fix? I understand that upstream maintainer review may still be pending. If Ubuntu requires upstream acceptance before reconsidering the SRU, please clarify that requirement so I know what the remaining blocker is. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166325 Title: Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 causes NVMe completion stalls Status in linux package in Ubuntu: Won't Fix Bug description: SRU Justification: Impact: On Intel VMD 8086:ad0b / Arrow Lake-HX systems, Ubuntu 26.04 with the 7.0.x kernel has two VMD-related problems. First, the stock VMD driver does not support Bus Offset Setting 3. On the affected MSI Vector this results in: vmd 0000:00:0e.0: Unknown Bus Offset Setting (3) and prevents enumeration of the internal NVMe device behind VMD. After adding the required second-rootbus / Bus Offset 3 support, a second issue is exposed: repeated NVMe timeout, completion polled events caused by the Intel Arrow Lake ARL004 interrupt-ordering erratum. These events cause severe storage stalls and make the system practically unusable under sustained I/O. Launchpad bug #2166325 is now Confirmed and affects multiple users. Fix: The fix is implemented as two logically separate changes: Add Intel VMD second-rootbus / Bus Offset 3 support so that NVMe devices behind VMD 8086:ad0b can be enumerated correctly. Apply an ARL004-specific interrupt-ordering workaround for VMD 8086:ad0b and child PCI_CLASS_STORAGE_EXPRESS devices. Before dispatching the child interrupt with generic_handle_irq(), perform a dummy PCI configuration-space read from the MSI-initiating NVMe device. The read is serialized with the existing VMD configuration-space lock. The workaround is deliberately limited to VMD 8086:ad0b and NVMe-class child devices, so other VMD devices and non-NVMe children are unaffected. The stock drivers/pci/controller/vmd.c in Ubuntu 7.0.0-30.30 and 7.0.0-31.31 is byte-for-byte identical: SHA256: b631d449d8e1e896bcf1fa1e4ade53789d28db3c86c6a15fb7fb7e506cd274c8 The patched vmd.c used successfully with Ubuntu 7.0.0-31-generic is: SHA256: 0a27aa1379e8b7fc22f509b8d06ed3676a211d7bb3226a3f9b3dadfc208be7a3 Testcase: Hardware: MSI Vector 17 HX AI, Intel VMD 8086:ad0b, NVMe behind VMD. With the stock driver: Boot Ubuntu 26.04 with the affected 7.0.x kernel. Verify that Bus Offset Setting 3 causes the VMD driver to fail NVMe enumeration. After Bus Offset 3 support is added but without the ARL004 workaround, run sustained sequential NVMe reads and monitor the kernel log. Repeated nvme nvme0: I/O tag ... timeout, completion polled events occur at approximately 30-second intervals. A 1 GiB sequential read took approximately 121 seconds (~8.8 MB/s). With both fixes applied: The internal NVMe is enumerated normally. The recurring timeout, completion polled events disappear. The same 1 GiB read completes in approximately 0.88 seconds (~1.2 GB/s). A subsequent 10 GiB sequential read also completes normally. The same patched implementation is currently running successfully on Ubuntu 7.0.0-31-generic. Source and patch series: https://github.com/gvozd188/vmd-arl004 Original public implementation: https://github.com/gvozd188/vmd-arl004/commit/5438c83 Hardware ======== Laptop: MSI Vector 17 HX AI Platform: Intel Arrow Lake Intel VMD: 8086:ad0b VMD PCI address: 0000:00:0e.0 Subsystem: 1462:149c Internal NVMe SSD: Phison 1TB ESR01TBYCCA4-EDJ-2MS Controller: Phison PS5029-E29T PCIe 4.0 NVMe PCI ID: 1987:5029 (rev 01) Firmware: ETFM50.0 Ubuntu: 26.04 Current/final tested kernel: 7.0.0-30-generic Secure Boot: enabled Problem 1: Intel VMD Bus Offset 3 ================================ With the stock Ubuntu VMD driver the internal NVMe SSD is not exposed. The kernel reports: vmd 0000:00:0e.0: Unknown Bus Offset Setting (3) and no internal /dev/nvme* device is available. Linux 6.14 was also tested on this machine and did not solve the VMD problem. The system firmware does not expose a usable BIOS option to disable Intel VMD/RST. Intel's public VMD second-rootbus patch series was integrated into the Ubuntu VMD source: [PATCH v3 0/8] VMD add second rootbus support https://www.spinics.net/lists/linux-pci/msg163096.html After integrating the second-rootbus support, Linux successfully enumerates the internal NVMe controller and SSD. Problem 2: NVMe completion stalls ================================= After the SSD became accessible through the modified VMD driver, a second problem became visible. Kernel messages repeatedly contained: nvme nvme0: I/O tag ... timeout, completion polled The stalls occurred at approximately 30-second intervals. A diagnostic sequential read before the workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress Result: 1 GiB in approximately 121.339 seconds approximately 8.8 MB/s CPU and memory were not saturated. Disabling ASPM was tested and did not solve the problem. ARL004 investigation ==================== The official Intel RST/VMD Windows driver distributed by MSI for this machine was examined by static analysis for comparison. The relevant Windows driver path performs a PCI configuration-space read after MSI handling when the completion state requires ordering. This behavior is consistent with the Intel Arrow Lake ARL004 erratum, where an MSI from a VMD-owned device may pass a preceding memory write. An experimental Linux workaround was implemented for the tested 8086:ad0b VMD/NVMe path. It performs a dummy PCI configuration-space read before the subsequent interrupt handling path. Result ====== With the experimental ARL004 workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress completed in: 1 GiB in 0.88206 seconds approximately 1.2 GB/s A subsequent 10 GiB sequential diagnostic read also completed normally. After booting with the final tested module: sudo journalctl -k -b | grep -E 'timeout|completion polled' produced no matching messages. The approximately 136x difference above is only a diagnostic comparison on this specific machine and is not intended as a general SSD benchmark. Reproduction / reference implementation ======================================= The complete investigation, tested source, separate patches, combined patch, known-working module, SHA256 checksums, installation/bootstrap procedure and recovery procedure are published here: https://github.com/gvozd188/vmd-arl004 Exact reference commit: https://github.com/gvozd188/vmd-arl004/commit/5438c83 Relevant files: 0001-vmd-second-rootbus-intel.patch Integration of Intel's second-rootbus support. 0002-vmd-ad0b-arl004-workaround.patch Experimental ARL004 workaround. vmd-arl004.patch Combined patch. vmd-ubuntu-7.0.0-30.c Ubuntu VMD source used as the patch base. vmd.c Final tested source. vmd.ko Known-working reference module for 7.0.0-30-generic. Known-working source SHA256: 0a27aa1379e8b7fc22f509b8d06ed3676a211d7bb3226a3f9b3dadfc208be7a3 Known-working module SHA256: b2c9eacb720d45fcaab15ff09ad3fdc2e97b8a6dd215c80fa282090ff8d2b2cd Installation history ==================== Because the stock VMD driver could not expose the internal SSD, an existing Ubuntu HDD from another laptop was connected to the MSI Vector through a SATA-to-USB adapter. The MSI Vector was booted directly from that HDD. That Ubuntu environment was running kernel 7.0.0-30-generic. The modified VMD driver was used there to expose the internal NVMe SSD. Ubuntu was then manually deployed onto the dedicated Ubuntu partition of the internal SSD without modifying the existing Windows and data partitions. The manually deployed SSD installation initially contained kernel 7.0.0-14-generic. This kernel was not intentionally selected as a VMD workaround; it was simply the kernel present in the manually deployed system at that stage. A compatible custom VMD module was installed for 7.0.0-14-generic and added to its initramfs, allowing the first independent boot from the internal SSD. Only after that successful SSD boot was DKMS configured. The SSD installation was subsequently updated to 7.0.0-30-generic, where the final VMD/ARL004 development and testing was performed. Expected result =============== The stock Ubuntu kernel should: 1. correctly enumerate the second-rootbus / Bus Offset 3 topology on Intel VMD 8086:ad0b; 2. expose the internal NVMe SSD; 3. handle NVMe completion ordering without repeated approximately 30-second completion timeouts. Actual result ============= With the stock VMD driver, the internal SSD is not exposed because Bus Offset Setting 3 is rejected. After adding second-rootbus support alone, the SSD becomes visible but repeated NVMe completion stalls occur on this hardware. The experimental ARL004 ordering workaround eliminates the observed stalls on the tested system. Notes ===== The ARL004 workaround is experimental and platform-specific. I am reporting the observed hardware behavior and the tested workaround rather than claiming that this implementation is the appropriate final upstream fix. The Windows driver binary is not redistributed in the GitHub repository. Only identification information, hashes and static-analysis notes are provided. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gvozd188 2323 F.... pipewire gvozd188 2360 F.... wireplumber /dev/snd/controlC0: gvozd188 2360 F.... wireplumber /dev/snd/seq: gvozd188 2323 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 13:08:10 2026 MachineType: Micro-Star International Co., Ltd. Vector 17 HX AI A2XWIG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=fef65fb9-b1c4-4bbe-9c02-92a4a7280fee ro quiet splash iommu=pt 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) WifiSyslog: dmi.bios.date: 04/20/2026 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17S3IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-17S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17S3IMS.112:bd04/20/2026:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnVector17HXAIA2XWIG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17S3.1:pfaVector: dmi.product.family: Vector dmi.product.name: Vector 17 HX AI A2XWIG dmi.product.sku: 17S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166325/+subscriptions
пятница
[Bug 2168586] [NEW] Jammy update: v5.15.220 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.220 upstream stable release from git://git.kernel.org/ RDMA/rxe: Fix OOB in free_rd_atomic_resources() ext4: don't enable DAX on new encrypted files io_uring/io-wq: fix worker accounting when canceling creation callbacks ipvs: reload ip header after head reallocation bpf: Remove tst_run from lwt_seg6local_prog_ops. jfs: add check read-only before truncation in jfs_truncate_nolock() jfs: add check read-only before txBeginAnon() call can: j1939: implement NETDEV_UNREGISTER notification handler can: j1939: add missing calls in NETDEV_UNREGISTER notification handler can: j1939: make j1939_sk_bind() fail if device is no longer registered KVM: arm64: Prevent access to vCPU events before init bpf: Fix use-after-free in offloaded map/prog info fill Revert "PM: sleep: Use complete() in device_pm_sleep_init()" smc: Use __sk_dst_get() and dst_dev_rcu() in smc_vlan_by_tcpsk(). selinux: switch two allocations to use kzalloc_objs() ALSA: pcm: fix wait_time calculations ASoC: tegra: Fix Master Volume Control ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() ALSA: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() kcov: replace local_irq_save() with a local_lock_t kcov: fix data corruption and race conditions on PREEMPT_RT ext4: propagate errors from fast commit range replay nilfs2: correct return value kernel-doc descriptions for ioctl functions nilfs2: reject invalid block index in GC ioctl nfc: nci: add data_len bound checks to activation parameter extractors HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() nvme: rename CDR/MORE/DNR to NVME_STATUS_* nvmet-tcp: bound SGL data length before allocating command buffers HID: uclogic: fix use-after-free of inrange_timer on remove HID: ft260: fix i2c probing for hwmon devices HID: ft260: improve i2c write performance HID: ft260: improve i2c large reads performance HID: ft260: skip unexpected HID input reports HID: ft260: wake up device from power saving mode HID: ft260: missed NACK from busy device HID: ft260: validate i2c input report length HID: ft260: fix stack-use-after-return write in I2C read race HID: input: read battery capacity from its actual report offset fpga: dfl: fme: add error handling accessibility: speakup: unregister tty ldisc on later init failures xhci: dbgtty: Fix unregister on tty_register_driver() failure xhci: dbgtty: Fix unregister on tty_alloc_driver() failure fuse: fix invalidate lock leak on setattr writeback failure fuse: fix invalidate lock leak on open O_TRUNC DAX failure usb: usbtest: disable dynamic ID support usb: gadget: f_tcm: keep port count until LUN teardown completes xfrm: espintcp: fix UAF during close xfrm: drop ESP-in-TCP packets with no ingress device xfrm: ah6: validate routing header segments_left xfrm: fix xfrm_state_construct() auth-trunc leak net: bridge: mcast: fix use-after-free of a master VLAN's multicast context ipv6: seg6: clear IPv4 control block on IPIP decapsulation mm/swap: reject swapon() on filesystem-level encrypted files crypto: atmel-tdes - use scatterlist length before DMA mapping crypto: qce - fix CCM AAD buffer underallocation crypto: mxs-dcp - fix source scatterlist length access crypto: qce - Remove unsafe/deprecated algorithms KVM: s390: vsie: zero stale crypto bits usb: core: Add lock to usb_wakeup_notification() usb: core: Strengthen error handling in hub_hub_status() ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() ALSA: usb-audio: Complete cleanup after system-resume errors USB: serial: option: fix slab OOB read in interrupt URB callback USB: serial: spcp8x5: drop broken carrier detect support USB: c67x00: fix use-after-free in c67x00_add_iso_urb() usb: usbfs: fix use-after-free of usb_device in usbdev_release() Linux 5.15.220 UBUNTU: Upstream stable to v5.15.220 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Vinicius Peixoto (vpeixoto) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Vinicius Peixoto (vpeixoto) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.220 upstream stable release from git://git.kernel.org/ - + RDMA/rxe: Fix OOB in free_rd_atomic_resources() + ext4: don't enable DAX on new encrypted files + io_uring/io-wq: fix worker accounting when canceling creation callbacks + ipvs: reload ip header after head reallocation + bpf: Remove tst_run from lwt_seg6local_prog_ops. + jfs: add check read-only before truncation in jfs_truncate_nolock() + jfs: add check read-only before txBeginAnon() call + can: j1939: implement NETDEV_UNREGISTER notification handler + can: j1939: add missing calls in NETDEV_UNREGISTER notification handler + can: j1939: make j1939_sk_bind() fail if device is no longer registered + KVM: arm64: Prevent access to vCPU events before init + bpf: Fix use-after-free in offloaded map/prog info fill + Revert "PM: sleep: Use complete() in device_pm_sleep_init()" + smc: Use __sk_dst_get() and dst_dev_rcu() in smc_vlan_by_tcpsk(). + selinux: switch two allocations to use kzalloc_objs() + ALSA: pcm: fix wait_time calculations + ASoC: tegra: Fix Master Volume Control + ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() + ALSA: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams + ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() + kcov: replace local_irq_save() with a local_lock_t + kcov: fix data corruption and race conditions on PREEMPT_RT + ext4: propagate errors from fast commit range replay + nilfs2: correct return value kernel-doc descriptions for ioctl functions + nilfs2: reject invalid block index in GC ioctl + nfc: nci: add data_len bound checks to activation parameter extractors + HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() + nvme: rename CDR/MORE/DNR to NVME_STATUS_* + nvmet-tcp: bound SGL data length before allocating command buffers + HID: uclogic: fix use-after-free of inrange_timer on remove + HID: ft260: fix i2c probing for hwmon devices + HID: ft260: improve i2c write performance + HID: ft260: improve i2c large reads performance + HID: ft260: skip unexpected HID input reports + HID: ft260: wake up device from power saving mode + HID: ft260: missed NACK from busy device + HID: ft260: validate i2c input report length + HID: ft260: fix stack-use-after-return write in I2C read race + HID: input: read battery capacity from its actual report offset + fpga: dfl: fme: add error handling + accessibility: speakup: unregister tty ldisc on later init failures + xhci: dbgtty: Fix unregister on tty_register_driver() failure + xhci: dbgtty: Fix unregister on tty_alloc_driver() failure + fuse: fix invalidate lock leak on setattr writeback failure + fuse: fix invalidate lock leak on open O_TRUNC DAX failure + usb: usbtest: disable dynamic ID support + usb: gadget: f_tcm: keep port count until LUN teardown completes + xfrm: espintcp: fix UAF during close + xfrm: drop ESP-in-TCP packets with no ingress device + xfrm: ah6: validate routing header segments_left + xfrm: fix xfrm_state_construct() auth-trunc leak + net: bridge: mcast: fix use-after-free of a master VLAN's multicast context + ipv6: seg6: clear IPv4 control block on IPIP decapsulation + mm/swap: reject swapon() on filesystem-level encrypted files + crypto: atmel-tdes - use scatterlist length before DMA mapping + crypto: qce - fix CCM AAD buffer underallocation + crypto: mxs-dcp - fix source scatterlist length access + crypto: qce - Remove unsafe/deprecated algorithms + KVM: s390: vsie: zero stale crypto bits + usb: core: Add lock to usb_wakeup_notification() + usb: core: Strengthen error handling in hub_hub_status() + ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() + ALSA: usb-audio: Complete cleanup after system-resume errors + USB: serial: option: fix slab OOB read in interrupt URB callback + USB: serial: spcp8x5: drop broken carrier detect support + USB: c67x00: fix use-after-free in c67x00_add_iso_urb() + usb: usbfs: fix use-after-free of usb_device in usbdev_release() Linux 5.15.220 - usb: usbfs: fix use-after-free of usb_device in usbdev_release() - USB: c67x00: fix use-after-free in c67x00_add_iso_urb() - USB: serial: spcp8x5: drop broken carrier detect support - USB: serial: option: fix slab OOB read in interrupt URB callback - ALSA: usb-audio: Complete cleanup after system-resume errors - ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() - usb: core: Strengthen error handling in hub_hub_status() - usb: core: Add lock to usb_wakeup_notification() - KVM: s390: vsie: zero stale crypto bits - crypto: qce - Remove unsafe/deprecated algorithms - crypto: mxs-dcp - fix source scatterlist length access - crypto: qce - fix CCM AAD buffer underallocation - crypto: atmel-tdes - use scatterlist length before DMA mapping - mm/swap: reject swapon() on filesystem-level encrypted files - ipv6: seg6: clear IPv4 control block on IPIP decapsulation - net: bridge: mcast: fix use-after-free of a master VLAN's multicast context - xfrm: fix xfrm_state_construct() auth-trunc leak - xfrm: ah6: validate routing header segments_left - xfrm: drop ESP-in-TCP packets with no ingress device - xfrm: espintcp: fix UAF during close - usb: gadget: f_tcm: keep port count until LUN teardown completes - usb: usbtest: disable dynamic ID support - fuse: fix invalidate lock leak on open O_TRUNC DAX failure - fuse: fix invalidate lock leak on setattr writeback failure - xhci: dbgtty: Fix unregister on tty_alloc_driver() failure - xhci: dbgtty: Fix unregister on tty_register_driver() failure - accessibility: speakup: unregister tty ldisc on later init failures - fpga: dfl: fme: add error handling - HID: input: read battery capacity from its actual report offset - HID: ft260: fix stack-use-after-return write in I2C read race - HID: ft260: validate i2c input report length - HID: ft260: missed NACK from busy device - HID: ft260: wake up device from power saving mode - HID: ft260: skip unexpected HID input reports - HID: ft260: improve i2c large reads performance - HID: ft260: improve i2c write performance - HID: ft260: fix i2c probing for hwmon devices - HID: uclogic: fix use-after-free of inrange_timer on remove - nvmet-tcp: bound SGL data length before allocating command buffers - nvme: rename CDR/MORE/DNR to NVME_STATUS_* - HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() - nfc: nci: add data_len bound checks to activation parameter extractors - nilfs2: reject invalid block index in GC ioctl - nilfs2: correct return value kernel-doc descriptions for ioctl functions - ext4: propagate errors from fast commit range replay - kcov: fix data corruption and race conditions on PREEMPT_RT - kcov: replace local_irq_save() with a local_lock_t - ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() - ALSA: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams - ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() - ASoC: tegra: Fix Master Volume Control - ALSA: pcm: fix wait_time calculations - Revert "smb: client: use kvzalloc() for megabyte buffer in simple fallocate" - Revert "mtd: maps: vmu-flash: fix fault in unaligned fixup" - selinux: switch two allocations to use kzalloc_objs() - smc: Use __sk_dst_get() and dst_dev_rcu() in smc_vlan_by_tcpsk(). - Revert "PM: sleep: Use complete() in device_pm_sleep_init()" - bpf: Fix use-after-free in offloaded map/prog info fill - KVM: arm64: Prevent access to vCPU events before init - can: j1939: make j1939_sk_bind() fail if device is no longer registered - can: j1939: add missing calls in NETDEV_UNREGISTER notification handler - can: j1939: implement NETDEV_UNREGISTER notification handler - jfs: add check read-only before txBeginAnon() call - jfs: add check read-only before truncation in jfs_truncate_nolock() - bpf: Remove tst_run from lwt_seg6local_prog_ops. - ipvs: reload ip header after head reallocation - io_uring/io-wq: fix worker accounting when canceling creation callbacks - ext4: don't enable DAX on new encrypted files - RDMA/rxe: Fix OOB in free_rd_atomic_resources() + UBUNTU: Upstream stable to v5.15.220 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168586 Title: Jammy update: v5.15.220 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.220 upstream stable release from git://git.kernel.org/ RDMA/rxe: Fix OOB in free_rd_atomic_resources() ext4: don't enable DAX on new encrypted files io_uring/io-wq: fix worker accounting when canceling creation callbacks ipvs: reload ip header after head reallocation bpf: Remove tst_run from lwt_seg6local_prog_ops. jfs: add check read-only before truncation in jfs_truncate_nolock() jfs: add check read-only before txBeginAnon() call can: j1939: implement NETDEV_UNREGISTER notification handler can: j1939: add missing calls in NETDEV_UNREGISTER notification handler can: j1939: make j1939_sk_bind() fail if device is no longer registered KVM: arm64: Prevent access to vCPU events before init bpf: Fix use-after-free in offloaded map/prog info fill Revert "PM: sleep: Use complete() in device_pm_sleep_init()" smc: Use __sk_dst_get() and dst_dev_rcu() in smc_vlan_by_tcpsk(). selinux: switch two allocations to use kzalloc_objs() ALSA: pcm: fix wait_time calculations ASoC: tegra: Fix Master Volume Control ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() ALSA: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() kcov: replace local_irq_save() with a local_lock_t kcov: fix data corruption and race conditions on PREEMPT_RT ext4: propagate errors from fast commit range replay nilfs2: correct return value kernel-doc descriptions for ioctl functions nilfs2: reject invalid block index in GC ioctl nfc: nci: add data_len bound checks to activation parameter extractors HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() nvme: rename CDR/MORE/DNR to NVME_STATUS_* nvmet-tcp: bound SGL data length before allocating command buffers HID: uclogic: fix use-after-free of inrange_timer on remove HID: ft260: fix i2c probing for hwmon devices HID: ft260: improve i2c write performance HID: ft260: improve i2c large reads performance HID: ft260: skip unexpected HID input reports HID: ft260: wake up device from power saving mode HID: ft260: missed NACK from busy device HID: ft260: validate i2c input report length HID: ft260: fix stack-use-after-return write in I2C read race HID: input: read battery capacity from its actual report offset fpga: dfl: fme: add error handling accessibility: speakup: unregister tty ldisc on later init failures xhci: dbgtty: Fix unregister on tty_register_driver() failure xhci: dbgtty: Fix unregister on tty_alloc_driver() failure fuse: fix invalidate lock leak on setattr writeback failure fuse: fix invalidate lock leak on open O_TRUNC DAX failure usb: usbtest: disable dynamic ID support usb: gadget: f_tcm: keep port count until LUN teardown completes xfrm: espintcp: fix UAF during close xfrm: drop ESP-in-TCP packets with no ingress device xfrm: ah6: validate routing header segments_left xfrm: fix xfrm_state_construct() auth-trunc leak net: bridge: mcast: fix use-after-free of a master VLAN's multicast context ipv6: seg6: clear IPv4 control block on IPIP decapsulation mm/swap: reject swapon() on filesystem-level encrypted files crypto: atmel-tdes - use scatterlist length before DMA mapping crypto: qce - fix CCM AAD buffer underallocation crypto: mxs-dcp - fix source scatterlist length access crypto: qce - Remove unsafe/deprecated algorithms KVM: s390: vsie: zero stale crypto bits usb: core: Add lock to usb_wakeup_notification() usb: core: Strengthen error handling in hub_hub_status() ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() ALSA: usb-audio: Complete cleanup after system-resume errors USB: serial: option: fix slab OOB read in interrupt URB callback USB: serial: spcp8x5: drop broken carrier detect support USB: c67x00: fix use-after-free in c67x00_add_iso_urb() usb: usbfs: fix use-after-free of usb_device in usbdev_release() Linux 5.15.220 UBUNTU: Upstream stable to v5.15.220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168586/+subscriptions
[Bug 2168581] Re: Kernel 7.3.0-5 / -6: ZFS not working properly
** 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/2168581 Title: Kernel 7.3.0-5 / -6: ZFS not working properly Status in linux package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: Ubuntu 26.10 Stonking (Development version from 2026-09-20). Kernel: 7.3.0-5 and 7.3.0-6 (from -proposed) On a system with a ZFS root, after installation, I am unable to create or use any additional zfs pools. Details: Encrypted ZFS or not doesn't matter Kernel 7.3.0-5 (OpenZFS 2.4.4-1ubuntu2) and 7.3.0-6 (OpenZFS 2.4.4-1ubuntu3): FAILS. Kernel 7.2.0-5 with OpenZFS 2.4.2: WORKS. Kernel 7.2.0-5 with OpenZFS 2.4.4 (OpenZFS 2.4.4-1ubuntu3): WORKS. No -proposed, only kernel from -proposed, or all from -proposed as of submission time tested and gave same results. Quick reproduction way: 1) Install Ubuntu 26.10 Stonking development with ZFS root. Encrypted or not does not matter. 2) Boot system. It works as it should. 3) Run the following command: sudo -i bash -c 'uname -r; zfs version; truncate -s 1G /root/t.img && zpool create tp /root/t.img; echo "rc=${?}"; zpool list -H tp; zpool destroy tp 2>/dev/null; rm -f /root/t.img' What it does: - Prints out the kernel and zfs information. - Creates a 1G file in /root: /root/t.img. - Creates a zpool called "tp" on /root/t.img. - Prints the rc. Working should be 0. Not working is 1. - Displays the zpool. - Destroys the pool. - Removes the file from /root. Expected result: rc=0 and a created zpool. Received result: rc=1 and no zpool. If you create the partitions manually and make a manual installation including a home directory pool (hpool), the hpool cannot be imported, as the userspace receives ENOENT. There is a patch to fix this (debian/patches/linux-7.3-kthread-nullfs.patch), but it is insufficient, as it stores the initial root directory, which is then the initramfs and not the running root. I have written a patch that I will submit after I create the bug report that fixes it in all scenarios I have thought of. The log supplied shows the commands executed and the outcome. With my patch it gives rc=0 and works. // Stefan ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: zfsutils-linux 2.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 7.3.0-5.5-generic 7.3.0-rc3 Uname: Linux 7.3.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 21:14:20 2026 InstallationDate: Installed on 2026-09-25 (0 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Daily amd64 (20260920) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168581/+subscriptions
[Bug 2168537] Re: Please backport "drm/amdgpu: fix check in amdgpu_hmm_invalidate_gfx" (52f650963d88) to resolute 7.0 - NULL deref in kcompactd kills the system
** 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/2168537 Title: Please backport "drm/amdgpu: fix check in amdgpu_hmm_invalidate_gfx" (52f650963d88) to resolute 7.0 - NULL deref in kcompactd kills the system Status in linux package in Ubuntu: New Bug description: [Impact] On Ubuntu 26.04 (linux 7.0.0-31 and 7.0.0-34, based on 7.0.14), with an AMD GPU using amdgpu userptr BOs, kcompactd page migration calls amdgpu_hmm_invalidate_gfx() while a userptr BO is still being allocated or freed. At that point bo->vm_bo is NULL, and the kernel dereferences it: BUG: kernel NULL pointer dereference, address: 0000000000000000 Oops: 0000 [#1] SMP PTI CPU: 6 UID: 0 PID: 74 Comm: kcompactd0 Not tainted 7.0.0-31-generic #31-Ubuntu Hardware name: ASUS All Series/B85M-E, BIOS 0806 02/20/2014 RIP: 0010:amdgpu_hmm_invalidate_gfx+0x42/0xe0 [amdgpu] Call Trace: __mmu_notifier_invalidate_range_start+0x149/0x1b0 try_to_migrate_one+0xeea/0x1010 rmap_walk_anon+0xdb/0x220 try_to_migrate+0x84/0xe0 migrate_folio_unmap+0x276/0x320 migrate_pages_batch+0x17d/0x940 migrate_pages+0x3b2/0x520 compact_zone+0x513/0x790 kcompactd_do_work+0x109/0x270 note: kcompactd0[74] exited with irqs disabled kcompactd dies holding mm locks. After that, any task touching the affected pages hangs in D state for good: containers can't be stopped or killed, and even a normal reboot oopses again in amdgpu_pci_shutdown -> amdgpu_uvd_prepare_suspend (direct compaction hits the same page). Only a sysrq-b or power cycle recovers the machine. We have hit this 3 times in 2 weeks (2026-09-12, 09-19, 09-25) on a Radeon RX 550 (Polaris 12). The trigger is Jellyfin burning ASS subtitles in with an ffmpeg Vulkan filter chain: subtitles -> hwupload=derive_device=vulkan -> overlay_vulkan The oops fires about 2 seconds after an ffmpeg transcode starts. [Fix] Upstream commit 52f650963d8825e97a0ccdd2b616f8a01d9d3d38 "drm/amdgpu: fix check in amdgpu_hmm_invalidate_gfx" (cherry-picked from 631849ff5d603841e74f19f4a5e30fe1f7d7cf30) Fixes: 91250893cbaa ("drm/amdgpu: fix waiting for all submissions for userptrs") Closes: https://gitlab.freedesktop.org/drm/amd/-/work_items/5399 Cc: stable, queued for 7.1.y and 6.18.y The commit applies cleanly to the resolute 7.0.0-34.34 source (one hunk at offset -4). The regressing commit 91250893cbaa is in the resolute kernel. The fix did not reach 7.0.y stable because that branch is EOL upstream. Note: CVE-2026-68101 was assigned to this fix and later rejected, so the Ubuntu CVE tracker shows resolute as "not affected". It is affected. This is a stability bug, not a security bug, and it is reproducible. [Test Plan] On an amdgpu system, run a workload that creates and destroys userptr BOs repeatedly (for example, ffmpeg Vulkan hwupload in a loop) while forcing compaction with `echo 1 > /proc/sys/vm/compact_memory`. Unpatched kernels oops in amdgpu_hmm_invalidate_gfx; patched kernels don't. [Where problems could occur] The change is limited to amdgpu userptr BOs. The BO now holds a reference to the VM root PD as bo->parent, and amdgpu_bo_destroy() already drops that reference (amdgpu_bo_unref(&bo->parent)). A mistake would show up as a leaked root PD on userptr BO free, or as a wait on the wrong reservation object during invalidation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-34-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-08-30 (26 days ago) InstallationMedia: Ubuntu-Server 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-34-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: resolute 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: adm cdrom dip docker lxd plugdev render sudo users video _MarkForUpload: False acpidump: dmi.bios.date: 02/20/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd02/20/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll:pfaASUSMB: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All 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/2168537/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-ibm-6.8/6.8.0-1066.67~22.04.1)
All autopkgtests for the newly accepted linux-meta-ibm-6.8 (6.8.0-1066.67~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dm-writeboost/2.2.13-1ubuntu4 (amd64) dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-meta-ibm-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2168581] Re: Kernel 7.3.0-5 / -6: ZFS not working properly
This is my proposed fix for the problem. This solves the problem of creating pools after boot and importing existing pools during and after boot. I have attached a debdiff calling it ubuntu4, while the tests were done on the same code called ubuntu3-stesmi2 (and 1 before that). I have tested this one as well. ** Patch added: "Debdiff for my proposal to fix the issue" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2168581/+attachment/6002679/+files/zfs-linux_2.4.4-1ubuntu4.debdiff ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168581 Title: Kernel 7.3.0-5 / -6: ZFS not working properly Status in linux package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: Ubuntu 26.10 Stonking (Development version from 2026-09-20). Kernel: 7.3.0-5 and 7.3.0-6 (from -proposed) On a system with a ZFS root, after installation, I am unable to create or use any additional zfs pools. Details: Encrypted ZFS or not doesn't matter Kernel 7.3.0-5 (OpenZFS 2.4.4-1ubuntu2) and 7.3.0-6 (OpenZFS 2.4.4-1ubuntu3): FAILS. Kernel 7.2.0-5 with OpenZFS 2.4.2: WORKS. Kernel 7.2.0-5 with OpenZFS 2.4.4 (OpenZFS 2.4.4-1ubuntu3): WORKS. No -proposed, only kernel from -proposed, or all from -proposed as of submission time tested and gave same results. Quick reproduction way: 1) Install Ubuntu 26.10 Stonking development with ZFS root. Encrypted or not does not matter. 2) Boot system. It works as it should. 3) Run the following command: sudo -i bash -c 'uname -r; zfs version; truncate -s 1G /root/t.img && zpool create tp /root/t.img; echo "rc=${?}"; zpool list -H tp; zpool destroy tp 2>/dev/null; rm -f /root/t.img' What it does: - Prints out the kernel and zfs information. - Creates a 1G file in /root: /root/t.img. - Creates a zpool called "tp" on /root/t.img. - Prints the rc. Working should be 0. Not working is 1. - Displays the zpool. - Destroys the pool. - Removes the file from /root. Expected result: rc=0 and a created zpool. Received result: rc=1 and no zpool. If you create the partitions manually and make a manual installation including a home directory pool (hpool), the hpool cannot be imported, as the userspace receives ENOENT. There is a patch to fix this (debian/patches/linux-7.3-kthread-nullfs.patch), but it is insufficient, as it stores the initial root directory, which is then the initramfs and not the running root. I have written a patch that I will submit after I create the bug report that fixes it in all scenarios I have thought of. The log supplied shows the commands executed and the outcome. With my patch it gives rc=0 and works. // Stefan ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: zfsutils-linux 2.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 7.3.0-5.5-generic 7.3.0-rc3 Uname: Linux 7.3.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 21:14:20 2026 InstallationDate: Installed on 2026-09-25 (0 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Daily amd64 (20260920) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168581/+subscriptions
четверг
[Bug 2154307] Re: framebuffer-nvidia initramfs hook skips compressed (.ko.zst) DKMS modules
Updated description to reflect cause identified in comment #7 (the framebuffer-nvidia initramfs hook matches only "*.ko"), DKMS compression mechanism from comment #11, and a correction: initramfs-tools does handle compressed modules correctly; the initramfs-tools task is likely invalid. Original description is retained below the new. New information: the identical hook is also shipped by nvidia-kernel-common-580 (580.178.04-0ubuntu0.24.04.1), so the 580 branch is affected as well. The original report was on nvidia-dkms-580. ** Description changed: + DKMS-built NVIDIA modules installed as .ko.zst are not included in the + initramfs, so the driver is unavailable at early boot (e.g., wrong- + resolution splash; early Vulkan apps may fall back to llvmpipe -- Zed + does). Driver still loads later from the root filesystem. + + CAUSE: the framebuffer-nvidia initramfs hook (nvidia-kernel- + common-<branch>) only matches "*.ko" (comment #7). initramfs-tools + itself handles .ko.zst correctly. DKMS compresses its output when the + kernel's modules.dep already lists .zst modules (comment #11). + + AFFECTED: nvidia-kernel-common-580 and -595 (identical hook). + + SUGGESTED FIX (/usr/share/initramfs-tools/hooks/framebuffer-nvidia): + - for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko" -print); do + - manual_add_modules $(basename ${kmod} .ko) + + for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko*" -print); do + + kmod="${kmod##*/}" + + manual_add_modules "${kmod%%.ko*}" + + WORKAROUND: unzstd the .ko.zst files in /usr/lib/modules/<kernel>/updates/dkms/ and + /var/lib/dkms/nvidia/<ver>/<kernel>/x86_64/module/, then depmod and update-initramfs. + + --- Original description (2026-05-27) --- + DKMS-built kernel modules are installed as .ko.zst (zstd-compressed) rather than uncompressed .ko files. The initramfs-tools module inclusion code does not handle .ko.zst files — it finds and includes only uncompressed .ko files. As a result, DKMS-managed modules are absent from the initramfs, and drivers depending on them fail to load at early boot. The current workaround are manual steps to run unzstd --rm on the modules, depmod -a, and update-initramfs to include them. Affected kernels (confirmed on this system): - 6.8.0-50-generic: broken (first occurrence) - 6.11.0-24-generic: broken - 6.11.0-25-generic: broken - 6.11.0-26-generic: working (uncompressed .ko files present after upgrade) - 6.11.0-28-generic: broken (regression) - All subsequent kernels through 6.17.0-29-generic: broken + 6.8.0-50-generic: broken (first occurrence) + 6.11.0-24-generic: broken + 6.11.0-25-generic: broken + 6.11.0-26-generic: working (uncompressed .ko files present after upgrade) + 6.11.0-28-generic: broken (regression) + All subsequent kernels through 6.17.0-29-generic: broken Cause: July 2023, a patch series by Dimitri John Ledkov was applied to Ubuntu's kernel packaging to enable zstd-compressed modules: https://lists.ubuntu.com/archives/kernel-team/2023-July/141412.html The patch series description makes clear the intent was for DKMS-built modules to remain uncompressed. It explicitly states: "the makefile is patched to not attempt installing random modules compressed — this is to ensure that any dkms / lrm / modules builds." However, in practice, DKMS reads CONFIG_MODULE_COMPRESS_ZSTD from the kernel configuration and compresses its output accordingly, regardless of that intent. The result is that DKMS modules are installed as .ko.zst rather than as .ko. Investigation shows initramfs-tools does have .zst handling, but only in the add_firmware() function (searching /lib/firmware/ paths). There is no corresponding .zst handling in the module inclusion code path. Confirmed by: $ grep -A 10 -B 10 "zst" /usr/share/initramfs-tools/hook- functions This leaves a conflict between the actions of the components: - Ubuntu kernel packaging compresses modules and intends to exclude DKMS — but does not fully achieve that exclusion - DKMS follows CONFIG_MODULE_COMPRESS_ZSTD from the kernel config and compresses its output - initramfs-tools has no .zst handling in its module inclusion path, only in its firmware path Environment: - Distribution: Linux Mint 22.3 (Ubuntu Noble/24.04 base) - Kernel: Affects 6.8.0-50-generic and all subsequent kernels tested through 6.17.0-29-generic, with one exception noted above - GPU: NVIDIA GeForce GTX 1660 Super - NVIDIA driver: 580.159.03 (nvidia-dkms-580) + Distribution: Linux Mint 22.3 (Ubuntu Noble/24.04 base) + Kernel: Affects 6.8.0-50-generic and all subsequent kernels tested through 6.17.0-29-generic, with one exception noted above + GPU: NVIDIA GeForce GTX 1660 Super + NVIDIA driver: 580.159.03 (nvidia-dkms-580) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154307 Title: framebuffer-nvidia initramfs hook skips compressed (.ko.zst) DKMS modules Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-595 package in Ubuntu: Confirmed Bug description: DKMS-built NVIDIA modules installed as .ko.zst are not included in the initramfs, so the driver is unavailable at early boot (e.g., wrong- resolution splash; early Vulkan apps may fall back to llvmpipe -- Zed does). Driver still loads later from the root filesystem. CAUSE: the framebuffer-nvidia initramfs hook (nvidia-kernel- common-<branch>) only matches "*.ko" (comment #7). initramfs-tools itself handles .ko.zst correctly. DKMS compresses its output when the kernel's modules.dep already lists .zst modules (comment #11). AFFECTED: nvidia-kernel-common-580 and -595 (identical hook). SUGGESTED FIX (/usr/share/initramfs-tools/hooks/framebuffer-nvidia): - for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko" -print); do - manual_add_modules $(basename ${kmod} .ko) + for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko*" -print); do + kmod="${kmod##*/}" + manual_add_modules "${kmod%%.ko*}" WORKAROUND: unzstd the .ko.zst files in /usr/lib/modules/<kernel>/updates/dkms/ and /var/lib/dkms/nvidia/<ver>/<kernel>/x86_64/module/, then depmod and update-initramfs. --- Original description (2026-05-27) --- DKMS-built kernel modules are installed as .ko.zst (zstd-compressed) rather than uncompressed .ko files. The initramfs-tools module inclusion code does not handle .ko.zst files — it finds and includes only uncompressed .ko files. As a result, DKMS-managed modules are absent from the initramfs, and drivers depending on them fail to load at early boot. The current workaround are manual steps to run unzstd --rm on the modules, depmod -a, and update-initramfs to include them. Affected kernels (confirmed on this system): 6.8.0-50-generic: broken (first occurrence) 6.11.0-24-generic: broken 6.11.0-25-generic: broken 6.11.0-26-generic: working (uncompressed .ko files present after upgrade) 6.11.0-28-generic: broken (regression) All subsequent kernels through 6.17.0-29-generic: broken Cause: July 2023, a patch series by Dimitri John Ledkov was applied to Ubuntu's kernel packaging to enable zstd-compressed modules: https://lists.ubuntu.com/archives/kernel-team/2023-July/141412.html The patch series description makes clear the intent was for DKMS-built modules to remain uncompressed. It explicitly states: "the makefile is patched to not attempt installing random modules compressed — this is to ensure that any dkms / lrm / modules builds." However, in practice, DKMS reads CONFIG_MODULE_COMPRESS_ZSTD from the kernel configuration and compresses its output accordingly, regardless of that intent. The result is that DKMS modules are installed as .ko.zst rather than as .ko. Investigation shows initramfs-tools does have .zst handling, but only in the add_firmware() function (searching /lib/firmware/ paths). There is no corresponding .zst handling in the module inclusion code path. Confirmed by: $ grep -A 10 -B 10 "zst" /usr/share/initramfs- tools/hook-functions This leaves a conflict between the actions of the components: - Ubuntu kernel packaging compresses modules and intends to exclude DKMS — but does not fully achieve that exclusion - DKMS follows CONFIG_MODULE_COMPRESS_ZSTD from the kernel config and compresses its output - initramfs-tools has no .zst handling in its module inclusion path, only in its firmware path Environment: Distribution: Linux Mint 22.3 (Ubuntu Noble/24.04 base) Kernel: Affects 6.8.0-50-generic and all subsequent kernels tested through 6.17.0-29-generic, with one exception noted above GPU: NVIDIA GeForce GTX 1660 Super NVIDIA driver: 580.159.03 (nvidia-dkms-580) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2154307/+subscriptions
[Bug 2154307] Re: framebuffer-nvidia initramfs hook skips compressed (.ko.zst) DKMS modules
** Summary changed: - DKMS modules installed as .ko.zst; are not included in initramfs + framebuffer-nvidia initramfs hook skips compressed (.ko.zst) DKMS modules -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154307 Title: framebuffer-nvidia initramfs hook skips compressed (.ko.zst) DKMS modules Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-595 package in Ubuntu: Confirmed Bug description: DKMS-built NVIDIA modules installed as .ko.zst are not included in the initramfs, so the driver is unavailable at early boot (e.g., wrong- resolution splash; early Vulkan apps may fall back to llvmpipe -- Zed does). Driver still loads later from the root filesystem. CAUSE: the framebuffer-nvidia initramfs hook (nvidia-kernel- common-<branch>) only matches "*.ko" (comment #7). initramfs-tools itself handles .ko.zst correctly. DKMS compresses its output when the kernel's modules.dep already lists .zst modules (comment #11). AFFECTED: nvidia-kernel-common-580 and -595 (identical hook). SUGGESTED FIX (/usr/share/initramfs-tools/hooks/framebuffer-nvidia): - for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko" -print); do - manual_add_modules $(basename ${kmod} .ko) + for kmod in $(find "${MODULESDIR}/${dir}" ${exclude:-} -name "$pattern*.ko*" -print); do + kmod="${kmod##*/}" + manual_add_modules "${kmod%%.ko*}" WORKAROUND: unzstd the .ko.zst files in /usr/lib/modules/<kernel>/updates/dkms/ and /var/lib/dkms/nvidia/<ver>/<kernel>/x86_64/module/, then depmod and update-initramfs. --- Original description (2026-05-27) --- DKMS-built kernel modules are installed as .ko.zst (zstd-compressed) rather than uncompressed .ko files. The initramfs-tools module inclusion code does not handle .ko.zst files — it finds and includes only uncompressed .ko files. As a result, DKMS-managed modules are absent from the initramfs, and drivers depending on them fail to load at early boot. The current workaround are manual steps to run unzstd --rm on the modules, depmod -a, and update-initramfs to include them. Affected kernels (confirmed on this system): 6.8.0-50-generic: broken (first occurrence) 6.11.0-24-generic: broken 6.11.0-25-generic: broken 6.11.0-26-generic: working (uncompressed .ko files present after upgrade) 6.11.0-28-generic: broken (regression) All subsequent kernels through 6.17.0-29-generic: broken Cause: July 2023, a patch series by Dimitri John Ledkov was applied to Ubuntu's kernel packaging to enable zstd-compressed modules: https://lists.ubuntu.com/archives/kernel-team/2023-July/141412.html The patch series description makes clear the intent was for DKMS-built modules to remain uncompressed. It explicitly states: "the makefile is patched to not attempt installing random modules compressed — this is to ensure that any dkms / lrm / modules builds." However, in practice, DKMS reads CONFIG_MODULE_COMPRESS_ZSTD from the kernel configuration and compresses its output accordingly, regardless of that intent. The result is that DKMS modules are installed as .ko.zst rather than as .ko. Investigation shows initramfs-tools does have .zst handling, but only in the add_firmware() function (searching /lib/firmware/ paths). There is no corresponding .zst handling in the module inclusion code path. Confirmed by: $ grep -A 10 -B 10 "zst" /usr/share/initramfs- tools/hook-functions This leaves a conflict between the actions of the components: - Ubuntu kernel packaging compresses modules and intends to exclude DKMS — but does not fully achieve that exclusion - DKMS follows CONFIG_MODULE_COMPRESS_ZSTD from the kernel config and compresses its output - initramfs-tools has no .zst handling in its module inclusion path, only in its firmware path Environment: Distribution: Linux Mint 22.3 (Ubuntu Noble/24.04 base) Kernel: Affects 6.8.0-50-generic and all subsequent kernels tested through 6.17.0-29-generic, with one exception noted above GPU: NVIDIA GeForce GTX 1660 Super NVIDIA driver: 580.159.03 (nvidia-dkms-580) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2154307/+subscriptions
[Bug 2168480] Re: Logitech MX Master 3S scrollwheel becomes oversensitive sometimes, registring one flick as several
** 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/2168480 Title: Logitech MX Master 3S scrollwheel becomes oversensitive sometimes, registring one flick as several Status in linux package in Ubuntu: New Bug description: Randomly, sometimes at boot and sometimes later, the scrolwheel of my Logitech MX Master 3s becomes oversensitive, registring 1 short flick as 5 to 7 long flicks. The workaround is running solaar (the problem appears whether solaar is loaded at session start or not), entering the MX Master 3s section, unlocking and enabling the "Scroll Wheel Resolution" switch, and re-disabling it. This is what I get from 1 short flick when the problem occurs: libinput debug-events --show-keycodes -event9 DEVICE_ADDED Logitech USB Receiver seat0 default group1 cap:k -event4 DEVICE_ADDED Logitech USB Receiver Mouse seat0 default group1 cap:p left scroll-nat scroll-button -event7 DEVICE_ADDED Logitech USB Receiver Consumer Control seat0 default group1 cap:kp scroll-nat -event10 DEVICE_ADDED Logitech USB Receiver System Control seat0 default group1 cap:k -event6 DEVICE_ADDED Logitech Wireless Mouse PID:b034 seat0 default group2 cap:kp left scroll-nat scroll-button -event5 DEVICE_ADDED Logitech Wireless Keyboard PID:b378 seat0 default group3 cap:kp scroll-nat -event8 DEVICE_ADDED Logitech USB Receiver seat0 default group1 cap:t size 116x74mm ntouches 1 calib -event3 DEVICE_ADDED GN Audio A/S Jabra Evolve2 30 SE seat0 default group4 cap:k -event2 DEVICE_ADDED Power Button seat0 default group5 cap:k -event1 DEVICE_ADDED Power Button seat0 default group6 cap:k -event0 DEVICE_ADDED Sleep Button seat0 default group7 cap:k -event12 DEVICE_ADDED Eee PC WMI hotkeys seat0 default group8 cap:k -event24 DEVICE_ADDED xremap seat0 default group9 cap:kp scroll-nat -event4 POINTER_SCROLL_WHEEL +0.000s vert 30.00/240.0* horiz 0.00/0.0 (wheel) event4 POINTER_SCROLL_WHEEL 2 +0.082s vert 30.00/240.0* horiz 0.00/0.0 (wheel) event4 POINTER_SCROLL_WHEEL 3 +0.135s vert 45.00/360.0* horiz 0.00/0.0 (wheel) event4 POINTER_SCROLL_WHEEL 4 +0.142s vert 60.00/480.0* horiz 0.00/0.0 (wheel) event4 POINTER_SCROLL_WHEEL 5 +0.150s vert 30.00/240.0* horiz 0.00/0.0 (wheel) event4 POINTER_SCROLL_WHEEL 6 +0.171s vert 30.00/240.0* horiz 0.00/0.0 (wheel) And this is what I get from 1 short flick when it does not occur, or after using the workaround: libinput debug-events --show-keycodes -event9 DEVICE_ADDED Logitech USB Receiver seat0 default group1 cap:k -event4 DEVICE_ADDED Logitech USB Receiver Mouse seat0 default group1 cap:p left scroll-nat scroll-button -event7 DEVICE_ADDED Logitech USB Receiver Consumer Control seat0 default group1 cap:kp scroll-nat -event10 DEVICE_ADDED Logitech USB Receiver System Control seat0 default group1 cap:k -event6 DEVICE_ADDED Logitech Wireless Mouse PID:b034 seat0 default group2 cap:kp left scroll-nat scroll-button -event5 DEVICE_ADDED Logitech Wireless Keyboard PID:b378 seat0 default group3 cap:kp scroll-nat -event8 DEVICE_ADDED Logitech USB Receiver seat0 default group1 cap:t size 116x74mm ntouches 1 calib -event3 DEVICE_ADDED GN Audio A/S Jabra Evolve2 30 SE seat0 default group4 cap:k -event2 DEVICE_ADDED Power Button seat0 default group5 cap:k -event1 DEVICE_ADDED Power Button seat0 default group6 cap:k -event0 DEVICE_ADDED Sleep Button seat0 default group7 cap:k -event12 DEVICE_ADDED Eee PC WMI hotkeys seat0 default group8 cap:k -event24 DEVICE_ADDED xremap seat0 default group9 cap:kp scroll-nat -event4 POINTER_SCROLL_WHEEL +0.000s vert 15.00/120.0* horiz 0.00/0.0 (wheel) ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-5-generic 7.3.0-5.5 ProcVersionSignature: Ubuntu 7.3.0-5.5-generic 7.3.0-rc3 Uname: Linux 7.3.0-5-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: yotam 4942 F.... wireplumber /dev/snd/controlC0: yotam 4942 F.... wireplumber /dev/snd/controlC2: yotam 4942 F.... wireplumber /dev/snd/seq: yotam 4938 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 21:20:49 2026 InstallationDate: Installed on 2022-01-31 (1697 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) MachineType: ASUS System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-5-generic root=UUID=06eb0295-6f5f-4d0e-96e7-4d2e2fe687ac ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to stonking on 2026-08-03 (52 days ago) dmi.bios.date: 11/29/2025 dmi.bios.release: 45.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4505 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690-A 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.:bvr4505:bd11/29/2025:br45.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-A: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/2168480/+subscriptions
[Bug 2168491] Re: perf/x86/amd/uncore: Use Node ID to identify DF and UMC domains
** 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/2168491 Title: perf/x86/amd/uncore: Use Node ID to identify DF and UMC domains Status in linux package in Ubuntu: New Bug description: For DF and UMC PMUs, a single context is shared across all CPUs that are connected to the same Data Fabric (DF) instance. Currently, the Package ID, which also happens to be the Socket ID, is used to identify DF instances. This approach works for configurations having a single IO Die (IOD) but fails in the following cases. Older Zen 1 processors, where each chiplet has its own DF instance. Any configurations with multiple DF instances or multiple IODs in the same package. The correct way to identify DF instances is through the Node ID (not to be confused with NUMA Node ID). This is available in ECX[7:0] of CPUID leaf 0x8000001e and returned via topology_amd_node_id(). Hence, replace usage of topology_logical_package_id() with topology_amd_node_id(). https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=67d27727854def4a7e2b386429941f5c4741ccc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168491/+subscriptions
[Bug 2168369] Re: Kernel 7.0.0-34 still no wake up from suspend
** 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/2168369 Title: Kernel 7.0.0-34 still no wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: The issue with failure to wake up as in previous versions - except 7.0.0.27 which does work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168369/+subscriptions
[Bug 2165407] Re: resolute: llvm-21-dev build-depends breaks cross-builds
** Changed in: linux-nvidia (Ubuntu Resolute) Status: New => Fix Committed ** Changed in: linux-nvidia (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/2165407 Title: resolute: llvm-21-dev build-depends breaks cross-builds Status in linux package in Ubuntu: New Status in linux-nvidia package in Ubuntu: Invalid Status in linux-nvidia-bos package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Fix Committed Status in linux source package in Resolute: New Status in linux-nvidia source package in Resolute: Fix Committed Status in linux-nvidia-bos source package in Resolute: Fix Committed Status in linux-riscv source package in Resolute: Fix Committed Bug description: Commit e66125ce24f6 ("UBUNTU: [Packaging] Add llvm-21-dev to build-depends for perf", LP: #2138328) added llvm-21-dev as an unqualified Build-Depends entry to enable LLVM-accelerated addr2line() in perf. Because llvm-21-dev is not annotated with :native or an architecture restriction, dpkg attempts to satisfy it for the target (cross) architecture during cross-compilation (e.g. arm64 from amd64). Since the llvm-21-dev package is not available for all cross targets or cannot co-install alongside the native toolchain, cross-builds fail to resolve build dependencies. The fix (already applied in stonking as commit 2aebbf625fd4) makes three changes to debian.master/control.stub.in: - Replaces "llvm-21-dev" with "llvm-21-tools:native <!stage1>" so the LLVM dependency is satisfied from the build host architecture. - Adds "libllvm21 <!stage1>" as a separate library dependency. - Adds "libstd-rust-dev" with an explicit architecture list. This needs to be cherry-picked to resolute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165407/+subscriptions
среда
[Bug 2168369] Re: Kernel 7.0.0-34 still no wake up from suspend
Dell Inspiron 7390. Fails to wake up after 15 minutes of suspension. Only a hard restart allows me to use the laptop. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168369 Title: Kernel 7.0.0-34 still no wake up from suspend Status in linux package in Ubuntu: Incomplete Bug description: The issue with failure to wake up as in previous versions - except 7.0.0.27 which does work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168369/+subscriptions