[Bug 2167995] [NEW] HMC error triggers cascading PF resets and tears down RDMA connections

Public bug reported: [ Impact ] A single HMC error triggers cascading PF resets and tears down RDMA connections on the device: kernel: ice 0000:17:00.1 irdma1: HMC Error kernel: ice 0000:17:00.1 irdma1: Requesting a reset kernel: DMAR: DRHD: handling fault status reg 2 kernel: DMAR: [DMA Read NO_PASID] Request device [17:00.1] fault addr 0xfddce000 [fault reason 0x06] PTE Read access is not set kernel: bond1: (slave enp23s0f1np1): link status definitely down, disabling slave kernel: bond1: active interface up! kernel: ice 0000:17:00.1: PTP reset successful ice 0000:17:00.1: VSI rebuilt. VSI index 0, type ICE_VSI_PF ice 0000:17:00.1: VSI rebuilt. VSI index 1, type ICE_VSI_CTRL bond1: (slave enp23s0f1np1): link status definitely up, 25000 Mbps full duplex This causes a short network outage on intel ice NIC, but not i40e which already has a fix. upstream commit: https://github.com/torvalds/linux/commit/4dc9c884c0aafac1e8d37536d88d485135e26883 applys the same fix to ice. [ Test Plan ] Make sure machine with intel ice works fine by running basic network traffic test and then reproduce the issue in a lab environment. Confirm the issue can not be reproduced with the above commit. [ Where problems could occur ] The same fix has been applied to intel i40e, the commit does the same thing. If something goes wrong in the path, and PF is not reset, it may hit the same network outage when using intel ice ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: High Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Resolute) Importance: High Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Resolute) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => High -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167995 Title: HMC error triggers cascading PF resets and tears down RDMA connections Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Resolute: In Progress Bug description: [ Impact ] A single HMC error triggers cascading PF resets and tears down RDMA connections on the device: kernel: ice 0000:17:00.1 irdma1: HMC Error kernel: ice 0000:17:00.1 irdma1: Requesting a reset kernel: DMAR: DRHD: handling fault status reg 2 kernel: DMAR: [DMA Read NO_PASID] Request device [17:00.1] fault addr 0xfddce000 [fault reason 0x06] PTE Read access is not set kernel: bond1: (slave enp23s0f1np1): link status definitely down, disabling slave kernel: bond1: active interface up! kernel: ice 0000:17:00.1: PTP reset successful ice 0000:17:00.1: VSI rebuilt. VSI index 0, type ICE_VSI_PF ice 0000:17:00.1: VSI rebuilt. VSI index 1, type ICE_VSI_CTRL bond1: (slave enp23s0f1np1): link status definitely up, 25000 Mbps full duplex This causes a short network outage on intel ice NIC, but not i40e which already has a fix. upstream commit: https://github.com/torvalds/linux/commit/4dc9c884c0aafac1e8d37536d88d485135e26883 applys the same fix to ice. [ Test Plan ] Make sure machine with intel ice works fine by running basic network traffic test and then reproduce the issue in a lab environment. Confirm the issue can not be reproduced with the above commit. [ Where problems could occur ] The same fix has been applied to intel i40e, the commit does the same thing. If something goes wrong in the path, and PF is not reset, it may hit the same network outage when using intel ice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167995/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-bos/7.0.0-2019.19)

All autopkgtests for the newly accepted linux-meta-nvidia-bos (7.0.0-2019.19) for resolute have finished running. The following regressions have been reported in tests triggered by the package: dpdk-kmods/0~20241120+git-1 (amd64) fwts/unknown (amd64) zfs-linux/unknown (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/resolute/update_excuses.html#linux-meta-nvidia-bos [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 2163723] Re: btintel_pcie NULL pointer call trace during boot on Intel Bluetooth PCIe controllers

Included in stoking 9c36951474d8e Bluetooth: btintel_pcie: Refactor FLR to use device_reprobe() 86f8661893613 Bluetooth: btintel_pcie: split coredump worker into per-trigger works e0650618ee839 Bluetooth: btintel_pcie: serialize reset_type with RECOVERY_IN_PROGRESS ** Changed in: linux (Ubuntu Stonking) Status: In Progress => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163723 Title: btintel_pcie NULL pointer call trace during boot on Intel Bluetooth PCIe controllers Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-7.0 package in Ubuntu: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-7.0 source package in Resolute: Fix Committed Status in linux source package in Stonking: Fix Released Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [Impact] Bluetooth call trace shows up during boot on Dell systems with Intel PCIe Bluetooth controllers (CID: F14-DVT2-C1X). It can hang the system's shutdown/boot flow. Hit rate is about 1 in 500 boots. Error log: kernel: BUG: kernel NULL pointer dereference, address: 0000000000000db0 kernel: RIP: 0010:btintel_pcie_dump_debug_registers+0x20/0x8f0 [btintel_pcie] kernel: Call Trace: kernel: ? bt_err+0x7a/0xa7 [bluetooth] kernel: btintel_pcie_irq_msix_handler+0x1a2/0x230 [btintel_pcie] kernel: irq_thread_fn+0x26/0x70 kernel: irq_thread+0xbc/0x1c0 kernel: kthread+0xf7/0x130 kernel: ret_from_fork+0x195/0x2a0 kernel: ret_from_fork_asm+0x1a/0x30 The crash hits in the MSI-X interrupt thread while dumping debug registers, and the reset/coredump path around it has several races that can corrupt driver state or drop RX events during a coredump. [Fix] Eight btintel_pcie driver fixes, in dependency order. Merged in v7.2: e43b33bf8d671 Bluetooth: btintel_pcie: Load IOSF debug regs by controller variant 2d00975c841fa Bluetooth: btintel_pcie: Support Product level reset 975a70ff0aec8 Bluetooth: btintel_pcie: Add support for smart trigger dump 4d62d88e7ae6d Bluetooth: btintel_pcie: Add 50 ms delay before MAC init on BlazarIW f70f7f2512c6b Bluetooth: btintel_pcie: Separate coredump work from RX work These add product-level reset support, smart trigger coredumps, and a timing fix for BlazarIW fast-restart, and move coredump processing off the RX workqueue so RX events don't get dropped while a coredump runs. They land ahead of the reset-path rework below. Not yet in a released kernel, merged in the bluetooth-next tree (not yet released upstream): 603b91aeb20a2 Bluetooth: btintel_pcie: Refactor FLR to use device_reprobe() ca75417ab1793 Bluetooth: btintel_pcie: split coredump worker into per-trigger works bd8bee79e1fa8 Bluetooth: btintel_pcie: serialize reset_type with RECOVERY_IN_PROGRESS These rework the reset/coredump internals: FLR now shares the same teardown/re-init path as PLDR through device_reprobe() instead of an open-coded, easy-to-desync copy; the combined coredump worker is split into three single-purpose workers (coredump, hw-exception, fw-trigger) each owning one guard bit, closing a race where a duplicate IRQ could requeue while the previous coredump was still finishing; and reset_type is now written only after the RECOVERY_IN_PROGRESS bit is won, closing a window where two concurrent hardware-error events could pick different reset types for the same recovery attempt. These 3 follow-up patches were requested directly by the ODM (Hugh Chao) after testing showed the debug-register fix alone was not enough; they close races that the ODM's stress test could still trigger. [Test Plan] Reproduce on the affected Dell platform with the Intel PCIe Bluetooth controller: Run WB (wireless/Bluetooth) stress test across repeated boot cycles (the ODM's test hit the bug at roughly 1/500 boots). Without patches: btintel_pcie_dump_debug_registers NULL pointer dereference call trace shows up in dmesg during boot, can block shutdown. With patches: no call trace, no NULL pointer dereference across repeated boot/stress cycles. ODM confirmed the 3 bluetooth-next patches fixed the issue on their test kernel. [Where problems could occur] Could break the Bluetooth btintel_pcie driver's reset and coredump paths on Intel PCIe Bluetooth controllers (Blazar and Scorpius Peak families). If the IOSF base address selection by variant is wrong for some SKU, coredump reads would return garbage instead of crashing, making register dumps useless without an obvious symptom. If the FLR-to-device_reprobe() refactor has a bug, a function-level reset could leave the Bluetooth hci device half torn down, causing btintel_pcie_probe() to fail on reprobe and BT to stay non-functional after a reset event, instead of the driver silently working around it as before. If the split coredump workers or the RECOVERY_IN_PROGRESS serialization miss a case, two reset/coredump triggers could still race, corrupting a coredump buffer or leaving a stale reset_type, which would show up as an incomplete or garbled coredump, or the wrong reset variant (FLR vs PLDR) running when a hardware error hits. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2163723/+subscriptions

[Bug 2167950] Re: Resolute update: upstream stable patchset 2026-09-22

** 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/2167950 Title: Resolute update: upstream stable patchset 2026-09-22 Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed 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: upstream stable patchset 2026-09-22 Ported from the following upstream stable releases: v6.18.51, v7.2.5 from git://git.kernel.org/ net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy() fsnotify: inotify: pass mark connector to fsnotify_recalc_mask() drm/xe: Don't hand out the flat CCS storage as usable VRAM drm/amd/display: fix division by zero in get_estimated_bw() usb: image: mdc800: change kmalloc() to kzalloc() ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() clk: qcom: gcc-mdm9607: Increase delay for USB PHY reset media: usbtv: keep device alive while ALSA card exists usb-storage: ene_ub6250: fix race between scan work and probe usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() usb: dwc3: clear forceRM when issuing EndTransfer usb: storage: realtek_cr: fix use-after-free on disconnect usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop usb: typec: qcom-pmic-typec: drain cc_debounce_dwork if port_start() fails usb: typec: qcom-pmic: cancel reset_work on stop usb: typec: tcpm: constrain TCPM_SOURCING_VBUS event handling usb: typec: tipd: Fix Thunderbolt altmode VDOs for cd321x usb: typec: ucsi: displayport: Fix OOB altmode array index usb: gadget: midi2: Fix null-pointer dereference in f_midi2_free_ep_reqs usb: gadget: f_midi2: fix use-after-free in string attribute show path usb: gadget: f_midi: initialize work in f_midi_alloc() USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() usb: gadget: fix null pointer dereference in usb_put_function_instance() staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() xhci: fix lost bounce buffers on TDs spanning several ring segments thermal/drivers/imx: Disable clock on runtime resume failure thermal/drivers/qoriq: Disable clock on resume failure userfaultfd: reset err to be 0 when move_pages_ptes succeeded ublk: clear VM_MAYWRITE on read-only ublk char device mmap soc: qcom: geni-se: Use HW PROG_RAM_DEPTH to validate firmware size spi: bcm63xx-hsspi: disable clocks on resume failure spi: bcm63xx: disable clock on resume failure spi: bcmbca-hsspi: disable clocks on resume failure spi: Fix DMA mapping ownership on partial map failure scsi: target: iscsi: Reserve a terminator byte for the login payload scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame scsi: pm8001: Use rollback index when freeing MSI-X vectors mm/damon/vaddr-kunit: check region count in three_regions test samples/damon/mtier: handle damon_start() failure samples/damon/mtier: handle damon_stop() failure samples/damon/prcl: handle damon_start() failure samples/damon/prcl: stop and free damon ctx when damon_call() fails samples/damon/wsse: handle damon_start() failure samples/damon/wsse: stop and free damon ctx when damon_call() fails mm/damon/sysfs-schemes: kobject_del() scheme action destination dirs mm/damon/sysfs-schemes: kobject_del() scheme dirs mm/damon/sysfs-schemes: kobject_del() scheme filter dirs mm/damon/sysfs-schemes: kobject_del() scheme quota goal dirs mm/damon/sysfs-schemes: kobject_del() scheme region dirs mm/damon/sysfs: kobject_del() region and target (error) dirs mm/damon/sysfs: kobject_del() target (normal), context and kdamond dirs mm/damon/core-kunit: check region count before testing in split_at() futex: Prevent rcuwait use-after-free during requeue PI ftrace: Synchronize the initialization of ftrace_ops HID: bpf: serialize device reference release in struct_ops destroy path HID: rmi: fix OOB access with undersized RMI reports HID: wacom: validate report length in wacom_intuos_pro2_bt_irq dm: fix race when loading and unloading a table dm: fix resume-vs-remove race dma-direct: return struct page from dma_direct_alloc_from_pool() dmaengine: fsl-edma: tracing: no ptr dereference during log output dmaengine: dw-edma: Fix HDMA channel status register access dmaengine: dw-edma: Complete descriptors before pausing dmaengine: dw-edma: Initialize IRQ data before requesting IRQs cpuidle: dt_idle_genpd: kfree() the original name allocation cpuidle: psci: Fix support for probe deferral by dropping the faux device block: flag zoned disks with GENHD_FL_NO_PART bpf: Fix infinite loop in pcpu_freelist push with one possible CPU ceph: lock mutex in ceph_mds_check_access() ata: ahci: work around lost interrupts on Marvell 88SE61xx ima: Check for ERR_PTR from dentry_path() in validate_hash_algo() irqchip/stm32mp-exti: Fix the unit of the hwspinlock timeout kprobes: Protect kprobe_blacklist with RCU mm/mempolicy: fix sleeping allocation in alloc_pages_bulk_weighted_interleave() fs/ntfs3: fix slab-out-of-bounds write in ni_create_attr_list() Input: aiptek - validate raw macro indices before updating state memcg: bypass the reclaim and oom killer for dying tasks once oom_reaper is done memcg: make the v1 soft limit knob inert rtc: rzn1: Handle EPROBE_DEFER for optional pps interrupt rtc: rzn1: Fix weekday underflow when alarm crosses month boundary rtc: rzn1: Handle unset alarm weekday in rzn1_rtc_read_alarm rtc: rzn1: Disable alarm interrupt before reprogramming alarm registers perf/x86/intel: Fix kernel address leakages in LBR stack perf trace: Factor out BPF loop body perf trace: Refactor augmented_raw_syscalls using bpf_for perf hisi-ptt: Fix PTT trace TLP header parsing i2c: designware: Enable interrupt mask workaround for HJMC3001 i2c: qcom-geni: update frequency table to fix timing parameters i2c: core: fix debugfs UAF on adapter removal i2c: mux: Fix channel node leak on adapter add failure arm64: mm: Fix the lockless page-table walk in show_pte() arm64: errata: pass REVIDR when matching target implementation CPUs ALSA: rawmidi: Return the error from snd_rawmidi_input_params() ALSA: harmony: initialize locks before requesting IRQ ALSA: pcm: Fix race between non-atomic ops and trigger-start nvme-fabrics: fix DHCHAP secret leak on parse failure nvme-fc: fix double free of fabrics options when nvme_add_ctrl() fails nvme-tcp: check the data direction of a C2HData PDU nvme: add missing SRCU grace period in error path nvmet-auth: Synchronize timeout work during SQ teardown nvmet-tcp: fix out-of-bounds write when receiving an over-long PDU nvmet-tcp: reject unsolicited H2CData PDUs pmdomain: airoha: fix unselectable AIROHA_CPU_PM_DOMAIN kconfig Revert "irqchip/mbigen: Fix mbigen node address layout" mm/hugetlb: fix missing migratable flag on same-node hugetlb migration mm/hugetlb: keep max_huge_pages when dissolving surplus folios mm/hugetlb_cgroup: call page_counter_set_max() outside VM_BUG_ON() nvdimm/btt: reject an arena whose nfree is below the lane count parisc: eisa: Fix infinite loop when parsing invalid IRQ value parisc: Fix alignment of asm statements in head.S powerpc/kexec_file: Fix null-ptr-def in extra size calculation powerpc/kexec_file: Prevent kexec range truncation powerpc/mm: fix wrong addr_pfn tracking in compound vmemmap population powerpc/pseries: Handle and log pseries-wdt registration failures powerpc/pseries: Move H_WATCHDOG definitions to a common header powerpc/crash: stop watchdogs before booting kdump kernel s390/vfio-ap: fix stale pqap_hook pointer on error in vfio_ap_mdev_set_kvm() s390/vfio-ap: Fix stale do_remove flag across iterations in vfio_ap_mdev_cfg_remove s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove s390/vfio-ap: Fix dereference matrix_mdev->kvm without checking for NULL s390/vfio-ap: Fix hot-unplug skipped when last AP adapter or domain removed s390/vfio-ap: Fix missing lock required to access list of ap_matrix_mdev objects s390/vfio-ap: Fix NULL deref in status_show() during queue probe s390/vfio-ap: fix potential use of uninitialized apm_filtered bitmap s390/vfio-ap: Fix required lock not held during update of ap_matrix_mdev object mtd: afs: validate v2 image info bounds mtd: mtdoops: free page bitmap when the backing MTD is removed mtd: nand: realtek-ecc: add missing MODULE_DEVICE_TABLE() mtd: rawnand: validate ONFI extended parameter page sections batman-adv: fix stale receive device on merged fragments batman-adv: mcast: ensure unshared skb for multicast packets batman-adv: mcast: linearize skbuff for packet generation batman-adv: dat: avoid unaligned fault in IP extraction batman-adv: bla: fix freeing of claims on meshif deletion batman-adv: bla: prevent CRC corruptions after claim flush clk: clocking-wizard: fix integer overflow in rate calculation clk: mediatek: mt8196: Select REGMAP_MMIO for vlpckgen clk: meson: align gxbb_32k_clk_sel number of parents with actual count clk: qcom: gcc-msm8916: Fix enable_reg for gcc_blsp1_sleep_clk clk: qcom: gcc-msm8939: Fix enable_reg for gcc_blsp1_sleep_clk clk: rockchip: rk3588: Don't change PLL rates when setting dclk_vop2_src clk: qcom: gcc-mdm9607: Drop incorrect apss_tcu_clk_src clk: qcom: gcc-mdm9607: Drop incorrect system_noc_bfdcd_clk_src clk: qcom: gcc-mdm9607: Fix enable_reg for gcc_blsp1_sleep_clk clk: qcom: gcc-mdm9607: Fix halt_reg for gcc_apss_axi_clk clk: qcom: gcc-mdm9607: Drop incorrect BIMC PLL and related clocks i2c: mux: demux-pinctrl: fix OF node leak on kstrdup failure ASoC: cs35l33: drain threaded IRQ before runtime suspend ASoC: cs35l34: drain threaded IRQ before runtime suspend ASoC: fsl: mpc5200-i2s: Free DMA resources on probe failure ASoC: fsl_easrc: Use div64_u64 for 64-by-64 division ASoC: hdac_hda: Fix hlink refcount leak on component registration failure AsoC: intel: sst: fix PCI device reference leak on probe failure ASoC: loongson: Fix error handling in ACPI property parsing ASoC: samsung: aries_audio_probe: double of_node_put due to direct assignment without of_node_get iio: adc: adi-axi-adc: add data size support for AD408X backend iio: adc: max34408: add missing 'select REGMAP_I2C' to Kconfig iio: adc: pac1921: fix wrong channel used in trigger handler read iio: buffer: Fix potential use-after-free in anonymous buffer release iio: buffer: Make IIO DMA fence release RCU-safe iio: buffer: Tie IIO dma fence lock lifetime to the fence iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF iio: chemical: sgp30: Handle IAQ thread creation failure iio: dac: ad3552r-hs: fix scnprintf() buffer bound in data source show iio: dac: m62332: Fix regulator reference count imbalance iio: gyro: mpu3050: fix sign of raw angular velocity readings iio: light: cm32181: return zero after writing calibscale iio: light: gp2ap002: Disable regulators on resume failure iio: light: ltrf216a: fix runtime PM reference leak in error path iio: pressure: dps310: fix NULL pointer dereference on ACPI probe iio: pressure: mpl115: Fix runtime PM cleanup iio: srf04: fix pm_runtime handling on probe error path iio: temperature: hid-sensor-temperature: switch to non-devm iio_device_register() iio: ti-ads7138: Disable STATS_EN bit while reading conversion results iio: light: opt4060: Reject integration times with a non-zero seconds part iio: light: opt4060: Fix incorrect register name in threshold read error message iio: light: opt4001: Fix power down clearing bits of the wrong register iio: light: opt4001: Fix incompatible pointer type passed to div_u64_rem() iio: light: opt4001: Reject integration times with a non-zero seconds part iio: light: opt4001: Fix reversed GENMASK() arguments in fault count mask KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode KVM: nVMX: Always flush vpid02 on first use KVM: nVMX: Decouple INVVPID operand checks from flushing of vpid02 KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit KVM: nVMX: Service local TLB flushes on failed nested VM-Enter KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU KVM: x86/mmu: Fold kvm_mmu_zap_memslot() into kvm_arch_flush_shadow_memslot() KVM: x86/mmu: Split kvm_mmu_zap_all_fast() into "front" and "back" halves KVM: x86/mmu: Use CMPXCHG when clearing Accessed bit in TDP MMU KVM: x86/mmu: Use split "zap all fast" helpers when invalidating memslot KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock KVM: x86: Serialize writes to disabled_quirks using kvm->lock KVM: x86: Ensure runtime reads of disabled_quirks are resolved once KVM: s390: Fix length check __import_wp_info() KVM: s390: Fix memory leak in guest debug handling KVM: s390: Fix old_data leak in guest debug error path KVM: s390: Free guest debug data on vcpu destroy KVM: s390: Take srcu when importing watchpoint data KVM: s390: Zero initialize irq in reinject_machine_check KVM: s390: Fix memory corruption by not reinjecting CK machine checks KVM: s390: pv: Fix rc/rrc offset for PVM_DUMP KVM: s390: Restore sigset on error path KVM: arm64: Consider SCTLR_EL2.M when mapping the L1 VNCR page KVM: arm64: Handle negative S1 walk levels in VNCR TLB size evaluation KVM: arm64: Correctly handle end of VA space TLBI invalidation KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry KVM: arm64: Sign-extend VA for range-based TLBI invalidation KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables KVM: arm64: vgic: Fix detection of MI on no pending LR KVM: arm64: vgic: Reset in_kernel on private IRQ allocation failure KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save KVM: arm64: Correctly cap TLBI Range to the architural limit LoongArch: KVM: Fix PC double advance in kernel MMIO read fast path LoongArch: KVM: Fix TOCTOU race on pv_features LoongArch: KVM: Free init resources if kvm_init() fails LoongArch: KVM: Preserve memslot arch flags on KVM_MR_FLAGS_ONLY LoongArch: Add DIRECT_MAP_PHYSMEM_END definition LoongArch: BPF: Optimize redundant TCC loads in epilogue LoongArch: BPF: Refactor jump offset calculation in tail call LoongArch: Fix acpi_package_ids[] array overflow LoongArch: Do not select HAVE_RUST when KASAN is enabled LoongArch: Do not save/restore percpu base register in rethook trampoline LoongArch: Avoid preempt count underflow without probe rust: drm: ioctl: fix unbounded lifetimes in ioctl handler arguments media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref media: amphion: Remove obsolete frame_count check in venc_start_session media: cec: disable delayed work before freeing an interrupted transmit media: cec: extron-da-hd-4k-plus: add sanity check media: cec: meson: ao-cec-g12a: name the CEC core regmap to avoid debugfs clash media: cec: Serialize exclusive follower delivery media: cedrus: fix memory leak in cedrus_init_ctrls() media: cobalt: Avoid freeing ALSA private data twice media: cx231xx: reject geometry changes while the VBI queue is busy media: cx23885: cancel NetUP CI work before teardown media: em28xx: defer audio-only extension registration media: em28xx: fix use-after-free of dev_next->devlist on disconnect media: go7007: defer the ALSA v4l2 put until card release media: i2c: alvium: Fix: Correct name of register in alvium_set_ctrl_auto_exposure media: i2c: imx415: Release runtime PM reference on VBLANK error media: i2c: imx415: Return test pattern write errors media: i2c: ov02a10: fix endpoint parsing use-after-free media: i2c: ov7740: fix use-after-destroy in remove media: imx355: Avoid calling imx355_power_off twice in error path media: intel/ipu6: fix async notifier cleanup leak on parse error media: iris: Enumerate cap->bus_info to differentiate between encoder and decoder media: meson: vdec: fix NULL pointer deref in vdec_try_fmt_common media: platform: mtk-mdp3: Fix SCP device refcounting media: platform: mtk-mdp3: fix NULL deref on failed SCP lookup media: nxp: imx8-isi: Fix stream ID validation bypass in crossbar routing media: nxp: imx8-isi: Correct color map between V4L2 and ISI media: nxp: imx8-isi: Use BIT_ULL() for 64-bit stream masks media: rc: sunxi-cir: Unregister rc device on probe failure media: rkvdec: Propagate platform_get_irq() errors media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure media: rzg2l-cru: Align bytesperline to hardware DMA stride requirement media: s2255: bound JPEG frame size before copying into the buffer media: s2255: check firmware size before reading trailing marker media: saa7164: fix cleanup on resource allocation failure media: tda18250: fix possible integer overflow media: v4l2-async: avoid deleting unlinked ASC entry on link error media: v4l2-ctrls: Allow unknown HDR10 white point and luminance media: v4l2-fwnode: Fix fwnode leak in v4l2_fwnode_parse_link media: venus: fix payload size returned by parse_caps() and parse_alloc_mode() media: venus: fix payload size calculation in parse_raw_formats() media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure media: vimc: fix pixel format lookup in enum_framesizes media: zoran: Avoid freeing a registered video_device twice media: qcom: iris: fix state-change debug log printing stale value media: qcom: iris: use disable_irq() during power-off media: chips-media: wave5: Guard bit depth check with initial_info_obtained media: chips-media: wave5: Set inst->std during default format initialization scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers scsi: qla2xxx: Bound i2c->length in I2C bsg handlers scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check scsi: qla2xxx: Fix Name Server logout detection on FWI2 adapters scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition() scsi: qla2xxx: Initialize NVMe abort_work once at submission scsi: qla2xxx: Check entry_status in qla24xx_modify_vp_config() scsi: qla2xxx: Bound image count in qla2x00_update_fru_versions() scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation scsi: qla2xxx: Serialize flash version read in reset handler scsi: qla2xxx: Fix cs84xx use-after-free on host teardown scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state() scsi: qla2xxx: Fix FCE trace enable parsing in debugfs scsi: qla2xxx: Don't query firmware state while chip is down scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path scsi: qla2xxx: Fix response queue over-consumption in __qla_consume_iocb() scsi: qla2xxx: Quiesce response IRQ before freeing request queue scsi: qla2xxx: Avoid double completion in async IOCB timeout scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry() scsi: qla2xxx: Fix NVMe abort reference leak on repeated abort scsi: qla2xxx: Drop vport reference under lock in report ID acquisition scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition scsi: qla2xxx: Use coherent DMA buffer for D_Port diagnostics scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started f2fs: return symlink writeback errors f2fs: reject overlapping move range after len expansion f2fs: only redirty pinned folios in redirty_blocks f2fs: fix to avoid move_range and defragment on device_alias file f2fs: dirty directory inodes on mtime/ctime update f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set() f2fs: return writeback error from collapse range f2fs: fix to avoid potential section-unaligned pinfile f2fs: fix dentry folio leak in find_in_level f2fs: avoid NULL checkpoint thread access in sysfs f2fs: fix to migrate all curseg types during free_segment_range f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages() f2fs: fix i_size when pinned fallocate partially fails f2fs: fix to off-by-one issue in f2fs_zero_post_eof_page() f2fs: fix to clear dirty flag on folio in error path f2fs: fix valid block count leak on data block allocation failure f2fs: fix to pass folio->index to f2fs_sanity_check_node_footer() f2fs: fix to zero post-EOF data when extending file size drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init() drm/xe/vram: report FLAT_CCS base misalignment drm/panthor: harden firmware build-info bounds checks drm/panthor: fix firmware control interface bounds checks drm/bridge: dw-hdmi: fix i2c adapter leak on probe failure drm/panel-edp: fix i2c adapter leak on probe failure drm: fix race between partial drm_dev_register() failure and ioctl drm/i915: Guard against NULL driver_data in i915_pci_probe() drm/ssd130x: fix column and row end address in partial updates for ssd132x drm/sun4i: fix refcount leak in sun4i_backend_init_sat() drm/ssd130x: fix column and row end address in partial updates in ssd133x drm/nouveau/disp/r535: Add scanline position support + head state support drm/hibmc: Fix list of formats on the primary plane drm/hibmc: Use drm_atomic_helper_check_plane_state() drm/amd/display: avoid divide-by-zero in __is_lut_linear() drm/amd/display: fix dc_lock leak on GPU reset error paths drm/amd/display: validate plane degamma LUT size for private color prop drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check drm/gud: NUL-terminate TV mode names read from the device drm/gud: validate TV mode names before creating enum property drm/msm/dsi: round 6G byte clock rate to the PLL-achievable value drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used drm/amdgpu: check thunderbolt before switcheroo registration drm/amdgpu: clamp the isolation index for rings outside a partition drm/amdgpu: Disable runtime PM for externally attached dGPUs drm/amdgpu: fix autosuspend cleanup during removal drm/amdgpu: Skip accessing psp rum time db for APUs drm/amdgpu: update the fw version for gfx11 userqueues drm/amdgpu: update the fw version for gfx12 userqueues drm/amdgpu: use AMDGPU_GPU_PAGE_SHIFT instead of PAGE_SHIFT drm/amdkfd: Add TLB flush after MES queue eviction/suspension drm/amdkfd: Fix error path at svm_migrate_copy_to_ram drm/amdkfd: Fix the case that vm range is hole at svm_migrate_copy_to_vram drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore drm/amdkfd: Reject zero-sized AQL queue allocations after size halving drm/sysfb: simpledrm: Improve framebuffer-size validation drm/sysfb: simpledrm: Improve panel-size validation drm/sysfb: simpledrm: Improve stride validation drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation drm/sysfb: ofdrm: Fix is_avivo() constant comparison bug drm/nouveau/gsp: use per-version DP_CONFIG_STREAM params on r570 firmware drm/nouveau: unsubscribe the channel-kill event before the fence context drm/nouveau: Use write-combined maps for coherent drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE drm/nouveau/disp: move GSP head-timing ISR and vblank helpers to tu102.c drm/nouveau/disp: move the GSP HDMI GCP AVMute write to engine/disp drm/nouveau/disp: route GSP-RM display MMIO through nvkm_disp_func hooks drm/nouveau/disp: fix HDMI vendor infoframes on GB20x drm/nouveau/disp: fix HDMI GCP AVMute register offsets on GB20x drm/nouveau/disp: fix head state readback on GB20x drm/nouveau/gsp: fix vblank interrupts on GB20x ksmbd: fix use-after-free in oplock break notification fuse: split off fuse_args and related definitions into a separate header fuse: remove fm arg of args->end callback crypto: atmel-ecc - replace min_t with min mm/hugetlb: defer vmemmap population for bootmem hugepages mm/hugetlb: refactor code around vmemmap_walk mm/page_alloc: don't spin_trylock() in NMI on UP USB: gadget: ffs: fix mm lifetime handling usb: gadget: f_fs: Fix Use-After-Free in AIO error path NFSD: Guard admin state-revocation walks with NFSD_NET_UP ceph: properly decrypt filenames in vmalloc() buffers HID: sony: use guard() and scoped_guard() HID: sony: clean up device list on probe failure ACPI: CPPC: Reject desired_perf reads on _CPC revision 4+ ACPI: x86: cmos_rtc: Create a CMOS RTC platform device ACPI: TAD: Rearrange RT data validation checking ACPI: TAD: Add locking around AML evaluations bpf: Factor stackid_init function from __bpf_get_stackid bpf: Factor stackid_fastpath function from __bpf_get_stackid bpf: Factor stackid_new_bucket from __bpf_get_stackid bpf: Use stack id functions instead of __bpf_get_stackid bpf: Disable preemption in bpf_get_stackid rpcrdma: arm rn_done before publishing the notification sched: Add assert_balance_callbacks_empty helper sched: Rework prev_balance() to avoid stale prev references sched/core: Make core-sched flips wait for in-flight selections remoteproc: qcom: pas: Guard dtb metadata release with dtb_pas_id check NFSD: Consolidate the revocation-path client unpin NFSD: Prevent client use-after-free during blocked-lock reaping NFSD: Prevent client use-after-free during close_lru reaping mm: rework compound_head() for power-of-2 sizeof(struct page) hugetlb: remove VMEMMAP_SYNCHRONIZE_RCU Docs/ABI/damon: fix typo in intervals_goal sysfs path power: supply: ab8500_fg: Remove redundant dev_err()/dev_err_probe() power: supply: ab8500_fg: fix use-after-free on remove mm/damon/tests/core-kunit: catch test failure in test_merge_regions_of() mm/damon/vaddr: drop last same folio access check optimization mm/damon/paddr: drop last same folio access check reuse optimization mm/damon/ops-common: use nr_accesses moving sum for quota score mm/damon/core: skip aging from repeated aggressive merging mm/damon/sysfs: read addr_unit only once in damon_sysfs_apply_inputs() mm/damon/core-kunit: handle region split failure in filter_out() mm/damon/core: initialize damos->last_applied mm/hugetlb_vmemmap: fix incorrect vmemmap restore in rollback ksmbd: zero pipe read compound padding zram: move lockmap to be per-zram instead per table zram: fix slot lock bit position on big-endian 64-bit ACPI: battery: Use kstrtoul() over sscanf("%lu\n") ACPI: battery: Protect all properties with a separated mutex KVM: SEV: Forcefully invalidate SNP VMSA if its backing gmem page is zapped NFSD: Annotate caller preconditions for the state-table walkers usb: cdnsp: fix wakeup from S3 after controller context loss usb: dwc3: google: Initialise probe properties with DWC3_DEFAULT_PROPERTIES usb: typec: hd3ss3220: track VBUS enable state per consumer usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers() staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() tracing/probes: Fix anon_stack check for unnamed bitfields in btf_find_struct_member tracing: Have show_event_filters/triggers files take trace array ref tracing: Remove the backup instance automatically after read tracing: Take trace_array reference when opening options file soc: fsl: qe: Add chained_irq_{enter,exit}() calls in cascade handler mm/damon/sysfs: read ops_id only once in damon_sysfs_apply_inputs() mm/damon/core-kunit: skip wrong dest walk in commit_dests_for() mm/damon/core-kunit: skip wrong quota goal walk in commit_quota_goals() mm/damon/core-kunit: skip wrong region walk in commit_target_regions() mm/secretmem: properly account locked pages futex: Provide rt_mutex_.*_schedule() equivalents for futex scheduling ftrace: Take trace_array reference before accessing its ftrace_ops dma-buf: dma-heap: don't publish fd before copy_to_user() succeeds bpf, riscv: Make arena support depend on ZACAS misc: fastrpc: don't publish fd before copy_to_user() succeeds mm/huge_memory: transfer the pmd dirty bit to the folio on zap perf/x86/intel: Remove anythread_deprecated bit from perf_capabilities perf build: Add clang and rust target flags for LoongArch perf/core: Fix deadlock in perf_mmap() failure path perf: Fix use-after-free when perf mmap() revival races with the last munmap() i2c: qcom-cci: Do not check return value of cci_init() i2c: qcom-cci: Remove overcautious disable_irq() calls i2c: qcom-cci: fix autosuspend cleanup arm64: Don't read GMID_EL1 when MTE is disabled ring-buffer: Show persistent buffer dropped events in trace_pipe file ring-buffer: Allow splice reads on static buffers accel/amdxdna: return early from a zero-length flush accel/ethosu: check MMIO mapping errors in probe dma-buf: add dma_fence_was_initialized function v2 accel/ethosu: fix job completion fence cleanup nvme: fold nvme_config_discard() into nvme_update_disk_info() nvme: skip the zoned limits update if the zone info query failed Revert "once: don't use a work queue to reset sleepable static key" mm: fix incorrect vm_flags usage when checking allowable orders for tmpfs mm/migrate_device: avoid out-of-bounds writes for compound folios mm/hugetlb_cma: fix null nodemask dereference in hugetlb_cma_alloc_frozen_folio mtd: rawnand: pl353: Make sure we use the monolithic helpers for raw accesses mtd: rawnand: sunxi: group controller delay tables mtd: rawnand: sunxi: describe tADL and tWHR delays mtd: rawnand: sunxi: fix H6/H616 controller timings batman-adv: fix TX priority extraction for BATADV_FORW_MCAST clk: microchip: mpfs: fix regmap_update_bits() mask/val order ASoC: adau1761: sort the register default table ASoC: cx2072x: sort the register default table ASoC: fsl_easrc: sort the register default table ASoC: max9860: sort the register default table ASoC: ml26124: sort the register default table ASoC: pcm512x: sort the register default table ASoC: pm4125-sdw: sort the register default table ASoC: rt1017-sdca-sdw: sort the register default table ASoC: rt1316-sdw: sort the register default table ASoC: rt1318-sdw: sort the register default table ASoC: rt1318: sort the register default table ASoC: rt274: sort the register default table ASoC: rt286: sort the register default table ASoC: rt298: sort the register default table ASoC: rt700: drop duplicate reg_default entry ASoC: rt700: sort the register default table ASoC: rt711-sdca: sort the register default tables ASoC: rt711: sort the register default table ASoC: rt712-sdca-dmic: sort the register default table ASoC: rt712-sdca-sdw: sort the register default table ASoC: rt715-sdca: drop duplicate reg_default entries ASoC: rt715-sdca: sort the register default tables ASoC: rt715: sort the register default table ASoC: rt721-sdca-sdw: sort the register default table ASoC: sgtl5000: sort the register default table ASoC: sti-sas: sort the register default table ASoC: tas2552: sort the register default table ASoC: tas2764: sort the register default table ASoC: tas2780: sort the register default table ASoC: tas2783-sdw: drop duplicate reg_default entry ASoC: tas2783-sdw: sort the register default table iio: adc: ad4080: configure backend data size iio: adc: max14001: add missing 'select REGMAP' to Kconfig iio: dac: ad5446: fix OF module device table iio: dac: mcp47feb02: add missing 'select REGMAP_I2C' to Kconfig iio: light: apds9306: fix PM reference leak in apds9306_read_data() KVM: x86: Move some EFER bits enablement to common code KVM: x86: Move enabling EFER.SVME and EFER.LMSLE to generic EFER setup KVM: s390: Zero initialize data structures for inject_pfault_token KVM: s390: keyop: use mmu_lock to read gmap->asce KVM: arm64: nv: Fully update VNCR fixmap state in kvm_translate_vncr() KVM: arm64: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping KVM: arm64: Remove VM-wide VNCR mapping counter LoongArch: Expand module virtual address space to 2GB LoongArch: BPF: Move arena register slot below TCC context LoongArch: BPF: Fix off-by-one error for insn_is_cast_user() media: dt-bindings: nxp,imx8-isi: Drop fsl,blk-ctrl requirement for i.MX8ULP media: i2c: vd55g1: Fix manual digital gain on color variant media: i2c: vd55g1: Fix media bus code initialization media: mali-c55: fix dropped last AEC histogram zone weight media: mali-c55: Fix clock leak on reset deassert failure media: mali-c55: Fix AEXP IHIST disable bit shift media: mali-c55: Fix scaler factor overflow for large crop sizes media: rkvdec: hevc: tighten EXT SPS RPS control dimensions media: rkvdec: hevc: guard INTER_REF_PIC_SET_PRED index underflow media: ti: vpe: quiesce overflow recovery before freeing streams media: v4l2-ctrls: validate HEVC EXT SPS RPS counts media: chips-media: wave5: avoid skipping device_run while VPU has work media: chips-media: wave5: Add timeout while stop_streaming media: chips-media: wave5: Defer job_finish() only when a DEC_PIC was queued media: chips-media: wave5: Fix pipeline stall when queuing fails media: chips-media: wave5: Resume device before setting EOS flag scsi: qla2xxx: Fix BSG job leak on validate flash image error path scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak f2fs: validate MOVE_RANGE destination size f2fs: limit recovery filename logging to stored length f2fs: embed f2fs_gc_kthread in f2fs_sb_info f2fs: fix folio_nr_pages() race after put in large folio invalidate f2fs: fix to return -EFSCORRUPTED in f2fs_get_node_info() correctly f2fs: protect critical_task_priority updates with s_umount f2fs: fix to reclaim space in f2fs_allocate_pinning_section() drm/amdgpu: avoid force-completing uninitialized UVD rings drm/i915/display: Clear SEL_FETCH_PLANE_CTL on plane disable drm/amd/display: Fix HPD consideration for VGA/LVDS connectors on DCE drm/amd/display: Set gpuvm min page size to 4K on dcn35/36 drm/ttm: Drop tt->restore after successful restore drm/amdgpu: force complete the KIQ ring fences on reset drm/amdgpu: force complete the MES ring fences on reset drm/amdkfd: fix scope of mqd_mgr dereference in pqm_debugfs_mqds drm/nouveau/dmem: fix callocated underflow on large folio split drm/nouveau/dmem: fix mismatched DMA unmap size for large folios mm/damon/core: avoid infinite kdamond_merge_regions() internal loop PCI: Introduce PCI_SLOT_PLACEHOLDER constant for slot_nr placeholder value PCI: Allow per function PCI slots to fix slot reset on s390 UBUNTU: Upstream stable to v6.18.51, v7.2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167950/+subscriptions

[Bug 2071590] Re: test_vxlan_vnifiltering.sh from ubuntu_kselftests_net failed on linux-oem-6.8 (with ipv6 default rdst)

** 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/2071590 Title: test_vxlan_vnifiltering.sh from ubuntu_kselftests_net failed on linux- oem-6.8 (with ipv6 default rdst) Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Committed Bug description: [Impact] The ubuntu_kselftests_net test test_vxlan_vnifiltering.sh fails on and off. One subtest fails while the other 26 pass: TEST: VM connectivity over vnifiltering vxlan (ipv4 default rdst) [ OK ] TEST: VM connectivity over vnifiltering vxlan (ipv6 default rdst) [ OK ] TEST: VM connectivity over vnifiltering vxlan pervni remote (ipv4 default rdst) [ OK ] TEST: VM connectivity over vnifiltering vxlan pervni remote (ipv6 default rdst) [FAIL] # Tests passed: 26 Tests failed: 1 not ok 1 selftests: net: test_vxlan_vnifiltering.sh # exit=1 Only the subtests that use an IPv6 underlay remote fail. Every IPv4 subtest passes in the same run. The test sends one ping with a 1 second deadline right after it sets up the network. The IPv6 underlay addresses are still doing Duplicate Address Detection at that point, so the address cannot be used as a tunnel source yet. The single packet is dropped and the test gives up. Slow machines lose this race more often. Seen on arm64 64k, lowlatency, lowlatency 64k, nvidia-lowlatency, azure and gcp instances. Also seen on amd64 gcp instances, so this is not arm64 only. This is a test bug. The VXLAN driver is fine. [Fix] Replace the single ping with slowwait, which retries every 100ms for up to 5 seconds. Also drop a pointless fixed "sleep 1". 948670361c0c1 selftests: net: use slowwait to make sure IPv6 setup finished Upstream in v6.17. slowwait() already exists in tools/testing/selftests/net/lib.sh on the target branches, so no other patch is needed first. [Test Plan] Run the test on a slow or loaded machine, arm64 or a small cloud instance: $ cd tools/testing/selftests/net $ sudo ./test_vxlan_vnifiltering.sh Repeat 20 times, the failure does not happen every run: $ for i in $(seq 20); do sudo ./test_vxlan_vnifiltering.sh | tail -3; done Without patch: "VM connectivity over vnifiltering vxlan pervni remote (ipv6 default rdst) [FAIL]" shows up in some runs, Tests failed: 1 With patch: all runs report Tests passed: 27, Tests failed: 0 [Where problems could occur] Could break test_vxlan_vnifiltering.sh itself. Nothing outside the test tree is touched, so no kernel code is at risk. slowwait retries until the command succeeds. If a real VXLAN datapath bug shows up later, this test now waits 5 seconds per ping before reporting it, so a broken run takes longer to finish. In the worst case, a full failure goes from a few seconds to about 50 seconds. If slowwait is missing from lib.sh on a branch, the test would abort with "slowwait: command not found" and every connectivity subtest would fail. Check lib.sh has slowwait() before applying. [Other Info] Test only change, no kernel code changes. Already in noble hwe-6.17 and hwe-7.0. Missing from noble 6.8 (master) which is the only branch still hitting this. ============================================== Test complains about: TAP version 13 1..1 # timeout set to 0 # selftests: net: test_vxlan_vnifiltering.sh # TEST: Create traditional vxlan device [ OK ] # TEST: Cannot create vnifilter device without external flag [ OK ] # TEST: Creating external vxlan device with vnifilter flag [ OK ] # TEST: Cannot set in-use vni id on vnifiltering device [ OK ] # TEST: Set new vni id on vnifiltering device [ OK ] # TEST: Create second external vxlan device with vnifilter flag [ OK ] # TEST: Cannot set in-use vni id on vnifiltering device [ OK ] # TEST: Set new vni id on vnifiltering device [ OK ] # TEST: Update vni id on vnifiltering device [ OK ] # TEST: Add new vni id on vnifiltering device [ OK ] # TEST: Set multicast group on existing vni [ OK ] # TEST: Set multicast group on existing vni [ OK ] # TEST: Cannot set vnifilter flag on a device [ OK ] # TEST: Cannot unset vnifilter flag on a device [ OK ] # TEST: VM connectivity over vnifiltering vxlan (ipv4 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan (ipv6 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan pervni remote (ipv4 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan pervni remote (ipv6 default rdst) [FAIL] # TEST: VM connectivity over vnifiltering vxlan mgroup (ipv4 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan mgroup (ipv6 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan pervni mgroup (ipv4 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan pervni mgroup (ipv6 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan pervni remote mix (ipv4 default rdst) [ OK ] # TEST: VM connectivity over vnifiltering vxlan pervni remote mix (ipv6 default rdst) [ OK ] # TEST: VM connectivity over traditional vxlan (ipv4 default rdst) [ OK ] # TEST: VM connectivity over traditional vxlan (ipv6 default rdst) [ OK ] # TEST: VM connectivity over metadata nonfiltering vxlan (ipv4 default rdst) [ OK ] # # Tests passed: 26 # Tests failed: 1 not ok 1 selftests: net: test_vxlan_vnifiltering.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071590/+subscriptions

[Bug 2167912] Re: No audio output from internal speakers on LG gram 16Z90U-H.AU87U1 (Intel Panther Lake platform), despite the entire audio stack reporting correct, unmuted, full-volume state.

** 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/2167912 Title: No audio output from internal speakers on LG gram 16Z90U-H.AU87U1 (Intel Panther Lake platform), despite the entire audio stack reporting correct, unmuted, full-volume state. Status in linux package in Ubuntu: New Bug description: Summary: No audio output from internal speakers on LG gram 16Z90U-H.AU87U1 (Intel Panther Lake platform), despite the entire audio stack reporting correct, unmuted, full-volume state. Hardware: LG Electronics 16Z90U-H.AU87U1, SoundWire audio via sof-audio-pci-intel-ptl (0000:00:1f.3). Speaker amp is a Realtek RT1320-SDCA (SoundWire link 1, mfg_id 0x025d part_id 0x1320). Mic/headset codec is RT712-SDCA (link 3, part_id 0x0713). SOF firmware version 2.14.1.1 (IPC4). Kernel: 7.0.0-31-generic. linux-firmware 20260319.git217ca6e4. Both are the latest available via apt. fwupdmgr get-updates shows no relevant BIOS/EC firmware update. Symptom: No sound from internal speakers, in any application. pactl/wpctl status show the Speaker sink as RUNNING, unmuted, 100% volume, with an active stream connected to it. ALSA simple-mixer controls (Speaker, Post Mixer Speaker, Pre Mixer Speaker) are all on/100%. Despite this, no audible output. Isolated below PipeWire: Stopped pipewire/pipewire-pulse/wireplumber entirely and ran speaker-test -D hw:0,2 -c2 -twav -l1 directly against the ALSA hardware device — still completely silent. This rules out PipeWire/WirePlumber routing as the cause; the fault is in the kernel/DSP/amp path itself. Relevant kernel log line: sof-audio-pci-intel-ptl 0000:00:1f.3: No SoundWire machine driver found for the ACPI-reported configuration: sof-audio-pci-intel-ptl 0000:00:1f.3: link 1 mfg_id 0x025d part_id 0x1320 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: link 3 mfg_id 0x025d part_id 0x0713 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: Use SoundWire default machine driver with function topologies No model-specific machine driver/quirk exists for this ACPI configuration, so the kernel falls back to a generic function-topology driver, which appears not to fully enable the speaker output on this model. Secondary bug (confirmed separate from the above): SoundWire runtime autosuspend (3s idle timer) repeatedly fails on the amp: rt1320-sdca sdw:0:1:025d:1320:01: rt1320_pde_transition_delay PDE to PS3 is NOT ready Disabling autosuspend via echo on > /sys/bus/soundwire/devices/sdw:0:1:025d:1320:01/power/control (made persistent via udev rule) eliminated this specific error on subsequent boots, but audio output was still absent — so this is a real bug but not the root cause of the silence. Also observed at every boot: alsactl: set_control:1521: Cannot write control 'numid=7,iface=MIXER,name='rt1320-1 R0 Load Mode'' : Invalid argument Already ruled out: mute/volume state, PipeWire/WirePlumber configuration, suspend/resume cycling (issue persists after resume), missing kernel/firmware updates (already latest), missing BIOS firmware update (none available via fwupd). ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ryan 3369 F.... pipewire ryan 3378 F.... wireplumber /dev/snd/seq: ryan 3369 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 21 22:03:04 2026 InstallationDate: Installed on 2026-09-19 (2 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 04f2:b88b Chicony Electronics Co., Ltd LGE Camera Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: LG Electronics 16Z90U-H.AU87U1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=98a4d959-fb3b-4440-921b-66cf03d1c892 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2026 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P1ZK3080 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 16Z90U dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 25.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP1ZK3080X64:bd01/22/2026:br0.1:efr25.0:svnLGElectronics:pn16Z90U-H.AU87U1:pvr0.1:rvnLGElectronics:rn16Z90U:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO:pfagramPro: dmi.product.family: gram Pro dmi.product.name: 16Z90U-H.AU87U1 dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167912/+subscriptions

[Bug 2167904] [NEW] xternal monitor fails EDID detection through Dell WD25Z dock

Public bug reported: # Bug report: External monitor fails EDID detection through Dell WD25Z dock (separate from known UCSI duplicate-altmode bug) ## Summary One external monitor connected via DisplayPort to a Dell Pro Dock WD25Z is never assigned a valid EDID by the kernel, and is limited to a small set of generic fallback resolutions (max 1024x768) instead of its native 1920x1080. A second external monitor connected via DisplayPort to the same dock, and the same monitor/cable/port under Windows 11, work correctly at 1920x1080. This report also documents a related, already- fixed UCSI firmware-duplicate-altmode bug encountered on the same hardware, which is **not** the cause of the EDID issue but was investigated in the same session and may be relevant context. ## System information - **Laptop:** Dell Latitude 7420 (BIOS 1.51.0 and 1.52.0 both tested, no change) - **OS:** Ubuntu 26.04.1 LTS - **Kernels tested:** - `7.0.0-31-generic` (default Ubuntu kernel) - `7.1.13-070113-generic` (mainline build from kernel.ubuntu.com, includes upstream commit `67c92c6419ea6dbc5b1f3e9691aecea956e3e81c`) - **Dock:** Dell Pro Dock WD25Z (USB4/DisplayPort Alt Mode; does not negotiate as a Thunderbolt device — confirmed absent from `boltctl` output and from Windows' Thunderbolt Control Center on both ports) - **Affected monitor:** connected via DisplayPort on the dock - **Working monitor for comparison:** LG Electronics 22" (model reports as "LG FULL HD"), connected via a second DisplayPort output on the same dock ## Steps to reproduce 1. Connect the Dell WD25Z dock to the Latitude 7420 via USB-C. 2. Connect two external monitors to the dock's two DisplayPort outputs (one HDMI + one DP was also tested with the same result on the DP-connected monitor). 3. Boot Ubuntu. ## Expected behaviour Both external monitors are detected with correct EDID (vendor/product/serial) and offer their native 1920x1080 resolution, as happens under Windows 11 on the same hardware. ## Actual behaviour - One monitor (LG) is detected correctly every time. - The other monitor is detected as "Unknown Display" (GNOME/Mutter) with `Vendor: unknown`, `Product: unknown`, `Serial: unknown`, and is limited to a short list of fallback modes (`1024x768@60.004`, `848x480@60.000`, `800x600@60.317`, `800x600@56.250`, `640x480@59.940`) with no 1920x1080 option. - `/sys/class/drm/cardX-DP-Y/edid` for the affected connector reads back **0 bytes**, while the working monitor's EDID reads back correctly at the same time. - The DRM connector number assigned to the affected monitor changes on every boot and every resume from suspend (observed as `DP-5`, `DP-6`, `DP-9`, `DP-10` across different sessions for what is physically the same port), consistent with the dock's internal MST/DP hub re-enumerating non-deterministically. - DisplayPort Alt Mode itself negotiates successfully on the USB-C link for this monitor: `/sys/class/typec/portN/portN-partner/portN-partner.X/active` = `yes` with the DisplayPort mode active. The failure appears to be downstream, in the actual DP-AUX/EDID read over the dock's internal hub for this specific output. ## Separate, already-resolved issue encountered during investigation While investigating, the following kernel WARNING was found on kernel `7.0.0-31-generic` when hot-plugging the dock: ``` ucsi_acpi USBC000:00: con2: Firmware bug: duplicate partner altmode SVID 0x413c (VDO 0x00000001 vs 0x00000002) at offset 2, ignoring. Please update your system firmware. ------------[ cut here ]------------ WARNING: drivers/usb/typec/class.c:311 at typec_altmode_update_active+0x101/0x110 [typec] ... Call Trace: ucsi_altmode_update_active+0x116/0x1b0 [typec_ucsi] ucsi_check_altmodes+0x92/0xd0 [typec_ucsi] ucsi_poll_worker+0x41/0xe0 [typec_ucsi] ``` This matches the upstream fix "usb: typec: ucsi: Detect and skip duplicate altmodes from buggy firmware" (commit `67c92c6419ea6dbc5b1f3e9691aecea956e3e81c`, landed for v7.1.6/v7.2). After building and booting mainline kernel `7.1.13`, this WARNING/call trace no longer occurs. However: - `/sys/class/typec/port1/port1.2/` and `port1.3/` (port side) and `port1-partner.1/` and `.2/` (partner side) still both advertise SVID `413c` with distinct VDOs (`0x00000001` and `0x00000002`) — the duplication is still present in the dock's firmware, it is simply no longer causing a kernel warning/crash, which appears to be intentional given the port itself also advertises the SVID twice (a case the current fix logic treats as tolerable rather than as the "buggy firmware" case it filters). - **This fix did not resolve the EDID/resolution issue**, which persisted identically on kernel 7.1.13. The two issues are independent. I am not certain whether the EDID read failure is best classified as a kernel/DRM driver issue, a udev/enumeration-ordering issue, or purely a dock firmware issue outside the kernel's control — filing here in case it's the former, and in parallel reporting to Dell in case it's a dock firmware issue. ## Workaround currently in use Forcing a synthetic EDID via the `drm.edid_firmware` kernel parameter, mapped to the range of connector names observed across boots, restores 1920x1080 output but does not restore correct monitor identification and is not a real fix for the underlying EDID read failure or the connector renumbering. ## Additional information available on request - Full `dmesg` output from both kernel versions - `xrandr --verbose` output - `gdctl show --modes` output - `/sys/class/typec/` and `/sys/class/drm/` sysfs dumps ## Report generated by Claude AI ** 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/2167904 Title: xternal monitor fails EDID detection through Dell WD25Z dock Status in linux package in Ubuntu: New Bug description: # Bug report: External monitor fails EDID detection through Dell WD25Z dock (separate from known UCSI duplicate-altmode bug) ## Summary One external monitor connected via DisplayPort to a Dell Pro Dock WD25Z is never assigned a valid EDID by the kernel, and is limited to a small set of generic fallback resolutions (max 1024x768) instead of its native 1920x1080. A second external monitor connected via DisplayPort to the same dock, and the same monitor/cable/port under Windows 11, work correctly at 1920x1080. This report also documents a related, already-fixed UCSI firmware-duplicate-altmode bug encountered on the same hardware, which is **not** the cause of the EDID issue but was investigated in the same session and may be relevant context. ## System information - **Laptop:** Dell Latitude 7420 (BIOS 1.51.0 and 1.52.0 both tested, no change) - **OS:** Ubuntu 26.04.1 LTS - **Kernels tested:** - `7.0.0-31-generic` (default Ubuntu kernel) - `7.1.13-070113-generic` (mainline build from kernel.ubuntu.com, includes upstream commit `67c92c6419ea6dbc5b1f3e9691aecea956e3e81c`) - **Dock:** Dell Pro Dock WD25Z (USB4/DisplayPort Alt Mode; does not negotiate as a Thunderbolt device — confirmed absent from `boltctl` output and from Windows' Thunderbolt Control Center on both ports) - **Affected monitor:** connected via DisplayPort on the dock - **Working monitor for comparison:** LG Electronics 22" (model reports as "LG FULL HD"), connected via a second DisplayPort output on the same dock ## Steps to reproduce 1. Connect the Dell WD25Z dock to the Latitude 7420 via USB-C. 2. Connect two external monitors to the dock's two DisplayPort outputs (one HDMI + one DP was also tested with the same result on the DP-connected monitor). 3. Boot Ubuntu. ## Expected behaviour Both external monitors are detected with correct EDID (vendor/product/serial) and offer their native 1920x1080 resolution, as happens under Windows 11 on the same hardware. ## Actual behaviour - One monitor (LG) is detected correctly every time. - The other monitor is detected as "Unknown Display" (GNOME/Mutter) with `Vendor: unknown`, `Product: unknown`, `Serial: unknown`, and is limited to a short list of fallback modes (`1024x768@60.004`, `848x480@60.000`, `800x600@60.317`, `800x600@56.250`, `640x480@59.940`) with no 1920x1080 option. - `/sys/class/drm/cardX-DP-Y/edid` for the affected connector reads back **0 bytes**, while the working monitor's EDID reads back correctly at the same time. - The DRM connector number assigned to the affected monitor changes on every boot and every resume from suspend (observed as `DP-5`, `DP-6`, `DP-9`, `DP-10` across different sessions for what is physically the same port), consistent with the dock's internal MST/DP hub re-enumerating non-deterministically. - DisplayPort Alt Mode itself negotiates successfully on the USB-C link for this monitor: `/sys/class/typec/portN/portN-partner/portN-partner.X/active` = `yes` with the DisplayPort mode active. The failure appears to be downstream, in the actual DP-AUX/EDID read over the dock's internal hub for this specific output. ## Separate, already-resolved issue encountered during investigation While investigating, the following kernel WARNING was found on kernel `7.0.0-31-generic` when hot-plugging the dock: ``` ucsi_acpi USBC000:00: con2: Firmware bug: duplicate partner altmode SVID 0x413c (VDO 0x00000001 vs 0x00000002) at offset 2, ignoring. Please update your system firmware. ------------[ cut here ]------------ WARNING: drivers/usb/typec/class.c:311 at typec_altmode_update_active+0x101/0x110 [typec] ... Call Trace: ucsi_altmode_update_active+0x116/0x1b0 [typec_ucsi] ucsi_check_altmodes+0x92/0xd0 [typec_ucsi] ucsi_poll_worker+0x41/0xe0 [typec_ucsi] ``` This matches the upstream fix "usb: typec: ucsi: Detect and skip duplicate altmodes from buggy firmware" (commit `67c92c6419ea6dbc5b1f3e9691aecea956e3e81c`, landed for v7.1.6/v7.2). After building and booting mainline kernel `7.1.13`, this WARNING/call trace no longer occurs. However: - `/sys/class/typec/port1/port1.2/` and `port1.3/` (port side) and `port1-partner.1/` and `.2/` (partner side) still both advertise SVID `413c` with distinct VDOs (`0x00000001` and `0x00000002`) — the duplication is still present in the dock's firmware, it is simply no longer causing a kernel warning/crash, which appears to be intentional given the port itself also advertises the SVID twice (a case the current fix logic treats as tolerable rather than as the "buggy firmware" case it filters). - **This fix did not resolve the EDID/resolution issue**, which persisted identically on kernel 7.1.13. The two issues are independent. I am not certain whether the EDID read failure is best classified as a kernel/DRM driver issue, a udev/enumeration-ordering issue, or purely a dock firmware issue outside the kernel's control — filing here in case it's the former, and in parallel reporting to Dell in case it's a dock firmware issue. ## Workaround currently in use Forcing a synthetic EDID via the `drm.edid_firmware` kernel parameter, mapped to the range of connector names observed across boots, restores 1920x1080 output but does not restore correct monitor identification and is not a real fix for the underlying EDID read failure or the connector renumbering. ## Additional information available on request - Full `dmesg` output from both kernel versions - `xrandr --verbose` output - `gdctl show --modes` output - `/sys/class/typec/` and `/sys/class/drm/` sysfs dumps ## Report generated by Claude AI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167904/+subscriptions

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

All autopkgtests for the newly accepted linux-restricted-modules-nvidia-6.8 (6.8.0-1064.67~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.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-restricted-modules-nvidia-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-6.8/6.8.0-146.146.1~22.04.1)

All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-6.8 (6.8.0-146.146.1~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.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-restricted-modules-lowlatency- hwe-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 2167877] Re: System update hangs on rsyslog error Sept-21-2026

** 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/2167877 Title: System update hangs on rsyslog error Sept-21-2026 Status in linux package in Ubuntu: New Bug description: System update as of Sep-21-2026 hangs on rsyslog error. -pressing cancel does nothing. Won't stop and reverse the update as expected. -the computer's fan runs profusely non stop even long after restart is issued. -system restart is the only recovery method. a screenshot of the bug is attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: spaceship 5341 F.... wireplumber /dev/snd/controlC1: spaceship 5341 F.... wireplumber /dev/snd/seq: spaceship 5320 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 21 11:47:40 2026 InstallationDate: Installed on 2026-09-12 (9 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Alienware Alienware m15 R3 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=2dbd6c8a-00b1-44ff-b27f-9cc4be6c79fc ro quiet splash lockdown=confidentiality crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2026 dmi.bios.release: 1.37 dmi.bios.vendor: Alienware dmi.bios.version: 1.37.0 dmi.board.name: Alienware m15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.37.0:bd07/08/2026:br1.37:svnAlienware:pnAlienwarem15R3:pvr1.37.0:rvnAlienware:rnAlienwarem15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku09CE:pfaAlienware: dmi.product.family: Alienware dmi.product.name: Alienware m15 R3 dmi.product.sku: 09CE dmi.product.version: 1.37.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167877/+subscriptions

[Bug 2031382] Re: ioprio_set03 in ubuntu_ltp_syscalls failed with J-oem-6.5 (TFAIL: ioprio_set IOPRIO_CLASS_BE prio 8 should not work)

** 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/2031382 Title: ioprio_set03 in ubuntu_ltp_syscalls failed with J-oem-6.5 (TFAIL: ioprio_set IOPRIO_CLASS_BE prio 8 should not work) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: New Bug description: SRU Justification: [Impact] On Jammy 6.8 series, ioprio_set system call does not return correct error value when setting IOPRIO_CLASS_BE to an invalid value. On Ubuntu Jammy, since we are using linux-klibc-dev package from 5.15 kernel the new ioprio level checking logic (added in upstream commit 893e5d32d5832674bcf6465f27958e883b72b346) resided in the 6.8 linux-klibc-dev headers will not be triggered. [Fix] Partially reverting the upstream commit eca2040972b411ec27483bf75dc8b84e730e88ff can workaround the issue. [Test Plan] Run LTP syscall testsuite `ioprio_set03` can sufficiently test the fix. [Where problems could occur] The patch could damage the ioprio_set system call handling further and cause issues with user-space applications that set the I/O priorities. [Other Info] Original bug report: Test failed with 6.5.0-1002.2. Test output: <<<test_start>>> tag=ioprio_set03 stime=1692085364 cmdline="ioprio_set03" contacts="" analysis=exit <<<test_output>>> incrementing stop tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s ioprio_set03.c:39: TFAIL: ioprio_set IOPRIO_CLASS_BE prio 8 should not work ioprio_set03.c:47: TINFO: tested illegal priority with class NONE ioprio_set03.c:50: TPASS: returned correct error for wrong prio: EINVAL (22) Summary: passed 1 failed 1 broken 0 skipped 0 warnings 0 <<<execution_status>>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<<test_end>>> Test case: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioprio/ioprio_set03.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031382/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1117.124)

All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1117.124) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (amd64, armhf) nvidia-graphics-drivers-390/unknown (i386) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.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-restricted-modules-aws [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 2167799] Re: Can't turn on Bluetooth

*** This bug is a duplicate of bug 2165873 *** https://bugs.launchpad.net/bugs/2165873 ** This bug has been marked a duplicate of bug 2165873 Bluetooth fails to initialize due to a kernel NULL pointer error -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167799 Title: Can't turn on Bluetooth Status in linux package in Ubuntu: New Bug description: [Expected Behavior] Bluetooth should turn on and be able to discover devices. It works perfectly on the older kernel version [Ubuntu, with Linux: 6.8.0-138]. [Actual Behavior] After the recent September update to kernel [Ubuntu, with Linux: 6.8.0-139], Bluetooth cannot be enabled. The toggle in the settings automatically switches back to "Off". [Steps to Reproduce] 1. Boot into the latest kernel ([6.8.0-139]). 2. Open Settings -> Bluetooth. 3. Try to turn Bluetooth on. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ni 2713 F.... wireplumber /dev/snd/controlC0: ni 2713 F.... wireplumber /dev/snd/seq: ni 2708 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 20:03:18 2026 InstallationDate: Installed on 2025-11-08 (316 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506NFR_FA506NFR ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=760880b1-41ea-410f-8a9e-bfc6f193138b ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2025-11-08 (316 days ago) dmi.bios.date: 03/21/2024 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA506NFR.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506NFR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA506NFR.300:bd03/21/2024:br5.24:efr3.0:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506NFR_FA506NFR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506NFR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA506NFR_FA506NFR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167799/+subscriptions