[РЕШЕНО] Ошибка № ...

пятница

[Bug 2062325] Re: Failed to read fan data for Asus Zenbook laptop

[Expired for lm-sensors (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lm-sensors (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2062325 Title: Failed to read fan data for Asus Zenbook laptop Status in linux package in Ubuntu: Incomplete Status in lm-sensors package in Ubuntu: Expired Bug description: Laptop: Asus Zenbook 14 UX435-EG [ 29.311703] asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19 [ 29.312163] asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19 [ 29.312630] asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19 [ 30.186596] thermal thermal_zone7: failed to read out thermal zone (-61) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: lm-sensors 1:3.6.0-9build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 15:01:26 2024 InstallationDate: Installed on 2024-03-22 (27 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: lm-sensors UpgradeStatus: Upgraded to noble on 2024-04-11 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062325/+subscriptions

[Bug 2155759] Re: package linux-headers-6.8.0-110-generic 6.8.0-110.110 failed to install/upgrade: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11

dkms autoinstall on 6.8.0-110-generic/x86_64 failed for anbox-ashmem(10) anbox-binder(10) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155759 Title: package linux-headers-6.8.0-110-generic 6.8.0-110.110 failed to install/upgrade: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 Status in linux package in Ubuntu: New Bug description: I didn't know this one, I just received a information about it. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-110-generic 6.8.0-110.110 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: lqdm12 30507 F.... pipewire /dev/snd/controlC0: lqdm12 30507 F.... pipewire lqdm12 30513 F.... wireplumber CasperMD5CheckResult: pass Date: Fri Jun 5 20:46:02 2026 ErrorMessage: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-04-23 (773 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 82MG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-40-generic root=UUID=475e5a4c-84b3-4d5f-a314-97697d9f1e94 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.12-1ubuntu7.3 SourcePackage: linux Title: package linux-headers-6.8.0-110-generic 6.8.0-110.110 failed to install/upgrade: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: Upgraded to noble on 2024-09-18 (626 days ago) dmi.bios.date: 06/14/2022 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H4CN25WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15IHU6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH4CN25WW(V1.10):bd06/14/2022:br1.25:efr1.25:svnLENOVO:pn82MG:pvrIdeaPadGaming315IHU6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPadGaming315IHU6:skuLENOVO_MT_82MG_BU_idea_FM_IdeaPadGaming315IHU6: dmi.product.family: IdeaPad Gaming 3 15IHU6 dmi.product.name: 82MG dmi.product.sku: LENOVO_MT_82MG_BU_idea_FM_IdeaPad Gaming 3 15IHU6 dmi.product.version: IdeaPad Gaming 3 15IHU6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155759/+subscriptions

[Bug 2155759] [NEW] package linux-headers-6.8.0-110-generic 6.8.0-110.110 failed to install/upgrade: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11

Public bug reported: I didn't know this one, I just received a information about it. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-110-generic 6.8.0-110.110 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: lqdm12 30507 F.... pipewire /dev/snd/controlC0: lqdm12 30507 F.... pipewire lqdm12 30513 F.... wireplumber CasperMD5CheckResult: pass Date: Fri Jun 5 20:46:02 2026 ErrorMessage: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-04-23 (773 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 82MG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-40-generic root=UUID=475e5a4c-84b3-4d5f-a314-97697d9f1e94 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.12-1ubuntu7.3 SourcePackage: linux Title: package linux-headers-6.8.0-110-generic 6.8.0-110.110 failed to install/upgrade: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: Upgraded to noble on 2024-09-18 (626 days ago) dmi.bios.date: 06/14/2022 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H4CN25WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15IHU6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH4CN25WW(V1.10):bd06/14/2022:br1.25:efr1.25:svnLENOVO:pn82MG:pvrIdeaPadGaming315IHU6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPadGaming315IHU6:skuLENOVO_MT_82MG_BU_idea_FM_IdeaPadGaming315IHU6: dmi.product.family: IdeaPad Gaming 3 15IHU6 dmi.product.name: 82MG dmi.product.sku: LENOVO_MT_82MG_BU_idea_FM_IdeaPad Gaming 3 15IHU6 dmi.product.version: IdeaPad Gaming 3 15IHU6 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155759 Title: package linux-headers-6.8.0-110-generic 6.8.0-110.110 failed to install/upgrade: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 Status in linux package in Ubuntu: New Bug description: I didn't know this one, I just received a information about it. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-110-generic 6.8.0-110.110 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: lqdm12 30507 F.... pipewire /dev/snd/controlC0: lqdm12 30507 F.... pipewire lqdm12 30513 F.... wireplumber CasperMD5CheckResult: pass Date: Fri Jun 5 20:46:02 2026 ErrorMessage: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-04-23 (773 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 82MG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-40-generic root=UUID=475e5a4c-84b3-4d5f-a314-97697d9f1e94 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.12-1ubuntu7.3 SourcePackage: linux Title: package linux-headers-6.8.0-110-generic 6.8.0-110.110 failed to install/upgrade: installed linux-headers-6.8.0-110-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: Upgraded to noble on 2024-09-18 (626 days ago) dmi.bios.date: 06/14/2022 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: H4CN25WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15IHU6 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrH4CN25WW(V1.10):bd06/14/2022:br1.25:efr1.25:svnLENOVO:pn82MG:pvrIdeaPadGaming315IHU6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPadGaming315IHU6:skuLENOVO_MT_82MG_BU_idea_FM_IdeaPadGaming315IHU6: dmi.product.family: IdeaPad Gaming 3 15IHU6 dmi.product.name: 82MG dmi.product.sku: LENOVO_MT_82MG_BU_idea_FM_IdeaPad Gaming 3 15IHU6 dmi.product.version: IdeaPad Gaming 3 15IHU6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155759/+subscriptions

[Bug 2155660] Re: Noble update: upstream stable patchset 2026-06-05

** 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/2155660 Title: Noble update: upstream stable patchset 2026-06-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: 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: upstream stable patchset 2026-06-05 Ported from the following upstream stable releases: v6.6.131, v6.12.78, v6.12.79, v6.12.80 from git://git.kernel.org/ perf: Extract a few helpers perf: Make sure to use pmu_ctx->pmu for groups cxl/hdm: Avoid incorrect DVSEC fallback when HDM decoders are enabled hwmon: (axi-fan-control) Use device firmware agnostic API hwmon: (axi-fan-control) Make use of dev_err_probe() hwmon: axi-fan: don't use driver_override as IRQ name sh: platform_early: remove pdev->driver_override check bpf: Release module BTF IDR before module unload bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN HID: asus: avoid memory leak in asus_report_fixup() platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list nvme-pci: cap queue creation to used queues nvme-fabrics: use kfree_sensitive() for DHCHAP secrets platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 nvme-pci: ensure we're polling a polled queue HID: magicmouse: fix battery reporting for Apple Magic Trackpad 2 HID: magicmouse: avoid memory leak in magicmouse_report_fixup() net: usb: r8152: add TRENDnet TUC-ET2G HID: mcp2221: cancel last I2C command on read error HID: asus: add xg mobile 2023 external hardware support module: Fix kernel panic when a symbol st_shndx is out of bounds ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() dma-buf: Include ioctl.h in UAPI header HID: apple: avoid memory leak in apple_report_fixup() btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 objtool: Handle Clang RSP musical chairs usb: core: new quirk to handle devices with zero configurations spi: intel-pci: Add support for Nova Lake mobile SPI flash xfrm: call xdo_dev_state_delete during state update xfrm: Fix the usage of skb->sk esp: fix skb leak with espintcp and async crypto af_key: validate families in pfkey_send_migrate() dma: swiotlb: add KMSAN annotations to swiotlb_bounce() can: statistics: add missing atomic access in hot path Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold Bluetooth: hci_ll: Fix firmware leak on error path Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb pinctrl: mediatek: common: Fix probe failure for devices without EINT ionic: fix persistent MAC address override on PF nfc: nci: fix circular locking dependency in nci_close_device net: openvswitch: Avoid releasing netdev before teardown completes openvswitch: defer tunnel netdev_put to RCU release openvswitch: validate MPLS set/set_masked payload length net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer rtnetlink: count IFLA_INFO_SLAVE_KIND in if_nlmsg_size platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen ice: use ice_update_eth_stats() for representor stats ipv6: Remove permanent routes from tb6_gc_hlist when all exceptions expire. ipv6: Don't remove permanent routes with exceptions from tb6_gc_hlist. tcp: optimize inet_use_bhash2_on_bind() udp: Fix wildcard bind conflict check when using hash2 net: enetc: fix the output issue of 'ethtool --show-ring' dma-mapping: add missing `inline` for `dma_free_attrs` Bluetooth: L2CAP: Fix send LE flow credits in ACL link Bluetooth: Remove 3 repeated macro definitions Bluetooth: hci_sync: Remove remaining dependencies of hci_request Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop Bluetooth: btusb: clamp SCO altsetting table indices tls: Purge async_hold in tls_decrypt_async_wait() netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() netfilter: nf_conntrack_expect: skip expectations in other netns via proc netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp netfilter: ctnetlink: use netlink policy range checks net: macb: use the current queue number for stats regmap: Synchronize cache for the page selector RDMA/rw: Fall back to direct SGE on MR pool exhaustion RDMA/irdma: Initialize free_qp completion before using it RDMA/irdma: Update ibqp state to error if QP is already in error state RDMA/irdma: Remove a NOP wait_event() in irdma_modify_qp_roce() RDMA/irdma: Clean up unnecessary dereference of event->cm_node RDMA/irdma: Remove reset check from irdma_modify_qp_to_err() RDMA/irdma: Fix deadlock during netdev reset with active connections RDMA/irdma: Return EINVAL for invalid arp index error scsi: scsi_transport_sas: Fix the maximum channel scanning issue x86/efi: efi_unmap_boot_services: fix calculation of ranges_to_free size drm/i915/gmbus: fix spurious timeout on 512-byte burst reads PM: hibernate: Don't ignore return from set_memory_ro() PM: hibernate: Drain trailing zero pages on userspace restore spi: sn-f-ospi: Fix resource leak in f_ospi_probe() ASoC: Intel: catpt: Fix the device initialization ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib hwmon: (adm1177) fix sysfs ABI violation and current unit conversion sysctl: fix uninitialized variable in proc_do_large_bitmap ASoC: adau1372: Fix unchecked clk_prepare_enable() return value ASoC: adau1372: Fix clock leak on PLL lock failure spi: spi-fsl-lpspi: fix teardown order issue (UAF) s390/syscalls: Add spectre boundary for syscall dispatch table s390/barrier: Make array_index_mask_nospec() __always_inline ksmbd: replace hardcoded hdr2_len with offsetof() in smb2_calc_max_out_buf_len() ksmbd: fix potencial OOB in get_file_all_info() for compound requests ksmbd: do not expire session on binding failure ALSA: firewire-lib: fix uninitialized local variable ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload can: gw: fix OOB heap access in cgw_csum_crc8_rel() can: isotp: fix tx.buf use-after-free in isotp_sendmsg() cpufreq: conservative: Reset requested_freq on limits change platform/x86: ISST: Correct locked bit width KVM: arm64: Discard PC update state on vcpu reset hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false s390/entry: Scrub r12 register on kernel entry erofs: add GFP_NOIO in the bio completion if needed alarmtimer: Fix argument order in alarm_timer_forward() scsi: ibmvfc: Fix OOB access in ibmvfc_discover_targets_done() scsi: ses: Handle positive SCSI error from ses_recv_diag() net: macb: Use dev_consume_skb_any() to free TX SKBs KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE jbd2: gracefully abort on checkpointing state corruptions irqchip/qcom-mpm: Add missing mailbox TX done acknowledgment dmaengine: sh: rz-dmac: Protect the driver specific lists dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock LoongArch: Workaround LS2K/LS7A GPU DMA hang bug xfs: stop reclaim before pushing AIL during unmount xfs: fix ri_total validation in xlog_recover_attri_commit_pass2 ext4: fix journal credit check when setting fscrypt context ext4: convert inline data to extents when truncate exceeds inline size ext4: fix fsync(2) for nojournal mode ext4: make recently_deleted() properly work with lazy itable initialization ext4: replace BUG_ON with proper error handling in ext4_read_inline_folio ext4: avoid infinite loops caused by residual data ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() ext4: reject mount if bigalloc with s_first_data_block != 0 ext4: fix use-after-free in update_super_work when racing with umount ext4: fix the might_sleep() warnings in kvfree() ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths ext4: always drain queued discard work in ext4_mb_release() arm64: dts: imx8mn-tqma8mqnl: fix LDO5 power off powerpc64/bpf: do not increment tailcall count when prog is NULL ksmbd: fix memory leaks and NULL deref in smb2_lock() tracing: Switch trace_osnoise.c code over to use guard() and __free() tracing: Fix potential deadlock in cpu hotplug with osnoise mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode libbpf: Fix -Wdiscarded-qualifiers under C23 mm/damon/sysfs: check contexts->nr before accessing contexts_arr[0] xfs: avoid dereferencing log items after push callbacks xfs: save ailp before dropping the AIL lock in push callbacks dmaengine: idxd: Fix not releasing workqueue on .release() dmaengine: idxd: Fix memory leak when a wq is reset phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() dmaengine: dw-edma: Fix multiple times setting of the CYCLE_STATE and CYCLE_BIT bits for HDMA. dmaengine: xilinx: xdma: Fix regmap init error handling dmaengine: xilinx: xilinx_dma: Fix dma_device directions dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction dmaengine: xilinx_dma: Fix reset related timeout with two-channel AXIDMA btrfs: fix super block offset in error message in btrfs_validate_super() btrfs: fix leak of kobject name for sub-group space_info btrfs: fix lost error when running device stats on multiple devices fs dmaengine: idxd: Fix freeing the allocated ida too late futex: Clear stale exiting pointer in futex_lock_pi() retry path ALSA: hda/realtek: Fix speaker pop on Star Labs StarFighter kexec: Consolidate machine_kexec_mask_interrupts() implementation UBUNTU: [Config] Enable GENERIC_IRQ_KEXEC_CLEAR_VM_FORWARD by default. kexec: Include kernel-end even without crashkernel powerpc/kexec/core: use big-endian types for crash variables drm/msm/dsi: fix hdisplay calculation when programming dsi registers perf disasm: Fix off-by-one bug in outside check net/mlx5: Fix crash when moving to switchdev mode bonding: add ESP offload features when slaves support bonding: Correctly support GSO ESP offload net: add a common function to compute features for upper devices bonding: use common function to compute the features bonding: fix type confusion in bond_setup_by_slave() xdp: allow attaching already registered memory model to xdp_rxq_info net: add generic percpu page_pool allocator net: do not consume a cacheline for system_page_pool xdp: register system page pool as an XDP memory model net: add xmit recursion limit to tunnel xmit functions netfilter: nf_tables: always walk all pending catchall elements net: prevent NULL deref in ip[6]tunnel_xmit() ata: libata-core: Add BRIDGE_OK quirk for QEMU drives usb: typec: altmode/displayport: set displayport signaling rate in configure message rust: kbuild: allow `unused_features` ceph: add a bunch of missing ceph_path_info initializers net/tcp-ao: Fix MAC comparison to be constant-time drm/amd/pm: remove invalid gpu_metrics.energy_accumulator on smu v13.0.x tracing: Fix enabling multiple events on the kernel command line and bootconfig qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size xfs: fix returned valued from xfs_defer_can_append iio: imu: inv_icm42600: add support of ICM-42686-P iio: imu: inv_icm42600: fix odr switch when turning buffer off perf/x86/intel/uncore: Support more units on Granite Rapids perf/x86/intel/uncore: Add per-scheduler IMC CAS count events cleanup: Provide retain_and_null_ptr() usb: gadget: f_ncm: Fix net_device lifecycle with device_move KVM: x86: Co-locate initialization of feature MSRs in kvm_arch_vcpu_create() KVM: x86: Quirk initialization of feature MSRs to KVM's max configuration KVM: x86: do not allow re-enabling quirks KVM: x86: Allow vendor code to disable quirks KVM: x86: Introduce supported_quirks to block disabling quirks KVM: x86: Remove VMX support for virtualizing guest MTRR memtypes KVM: VMX: Drop support for forcing UC memory when guest CR0.CD=1 KVM: x86: Introduce Intel specific quirk KVM_X86_QUIRK_IGNORE_GUEST_PAT KVM: nVMX: Add consistency checks for CR0.WP and CR4.CET KVM: x86: Introduce KVM_X86_QUIRK_VMCS12_ALLOW_FREEZE_IN_SMM drm/xe/sync: Cleanup partially initialized sync on parse failure ice: fix devlink reload call trace io_uring/uring_cmd: fix too strict requirement on ioctl erofs: fix inline data read failure for ztailpacking pclusters mm: merge folio_is_secretmem() and folio_fast_pin_allowed() into gup_fast_folio_allowed() mm: thp: deny THP for files on anonymous inodes sched/fair: Fix zero_vruntime tracking mac80211: fix crash in ieee80211_chan_bw_change for AP_VLAN stations drm/i915/dsc: Add Selective Update register definitions drm/imagination: Fix deadlock in soft reset sequence ata: libata-scsi: Return residual for emulated SCSI commands ata: libata-scsi: report correct sense field pointer in ata_scsiop_maint_in() soc: microchip: mpfs: Fix memory leak in mpfs_sys_controller_probe() firmware: arm_ffa: Remove vm_id argument in ffa_rxtx_unmap() Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers nf_tables: nft_dynset: fix possible stateful expression memleak in error path bonding: prevent potential infinite loop in bond_header_parse() drm/i915/psr: Compute PSR entry_setup_frames into intel_crtc_state perf/x86/intel: Add missing branch counters constraint apply Revert "LoongArch: Add machine_kexec_mask_interrupts() implementation" cxl/port: Fix use after free of parent_port in cxl_detach_ep() driver core: generalize driver_override in struct device driver core: platform: use generic driver_override infrastructure bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list kbuild: install-extmod-build: Package resolve_btfids if necessary nvmet: move async event work off nvmet-wq ALSA: hda/realtek: add quirk for ASUS UM6702RC i3c: master: dw-i3c: Fix missing of_node for virtual I2C adapter xfrm: add missing extack for XFRMA_SA_PCPU in add_acquire and allocspi xfrm: fix the condition on x->pcpu_num in xfrm_sa_len xfrm: prevent policy_hthresh.work from racing with netns teardown Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete net: bcmasp: remove eee_enabled/eee_active in bcmasp_get_eee() net: bcm: asp2: fix LPI timer handling net: bcm: asp2: remove tx_lpi_enabled net: bcmasp: Add support for ASP 2.2 net: bcm: asp2: convert to phylib managed EEE net: bcmasp: Remove support for asp-v2.0 net: bcmasp: streamline early exit in probe net: bcmasp: fix double free of WoL irq net: bcmasp: Add support for asp-v3.0 net: bcmasp: fix double disable of clk platform/x86: intel-hid: disable wakeup_mode during hibernation iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() team: fix header_ops type confusion with non-Ethernet ports ALSA: hda/realtek: Sequence GPIO2 on Star Labs StarFighter spi: meson-spicc: Fix double-put in remove path drm/amd/display: Do not skip unrelated mode changes in DSC validation spi: Group CS related fields in struct spi_device spi: use generic driver_override infrastructure hwmon: (pmbus/core) Fix various coding style issues hwmon: (pmbus) Mark lowest/average/highest/rated attributes as read-only hwmon: (pmbus) Introduce the concept of "write-only" attributes x86/cpu: Enable FSGSBASE early in cpu_init_exception_handling() ovl: fix wrong detection of 32bit inode numbers net: macb: Move devm_{free,request}_irq() out of spin lock area dmaengine: fsl-edma: change to guard(mutex) within fsl_edma3_xlate() dmaengine: fsl-edma: fix channel parameter config for fixed channel requests LoongArch: Fix missing NULL checks for kstrdup() xfs: scrub: unlock dquot before early return in quota scrub ext4: validate p_idx bounds in ext4_ext_correct_indexes LoongArch: vDSO: Emit GNU_EH_FRAME correctly spi: tegra210-quad: Protect curr_xfer check in IRQ handler media: nxp: imx8-isi: Fix streaming cleanup on release rust: pin-init: internal: init: document load-bearing fact of field accessors ovl: Use str_on_off() helper in ovl_show_options() ovl: make fsync after metadata copy-up opt-in mount option virt: tdx-guest: Fix handling of host controlled 'quote' buffer length net: add proper RCU protection to /proc/net/ptype landlock: Optimize file path walks and prepare for audit support landlock: Fix handling of disconnected directories idpf: check error for register_netdev() on init idpf: detach and close netdevs while handling a reset idpf: Fix RSS LUT NULL pointer crash on early ethtool operations idpf: Fix RSS LUT NULL ptr issue after soft reset ASoC: ak4458: Convert to RUNTIME_PM_OPS() & co netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() xen/privcmd: unregister xenstore notifier on module exit futex: Require sys_futex_requeue() to have identical flags dmaengine: idxd: Fix leaking event log memory net: bcmasp: Restore programming of TX map vector register net: bcmasp: Fix network filter wake for asp-3.0 idpf: nullify pointers after they are freed UBUNTU: Upstream stable to v6.6.131, v6.12.78, v6.12.79, v6.12.80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155660/+subscriptions

[Bug 2155732] Re: Bluetooth LE devices fail to reconnect after suspend/resume on kernel 6.17.0-35

** 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/2155732 Title: Bluetooth LE devices fail to reconnect after suspend/resume on kernel 6.17.0-35 Status in linux package in Ubuntu: New Bug description: Bluetooth LE devices fail to reconnect after suspend/resume on kernel 6.17.0-35-generic. Reverting to 6.17.0-29-generic resolves the issue completely. System: Linux Mint 22.3 (based on Ubuntu 24.04) Kernel broken: 6.17.0-35-generic Kernel working: 6.17.0-29-generic Bluetooth adapter: Intel AX201 (8087:0026) Affected device: Logitech ERGO K860 keyboard (Bluetooth LE) Unaffected device: Logitech mouse (works fine on resume with both kernels) Steps to reproduce: 1. Boot into kernel 6.17.0-35-generic 2. Connect Logitech ERGO K860 via Bluetooth 3. Suspend the machine 4. Resume 5. Keyboard fails to reconnect with error: le-connection-abort-by-local Expected: Keyboard reconnects automatically after resume as it did on 6.17.0-29 Actual: Keyboard fails with le-connection-abort-by-local, requires full reboot to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155732/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp/5.15.0-1110.120)

All autopkgtests for the newly accepted linux-restricted-modules-gcp (5.15.0-1110.120) 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, 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-gcp [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 2155619] Re: [SRU] Correct FIXED_VS Link Rate Toggle Condition

** Description changed: [ Impact ] Users connecting a Lenovo USB-C to VGA Adapter (or similar USB-C DP adapters with a FIXED_VS LTTPR retimer) get no display output. The AMD display driver fails DP link training and logs: - amdgpu 0000:c4:00.0: [drm] enabling link 2 failed: 15 + amdgpu 0000:c4:00.0: [drm] enabling link 2 failed: 15 The fix is a single-line change: - - if (memcmp("\x0,\x0,\x0", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) - + if (memcmp("\x00\x00\x00", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) + - if (memcmp("\x0,\x0,\x0", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) + + if (memcmp("\x00\x00\x00", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) The root cause is a typo in a C string literal used to check whether a FIXED_VS LTTPR retimer has no IEEE OUI. The literal "\x0,\x0,\x0" was intended to be three zero bytes but actually evaluates to five bytes {0x00, 0x2C, 0x00, 0x2C, 0x00} (0x2C = ASCII comma) because commas are not valid hex digits and terminate the \x escape early. The memcmp() against the 3-byte LTTPR OUI field therefore never matches, so the vendor-specific link rate toggle workaround required by these retimers is never applied, and link training fails. [ Test Plan ] 1. Connect a Lenovo USB-C to VGA Adapter to a system with an AMD GPU. 2. Without patch: confirm no display output and observe the following in dmesg: - amdgpu ...: [drm] enabling link N failed: 15 + amdgpu ...: [drm] enabling link N failed: 15 3. Install a new kernel with patch: confirm display output appears and the "enabling link failed: 15" - message is absent from dmesg. + message is absent from dmesg. [ Where problems could occur ] The change is confined to the FIXED_VS LTTPR link training path (dp_perform_fixed_vs_pe_training_sequence). It only affects systems where: - - An AMD GPU with USB-C DP output is present, AND - - A DP retimer (LTTPR) with no IEEE OUI is detected on the link. + - An AMD GPU with USB-C DP output is present, AND + - A DP retimer (LTTPR) with no IEEE OUI is detected on the link. The risk of regression is very low — the fix corrects a comparison that was always false before, restoring the originally intended behaviour. Systems without a FIXED_VS LTTPR retimer are completely unaffected. [ Other Info ] Upstream commit: 531fe6e0fee85a1bdb5b8223a706fff654ed0a61 (v7.0-rc1) Stable backport: 91e6b6a7fe57d48c392d353ee50162a525d9e80c (v6.19.6) - Reported against: linux-oem-6.17 6.17.0-1025.25 + Affected kernel on noble and questing: + linux-oem-6.17 6.17.0-1025.25 + linux-image-generic-hwe-24.04 6.17.0-35.35~24.04.1 + Noble's hwe-24.04-edge and resolute is not affected. + linux-image-generic-hwe-24.04-edge 7.0.0-14.14~24.04.3 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155619 Title: [SRU] Correct FIXED_VS Link Rate Toggle Condition Status in linux package in Ubuntu: In Progress Bug description: [ Impact ] Users connecting a Lenovo USB-C to VGA Adapter (or similar USB-C DP adapters with a FIXED_VS LTTPR retimer) get no display output. The AMD display driver fails DP link training and logs: amdgpu 0000:c4:00.0: [drm] enabling link 2 failed: 15 The fix is a single-line change: - if (memcmp("\x0,\x0,\x0", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) + if (memcmp("\x00\x00\x00", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) The root cause is a typo in a C string literal used to check whether a FIXED_VS LTTPR retimer has no IEEE OUI. The literal "\x0,\x0,\x0" was intended to be three zero bytes but actually evaluates to five bytes {0x00, 0x2C, 0x00, 0x2C, 0x00} (0x2C = ASCII comma) because commas are not valid hex digits and terminate the \x escape early. The memcmp() against the 3-byte LTTPR OUI field therefore never matches, so the vendor-specific link rate toggle workaround required by these retimers is never applied, and link training fails. [ Test Plan ] 1. Connect a Lenovo USB-C to VGA Adapter to a system with an AMD GPU. 2. Without patch: confirm no display output and observe the following in dmesg: amdgpu ...: [drm] enabling link N failed: 15 3. Install a new kernel with patch: confirm display output appears and the "enabling link failed: 15" message is absent from dmesg. [ Where problems could occur ] The change is confined to the FIXED_VS LTTPR link training path (dp_perform_fixed_vs_pe_training_sequence). It only affects systems where: - An AMD GPU with USB-C DP output is present, AND - A DP retimer (LTTPR) with no IEEE OUI is detected on the link. The risk of regression is very low — the fix corrects a comparison that was always false before, restoring the originally intended behaviour. Systems without a FIXED_VS LTTPR retimer are completely unaffected. [ Other Info ] Upstream commit: 531fe6e0fee85a1bdb5b8223a706fff654ed0a61 (v7.0-rc1) Stable backport: 91e6b6a7fe57d48c392d353ee50162a525d9e80c (v6.19.6) Affected kernel on noble and questing: linux-oem-6.17 6.17.0-1025.25 linux-image-generic-hwe-24.04 6.17.0-35.35~24.04.1 Noble's hwe-24.04-edge and resolute is not affected. linux-image-generic-hwe-24.04-edge 7.0.0-14.14~24.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155619/+subscriptions

[Bug 2155619] [NEW] [SRU] Correct FIXED_VS Link Rate Toggle Condition

Public bug reported: [ Impact ] Users connecting a Lenovo USB-C to VGA Adapter (or similar USB-C DP adapters with a FIXED_VS LTTPR retimer) get no display output. The AMD display driver fails DP link training and logs: amdgpu 0000:c4:00.0: [drm] enabling link 2 failed: 15 The fix is a single-line change: - if (memcmp("\x0,\x0,\x0", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) + if (memcmp("\x00\x00\x00", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) The root cause is a typo in a C string literal used to check whether a FIXED_VS LTTPR retimer has no IEEE OUI. The literal "\x0,\x0,\x0" was intended to be three zero bytes but actually evaluates to five bytes {0x00, 0x2C, 0x00, 0x2C, 0x00} (0x2C = ASCII comma) because commas are not valid hex digits and terminate the \x escape early. The memcmp() against the 3-byte LTTPR OUI field therefore never matches, so the vendor-specific link rate toggle workaround required by these retimers is never applied, and link training fails. [ Test Plan ] 1. Connect a Lenovo USB-C to VGA Adapter to a system with an AMD GPU. 2. Without patch: confirm no display output and observe the following in dmesg: amdgpu ...: [drm] enabling link N failed: 15 3. Install a new kernel with patch: confirm display output appears and the "enabling link failed: 15" message is absent from dmesg. [ Where problems could occur ] The change is confined to the FIXED_VS LTTPR link training path (dp_perform_fixed_vs_pe_training_sequence). It only affects systems where: - An AMD GPU with USB-C DP output is present, AND - A DP retimer (LTTPR) with no IEEE OUI is detected on the link. The risk of regression is very low — the fix corrects a comparison that was always false before, restoring the originally intended behaviour. Systems without a FIXED_VS LTTPR retimer are completely unaffected. [ Other Info ] Upstream commit: 531fe6e0fee85a1bdb5b8223a706fff654ed0a61 (v7.0-rc1) Stable backport: 91e6b6a7fe57d48c392d353ee50162a525d9e80c (v6.19.6) Reported against: linux-oem-6.17 6.17.0-1025.25 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Bin Li (binli) Status: In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155619 Title: [SRU] Correct FIXED_VS Link Rate Toggle Condition Status in linux package in Ubuntu: In Progress Bug description: [ Impact ] Users connecting a Lenovo USB-C to VGA Adapter (or similar USB-C DP adapters with a FIXED_VS LTTPR retimer) get no display output. The AMD display driver fails DP link training and logs: amdgpu 0000:c4:00.0: [drm] enabling link 2 failed: 15 The fix is a single-line change: - if (memcmp("\x0,\x0,\x0", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) + if (memcmp("\x00\x00\x00", &link->dpcd_caps.lttpr_caps.lttpr_ieee_oui[0], 3) == 0) The root cause is a typo in a C string literal used to check whether a FIXED_VS LTTPR retimer has no IEEE OUI. The literal "\x0,\x0,\x0" was intended to be three zero bytes but actually evaluates to five bytes {0x00, 0x2C, 0x00, 0x2C, 0x00} (0x2C = ASCII comma) because commas are not valid hex digits and terminate the \x escape early. The memcmp() against the 3-byte LTTPR OUI field therefore never matches, so the vendor-specific link rate toggle workaround required by these retimers is never applied, and link training fails. [ Test Plan ] 1. Connect a Lenovo USB-C to VGA Adapter to a system with an AMD GPU. 2. Without patch: confirm no display output and observe the following in dmesg: amdgpu ...: [drm] enabling link N failed: 15 3. Install a new kernel with patch: confirm display output appears and the "enabling link failed: 15" message is absent from dmesg. [ Where problems could occur ] The change is confined to the FIXED_VS LTTPR link training path (dp_perform_fixed_vs_pe_training_sequence). It only affects systems where: - An AMD GPU with USB-C DP output is present, AND - A DP retimer (LTTPR) with no IEEE OUI is detected on the link. The risk of regression is very low — the fix corrects a comparison that was always false before, restoring the originally intended behaviour. Systems without a FIXED_VS LTTPR retimer are completely unaffected. [ Other Info ] Upstream commit: 531fe6e0fee85a1bdb5b8223a706fff654ed0a61 (v7.0-rc1) Stable backport: 91e6b6a7fe57d48c392d353ee50162a525d9e80c (v6.19.6) Reported against: linux-oem-6.17 6.17.0-1025.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155619/+subscriptions

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

Public bug reported: On Ubuntu 24.04.2 LTS running on a Lenovo Legion 5 Pro 16ACH6H (AMD + NVIDIA RTX 3070 hybrid system), brightness control breaks starting from kernel 6.17.0-23-generic and remains broken on all newer kernels up to 6.17.0-35. The issue is fully reproducible. WORKING KERNEL: - 6.17.0-22-generic - Display session: X11 - NVIDIA proprietary driver in use - Backlight device present: /sys/class/backlight/nvidia_0 - Brightness control works normally BROKEN KERNELS: - 6.17.0-23-generic and newer (tested up to 6.17.0-35) - Wayland or X11 both affected - Backlight directory is empty: /sys/class/backlight/ SYMPTOMS: - Brightness stuck at 100% - No backlight device exposed in sysfs - Mouse cursor shows trailing/ghosting artifacts on Wayland - Display rendering instability EXPECTED BEHAVIOR: - /sys/class/backlight/nvidia_0 should be present - Brightness control should function via NVIDIA DRM backlight interface ACTUAL BEHAVIOR: - No backlight device is registered at all in /sys/class/backlight/ - GNOME brightness controls have no effect HARDWARE: - Lenovo Legion 5 Pro 16ACH6H - AMD Ryzen CPU (iGPU present but not used for display in working kernel) - NVIDIA RTX 3070 Mobile (primary display output via nvidia-drm) - NVIDIA proprietary driver active REGRESSION: - Kernel 6.17.0-22 works correctly - 6.17.0-23 introduces regression and all newer kernels inherit it This appears to be a regression in NVIDIA DRM backlight device registration (fbdev / sysfs exposure). ** 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/2155617 Title: Backlight device disappears and brightness breaks on kernel 6.17.0-23+ (Lenovo Legion 5 Pro, NVIDIA hybrid graphics) Status in linux package in Ubuntu: New Bug description: On Ubuntu 24.04.2 LTS running on a Lenovo Legion 5 Pro 16ACH6H (AMD + NVIDIA RTX 3070 hybrid system), brightness control breaks starting from kernel 6.17.0-23-generic and remains broken on all newer kernels up to 6.17.0-35. The issue is fully reproducible. WORKING KERNEL: - 6.17.0-22-generic - Display session: X11 - NVIDIA proprietary driver in use - Backlight device present: /sys/class/backlight/nvidia_0 - Brightness control works normally BROKEN KERNELS: - 6.17.0-23-generic and newer (tested up to 6.17.0-35) - Wayland or X11 both affected - Backlight directory is empty: /sys/class/backlight/ SYMPTOMS: - Brightness stuck at 100% - No backlight device exposed in sysfs - Mouse cursor shows trailing/ghosting artifacts on Wayland - Display rendering instability EXPECTED BEHAVIOR: - /sys/class/backlight/nvidia_0 should be present - Brightness control should function via NVIDIA DRM backlight interface ACTUAL BEHAVIOR: - No backlight device is registered at all in /sys/class/backlight/ - GNOME brightness controls have no effect HARDWARE: - Lenovo Legion 5 Pro 16ACH6H - AMD Ryzen CPU (iGPU present but not used for display in working kernel) - NVIDIA RTX 3070 Mobile (primary display output via nvidia-drm) - NVIDIA proprietary driver active REGRESSION: - Kernel 6.17.0-22 works correctly - 6.17.0-23 introduces regression and all newer kernels inherit it This appears to be a regression in NVIDIA DRM backlight device registration (fbdev / sysfs exposure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155617/+subscriptions

[Bug 2150196] Re: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms

Now 26.04 could be upgraded from 25.10. So I added the resolute repo in /etc/apt/sources, after that I installed the linux-generic-hwe-26.04 from resolute-proposed. Then the audio works beautifully. So the alsa- ucm-conf in questing works. I set the verification to done so that we wont' block the next release. $ do-release-upgrade -c Checking for a new Ubuntu release New release '26.04 LTS' available. Run 'do-release-upgrade' to upgrade to it. $ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://archive.ubuntu.com/ubuntu/ Suites: questing questing-updates questing-backports questing-proposed Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu/ Suites: questing-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://archive.ubuntu.com/ubuntu/ Suites: resolute resolute-updates resolute-backports resolute-proposed Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg ** Tags removed: verification-needed-questing ** Tags added: verification-done-questing -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150196 Title: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: Fix Committed Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in alsa-ucm-conf source package in Questing: Fix Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: New Status in alsa-ucm-conf source package in Resolute: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Status in alsa-ucm-conf source package in Stonking: Fix Released Status in linux source package in Stonking: Fix Committed Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: SRU Justification: [ Impact ] Lenovo PTL systems with rt722 headset codec + rt1320 speaker amp over SoundWire have no speaker audio and no DMIC. The kernel's PTL match table lacks the rt722_l0_rt1320_l23 topology, the rt1320 codec_info_list is missing its DMIC dai, and the is_amp flag is absent -- so the machine driver never matches and the wrong name prefix is assigned. [ Fix ] Seven upstream commits from Linus's mainline, applied in topological order: 1. 38ecd1384079 (v6.19) -- add ptl_rt722_l0_rt1320_l23 match table entry 2. 4fbd3b2ec04d (v7.0) -- use aggregated endpoints for rt722 in that entry 3. 403a0591be68 (v6.19) -- fix name_prefix of second rt1320 (rt1320-2) 4. 754b3dade5dd (v7.0) -- drop rt721 monolithic match tables (prerequisite for 5) 5. 9033f7b7f27d (linux/master, not yet tagged) -- drop rt722 monolithic match tables 6. dd4a1963ddf0 (linux/master, not yet tagged) -- add is_amp flag to fix wrong name prefix 7. ae2cb3384337 (linux/master, not yet tagged) -- add rt1320/rt1321 DMIC dai in codec_info_list All cherry-pick cleanly with zero conflicts. Diffs are byte-identical to upstream (only hunk offsets and context lines differ due to different base tree). [ Test Plan ] On a Lenovo PTL system with spk:rt1320 + hs:rt722: 1. Boot without patches: no speaker sound card components, no DMIC 2. Boot with patches: - Speaker playback: aplay -D hw:0,2 tone.wav - DMIC loopback: play 1kHz tone through speaker, record from DMIC, FFT confirms peak at 1000 Hz - WirePlumber sees all devices - Mute LEDs functional (speaker and mic) - Suspend/resume: full status diff pre vs post identical, loopback and LEDs work after resume [ Where problems could occur ] Patches touch PTL match tables, SoundWire codec_info_list, and SOF HDA codec matching. A wrong match table entry could cause a different PTL topology to break (wrong codec matched). The is_amp flag override in find_acpi_adr_device() runs for all SoundWire codecs on Intel SOF platforms -- if the flag logic is wrong, non-amp codecs could get misidentified, breaking name prefixes and DAI routing. Commits 4-5 remove rt721/rt722 monolithic match tables; any PTL machine still relying on monolithic matching (rather than function topologies) would lose its match entry. [ Other Info ] Commits 5-7 are merged on linux/master but not yet in a tagged release. Tested on two Lenovo PTL machines -- full audio pass including loopback and suspend/resume. Target: oem-6.17 and resolute only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150196/+subscriptions

[Bug 2155120] Re: Fix audio mute function not working on new Dell platforms

** Changed in: linux (Ubuntu Resolute) Status: New => Fix Released ** Changed in: linux (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Resolute) 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/2155120 Title: Fix audio mute function not working on new Dell platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Microphone mute hotkey(F4) have no function on Dell Sunfire powered by the AMD platform [Fix] Fix by backporting the commit: 26a7601471f6 ("platform/x86: dell-wmi: Add audio/mic mute key codes") by adding the corresponding key code for mute and mic mute. [Test Case] 1. Boot up the machine of new Dell Sunfire platforms 2. Press Fn+F4 to verify the mic-mute function. 3. Make sure the mic is muted by `arecord` [Where problems could occur] It only adds the key codes for the mic-mute and mute on some Dell platforms. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2155120/+subscriptions

[Bug 2155222] Re: [hyperv] Ensure MMIO Mapping is Correct for Kexec / kdump kernel on Azure v6 Instance Types

** 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/2155222 Title: [hyperv] Ensure MMIO Mapping is Correct for Kexec / kdump kernel on Azure v6 Instance Types Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux source package in Resolute: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2155222 [Impact] Jammy VMs running on "Gen2" v6 instance types on Azure fail to collect a kdump with both the 5.15 and 6.8 HWE kernel, yet kdump succeeds for 6.8 onward on noble onward. Even stranger, it succeeds on jammy with secureboot enabled, and fails with secureboot disabled. The difference between jammy and noble onward can be explained with userspace tools, as kdump-tools uses -c (--kexec-syscall) by default, and changes to -s (--kexec-file-syscall) when secureboot is enabled. Noble onward works due to using -a (--kexec-syscall-auto) by default, which defaults to -s. Noble will fail when using -c instead. From man kexec: -s (--kexec-file-syscall) Specify that the new KEXEC_FILE_LOAD syscall should be used exclusively. -c (--kexec-syscall) Specify that the old KEXEC_LOAD syscall should be used exclusively (the default). -a (--kexec-syscall-auto) Try the new KEXEC_FILE_LOAD syscall first and when it is not supported or the kernel does not understand the supplied image fall back to the old KEXEC_LOAD interface. There is no one single interface that always works. KEXEC_FILE_LOAD is required on systems that use locked-down secure boot to verify the kernel signature. KEXEC_LOAD may be also disabled in the kernel configuration. KEXEC_LOAD is required for some kernel image formats and on architectures that do not implement KEXEC_FILE_LOAD. Regardless, the issue is actually a hyperv subsystem issue in the kernel. When the kexec / kdump kernel boots, vmbus_reserve_fb() fails to reserve the framebuffer MMIO range due to a Gen2 VM's screen.lfb_base being zero. This causes a MMIO conflict between hyperv-drm and pci-hyperv: when the pci-hyperv's hv_allocate_config_window() calls vmbus_allocate_mmio() to get an MMIO range, it usually gets a 32-bit MMIO range that overlaps with the framebuffer MMIO range, and later hv_pci_enter_d0() fails with an error message "PCI Pass-through VSP failed D0 Entry with status" since the host thinks that PCI devices must not use MMIO space that the host has assigned to the framebuffer. This is especially an issue if pci-hyperv is built-in and hyperv-drm is built as a module. Consequently, the kdump/kexec kernel fails to detect PCI devices via pci-hyperv, and may fail to mount the root file system, which may reside in a NVMe disk. The end result is that capturing kdumps fail when -c (--kexec-syscall) is used, which is the default on jammy. [Fix] This is currently queued up in the hyperv maintainer tree, in the hyperv-fixes branch: commit 016a25e4b0df4d77e7c258edee4aaf982e4ee809 hyperv From: Dexuan Cui <decui@microsoft.com> Date: Thu, 7 May 2026 14:28:38 -0700 Subject: Drivers: hv: vmbus: Improve the logic of reserving fb_mmio on Gen2 VMs Link: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-fixes&id=016a25e4b0df4d77e7c258edee4aaf982e4ee809 This is expected to make the 7.2 merge window. This fix is required for hyperv users, and is mostly relevant for -azure users only, but I am still requesting this for -generic to ensure that anyone using -generic on Azure can still kexec, and to make it easier to bisect -generic on Azure in the future. [Testcase] This needs to be tested on Azure on both v5 and v6 instance types. The issue occurs with v6 instance types, but we need to ensure we do not cause a regression with v5 instance types. For each series you are testing, create a VM with the following instance types: - Standard_D4ads_v5 - Standard_D4ads_v6 For the image type, you need to select "Gen2" images: - "Ubuntu Server 22.04 LTS - x64 Gen2" - "Ubuntu Server 24.04 LTS - x64 Gen2" - "Ubuntu Server 25.10 - x64 Gen 2" - "Ubuntu Server 26.04 LTS - x64 Gen 2" If you are going to test with -c (--kexec-syscall), secureboot needs to be disabled, and you can do this with: - Under Security type, select "Configure security features" - uncheck "Enable Secure Boot". Save. Create the VM. Log in, and install kdump-tools: $ sudo apt update $ sudo apt install kdump-tools Say yes to each prompt. $ sudo vim /etc/default/grub.d/kdump-tools.cfg Change crashkernel=512M-:192M from 192M to 1G, save, exit. $ sudo vim /etc/kernel/postinst.d/kdump-tools Change dep to most, save exit. $ sudo update-grub $ sudo reboot Verify that the cmdline has crashkernel set to 1G memory: $ cat /proc/cmdline $ kdump-config show On the Azure Web Interface, select "Serial Console" for the VM, and watch the serial console. $ sudo sysctl -w kernel.sysrq=1 $ sudo su $ echo c > /proc/sysrq-trigger Watch the kernel panic and reboot into the crash kernel. On failure: The kexec kernel gets stuck, and writes these messages to dmesg. [ 1.157729] hv_pci 7ad35d50-c05b-47ab-b3a0-56a9a845852b: PCI VMBus probing: Using version 0x10004 [ 1.167427] hv_pci 7ad35d50-c05b-47ab-b3a0-56a9a845852b: Retrying D0 Entry [ 1.173231] hv_pci 7ad35d50-c05b-47ab-b3a0-56a9a845852b: PCI Pass-through VSP failed D0 Entry with status c000000d [ 1.181091] hv_vmbus: probe failed for device 7ad35d50-c05b-47ab-b3a0-56a9a845852b (-71) [ 1.186890] hv_pci: probe of 7ad35d50-c05b-47ab-b3a0-56a9a845852b failed with error -71 [ 1.194422] hv_pci 00000001-7870-47b5-b203-907d12ca697e: PCI VMBus probing: Using version 0x10004 [ 1.202172] hv_pci 00000001-7870-47b5-b203-907d12ca697e: Retrying D0 Entry [ 1.207877] hv_pci 00000001-7870-47b5-b203-907d12ca697e: PCI Pass-through VSP failed D0 Entry with status c000000d The kexec kernel gives up, and reboots. No kdump is generated. /var/crash will be empty. On success: The kdump is collected, and saved to /var/crash, and will be present on next boot. There are test kernels available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf425760-test If you install the test kernel and reboot, kdump will work correctly on v6 instance types. [Where problems could occur] This changes how vmbus_reserve_fb() reserves MMIO space for the framebuffer, and if a regression were to occur, it could affect the pci-hyperv and hyperv-drm drivers from being able to claim the correct MMIO ranges. This could show as instances failing to start or failing to kexec / collect a kdump with the crashkernel. This fix works both on amd64 and arm64 instance types, as well as with 32bit and 64bit pci busses. [Other info] Upstream mailing list threads: Abandoned Patch: V1: https://lore.kernel.org/linux-hyperv/20260122020337.94967-1-decui@microsoft.com/ V2: https://lore.kernel.org/linux-hyperv/20260402234313.2490779-1-decui@microsoft.com/ Current Patch: V1: https://lore.kernel.org/linux-hyperv/20260416183529.838321-1-decui@microsoft.com/ V2: https://lore.kernel.org/linux-hyperv/20260505004846.193441-1-decui@microsoft.com/ V3: https://lore.kernel.org/linux-hyperv/20260507212838.448891-1-decui@microsoft.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155222/+subscriptions