Public bug reported: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. ** 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/2152546 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: New Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152546/+subscriptions
четверг
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
Would 'apt install -t resolute-base linux-generic' work? Just guessing, replacing "proposed" with "base"... -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2152259] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2152259/+attachment/5970184/+files/ProcCpuinfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152259 Title: RTL8852AE (PCIe WiFi + USB BT combo) Bluetooth Failure Status in linux package in Ubuntu: Incomplete Bug description: Hardware: HP Pavilion Gaming 15-ec2xxx Chip: RTL8852AE (PCIe WiFi + USB BT combo) Symptom: hci0: RTL: Read reg16 failed (-110) crash loop triggered by BT connection attempt Kernel: 6.17.0-23-generic --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: svrt_ubu 14754 F.... wireplumber /dev/snd/controlC0: svrt_ubu 14754 F.... wireplumber /dev/snd/seq: svrt_ubu 14749 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2025-08-01 (286 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: HP HP Pavilion Gaming Laptop 15-ec2xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-23-generic root=UUID=b46be3e7-1b67-4d08-af06-a62ab919461b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.17.0-23.23~24.04.1-generic 6.17.13 RelatedPackageVersions: linux-restricted-modules-6.17.0-23-generic N/A linux-backports-modules-6.17.0-23-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 Tags: noble Uname: Linux 6.17.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/23/2025 dmi.bios.release: 15.30 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88DE dmi.board.vendor: HP dmi.board.version: 96.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.34 dmi.modalias: dmi:bvnAMI:bvrF.30:bd04/23/2025:br15.30:efr96.34:svnHP:pnHPPavilionGamingLaptop15-ec2xxx:pvr:rvnHP:rn88DE:rvr96.34:cvnHP:ct10:cvrChassisVersion:sku471C4PA#ACJ: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec2xxx dmi.product.sku: 471C4PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152259/+subscriptions
[Bug 2143083] Re: [SRU] Duplicated entries in /proc//mountinfo
This bug was fixed in the package linux - 6.17.0-29.29 --------------- linux (6.17.0-29.29) questing; urgency=medium * questing/linux: 6.17.0-29.29 -proposed tracker (LP: #2151099) * CVE-2026-31419 - net: bonding: fix use-after-free in bond_xmit_broadcast() * CVE-2026-31431 - crypto: algif_aead - Revert to operating out-of-place - crypto: algif_aead - snapshot IV for async AEAD requests - crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption - crypto: authencesn - Fix src offset when decrypting in-place - crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl - crypto: algif_aead - Fix minimum RX size check for decryption * CVE-2026-31533 - net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption * CVE-2026-31504 - net: fix fanout UAF in packet_release() via NETDEV_UP race -- Manuel Diewald <manuel.diewald@canonical.com> Tue, 05 May 2026 15:53:32 +0200 ** Changed in: linux (Ubuntu Questing) Status: In Progress => Fix Released ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31419 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31431 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31504 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31533 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2143083 Title: [SRU] Duplicated entries in /proc/<pid>/mountinfo Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux source package in Resolute: Fix Released Bug description: [ Impact ] Sometimes on a system that is mounting and unmounting filesystems frequently, for example running lots of docker containers, the size of /proc/1/mountinfo, can become very large -- 100s, to 1000s of entries or more -- with the vast majority being a single entry duplicated many times. This causes other problems on the system, due to systemd parsing the mount table whenever it changes, and eating up a lot of memory, for example [0]. Waiting long enough there are rare events where the length of mountinfo can go into the millions of lines and lead to OOM and kernel panics. [Fix] Christian Brauner submitted a patch on the mailing list[1] (now merged upstream [2]) which fixes the issue by a) using the unique mount ID as the pos for iterating the mounts b) updating to the pos of the iterator before returning [ Test Plan ] To test whether this issue occurs, it is sufficient to rapidly mount and unmount tmpfs rapidly and poll for duplicates in `/proc/1/mountinfo` this can be done for example by the following pair of scripts: repro.sh -------- #!/bin/bash counter=0 while true; do echo -n "." unique_name="tmpfs_$$_$counter" mkdir -p "/tmp/$unique_name" sudo mount -t tmpfs "$unique_name" "/tmp/$unique_name" sudo umount "/tmp/$unique_name" rmdir "/tmp/$unique_name" ((counter++)) sleep 0.1 done ------- has-bug.sh -------- #!/bin/bash THRESHOLD=100 WAIT_MIN=30 WAIT_SECONDS=$((WAIT_MIN * 60)) SECONDS=0 while ((SECONDS < WAIT_SECONDS)); do # Get mountinfo entries and count total mountinfo="$(cat /proc/1/mountinfo)" mountinfo_count=$(echo "$mountinfo" | wc -l) if ((mountinfo_count > THRESHOLD)); then echo "$(date): Mount count ($mountinfo_count) exceeds threshold ($THRESHOLD)" # Find and log duplicate mount points with their counts duplicates=$(echo "$mountinfo" | sort | uniq -cd) if [[ -n "$duplicates" ]]; then echo "Duplicate mounts :" echo "$duplicates" | while read -r count mountpoint; do echo " $mountpoint: $count occurrences" done fi exit 0 fi sleep 0.1 done exit 1 ------ In my testing, about 5 minutes is sufficient time for the bug to occur, so I've set the timeout to 30min in the test plan out of an abundance of caution. If the bug is present in the running kernel, `has-bug.sh` will print a message about duplicate entries and exit success, otherwise it will time out and exit with return code 1. The high level test plan is: 1. Run `has-bug.sh` and `repro.sh` on unpatched kernel. 2. Observe that bug is present 3. Upgrade to patched kernel and restart 4. Run `has-bug.sh` and `repro.sh` on unpatched kernel. 5. Observe that bug is no longer present [ Where problems could occur ] * The patch to fix this modifies how iterator position is tracked when iterating mounts. It therefore potentially affects anything that iterates through the mounts. [ Other Info ] [0]: https://github.com/systemd/systemd/issues/37939 [1]: https://lore.kernel.org/lkml/20260129-geleckt-treuhand-4bb940acacd9@brauner/ [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a403d7aa9074f527f064ef0806aaab38d14b07c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143083/+subscriptions
[Bug 2148768] Re: Fix internal speaker fail to output left/right only on CS42L45+CS35L57 audio solution
Verified with inux-oem-6.17/6.17.0-1021.21 on new Dell Renegade/Huracan PTL platforms with CirrusLogic audio solution, Go to g-s-d and select sound --> output (speaker) --> Test, and click on "Front Left" and "Front Right". The audio sounds good from the single side channel. ** Tags removed: verification-needed-noble-linux-oem-6.17 ** Tags added: verification-done-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148768 Title: Fix internal speaker fail to output left/right only on CS42L45+CS35L57 audio solution Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid 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] Dell Renegade/Huracan PTL platform with CirrusLogic audio solution CS42L45+CS35L57 only output on both channels but can't output on left/right only. [Fix] Fix the backport commit: ffcd44f1bedb ("ASoC: cs35l56: Support for reading speaker ID from on-chip GPIOs") which may cause the incorrect speaker to be involved. [Test Case] 1. Boot up the machine of new Dell Renegade/Huracan PTL platforms with CirrusLogic audio solution 2. Go to g-s-d and select sound --> output (speaker) --> Test, and click on "Front Left" and "Front Right" 3. Make sure the audio output is from left only and right only [Where problems could occur] It corrects the speaker ID identification for CirrusLogic amplifiers. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2148768/+subscriptions
[Bug 2150065] Re: Fix mic mute led on a HP EliteBook 6 G2a platform
This bug was fixed in the package linux-oem-6.17 - 6.17.0-1023.23 --------------- linux-oem-6.17 (6.17.0-1023.23) noble; urgency=medium * noble/linux-oem-6.17: 6.17.0-1023.23 -proposed tracker (LP: #2151771) [ Ubuntu: 6.17.0-29.29 ] * questing/linux: 6.17.0-29.29 -proposed tracker (LP: #2151099) * CVE-2026-31419 - net: bonding: fix use-after-free in bond_xmit_broadcast() * CVE-2026-31431 - crypto: algif_aead - Revert to operating out-of-place - crypto: algif_aead - snapshot IV for async AEAD requests - crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption - crypto: authencesn - Fix src offset when decrypting in-place - crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl - crypto: algif_aead - Fix minimum RX size check for decryption * CVE-2026-31533 - net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption * CVE-2026-31504 - net: fix fanout UAF in packet_release() via NETDEV_UP race -- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Fri, 08 May 2026 09:55:15 +0800 ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: Fix Committed => Fix Released ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31419 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31431 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31504 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31533 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150065 Title: Fix mic mute led on a HP EliteBook 6 G2a platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [Impact] New HP platform with Realtek ALC236 audio solution fail to toggle the mic-mute led accordingly while the mic-mute function work w/o problem. This SRU includes fix for the particular SSID only (Goat) [Fix] Backport the upstream fix: cb78517e60cf (ALSA: hda/realtek: Add LED fixup for HP EliteBook 6 G2a Laptops") [Test Case] 1. Boot up the machine of new HP platforms Goat 2. Press Fn+F6 for mic mute function 3. Click led lights up/down in according with the mic mute functions. [Where problems could occur] It fixes the quirk for particular SSIDs of the audio solution. No regression expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150065/+subscriptions
[Bug 2147543] Re: Noble update: upstream stable patchset 2026-04-08
This bug was fixed in the package linux - 6.8.0-117.117 --------------- linux (6.8.0-117.117) noble; urgency=medium * noble/linux: 6.8.0-117.117 -proposed tracker (LP: #2151070) * CVE-2026-31419 - net: bonding: fix use-after-free in bond_xmit_broadcast() * CVE-2026-31431 - crypto: scatterwalk - Backport memcpy_sglist() - crypto: algif_aead - use memcpy_sglist() instead of null skcipher - crypto: algif_aead - Revert to operating out-of-place - crypto: algif_aead - snapshot IV for async AEAD requests - crypto: authenc - use memcpy_sglist() instead of null skcipher - crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption - crypto: authencesn - Fix src offset when decrypting in-place - crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl - crypto: algif_aead - Fix minimum RX size check for decryption * CVE-2026-31533 - net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption * CVE-2026-31504 - net: fix fanout UAF in packet_release() via NETDEV_UP race -- Manuel Diewald <manuel.diewald@canonical.com> Tue, 05 May 2026 15:53:02 +0200 ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31419 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31431 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31504 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31533 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147543 Title: Noble update: upstream stable patchset 2026-04-08 Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released 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-04-08 Ported from the following upstream stable releases: v6.6.123, v6.12.69 from git://git.kernel.org/ Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work net/mlx5: Fix memory leak in esw_acl_ingress_lgcy_setup() can: gs_usb: gs_usb_receive_bulk_callback(): fix error message net: bcmasp: fix early exit leak with fixed phy octeon_ep: Fix memory leak in octep_device_setup() bonding: annotate data-races around slave->last_rx net: mvpp2: cls: Fix memory leak in mvpp2_ethtool_cls_rule_ins() ipv6: use the right ifindex when replying to icmpv6 from localhost net: wwan: t7xx: fix potential skb->frags overflow in RX path rocker: fix memory leak in rocker_world_port_post_fini() nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame(). ice: stop counting UDP csum mismatch as rx_errors net/mlx5e: TC, delete flows only for existing peers net/mlx5e: Report rx_discards_phy via rx_dropped net/mlx5e: Account for netdev stats in ndo_get_stats64 nfc: nci: Fix race between rfkill and nci_unregister_device(). net: bridge: fix static key check net/mlx5e: Skip ESN replay window setup for IPsec crypto offload scsi: firewire: sbp-target: Fix overflow in sbp_make_tpg() ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion gpiolib: acpi: use BIT_ULL() for u64 mask in address space handler dma/pool: distinguish between missing and exhausted atomic pools pinctrl: meson: mark the GPIO controller as sleeping riscv: compat: fix COMPAT_UTS_MACHINE definition rust: kbuild: give `--config-path` to `rustfmt` in `.rsi` target ASoC: fsl: imx-card: Do not force slot width to sample width scsi: be2iscsi: Fix a memory leak in beiscsi_boot_get_sinfo() ASoC: amd: yc: Add DMI quirk for Acer TravelMate P216-41-TCO gpio: pca953x: mask interrupts in irq shutdown scsi: qla2xxx: edif: Fix dma_free_coherent() size efivarfs: fix error propagation in efivar_entry_get() mptcp: only reset subflow errors when propagated selftests: mptcp: check no dup close events after error selftests: mptcp: check subflow errors in close events selftests: mptcp: join: fix local endp not being tracked flex_proportions: make fprop_new_period() hardirq safe scripts: generate_rust_analyzer: Add compiler_builtins -> core dep drm/imx/tve: fix probe device leak drm/amdgpu/soc21: fix xclk for APUs drm/amdgpu/gfx10: fix wptr reset in KGQ init drm/amdgpu/gfx11: fix wptr reset in KGQ init mm/kfence: randomize the freelist on initialization arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state arm64/fpsimd: signal: Consistently read FPSIMD context arm64/fpsimd: signal: Fix restoration of SVE context ksmbd: smbd: fix dma_unmap_sg() nents ksmbd: Fix race condition in RPC handle list access wifi: ath11k: add srng->lock for ath11k_hal_srng_* in monitor mode btrfs: prevent use-after-free on page private data in btrfs_subpage_clear_uptodate() net/sched: act_ife: convert comma to semicolon pinctrl: lpass-lpi: implement .get_direction() for the GPIO driver drm/msm/a6xx: fix bogus hwcg register updates perf: sched: Fix perf crash with new is_user_task() helper writeback: fix 100% CPU usage when dirtytime_expire_interval is 0 mptcp: avoid dup SUB_CLOSED events after disconnect drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove ksmbd: fix recursive locking in RPC handle list access bpf/selftests: test_select_reuseport_kern: Remove unused header can: at91_can: Fix memory leak in at91_can_probe() Bluetooth: MGMT: Fix memory leak in set_ssp_complete ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues net: phy: micrel: fix clk warning when removing the driver net/mlx5: fs, Fix inverted cap check in tx flow table root disconnect net/mlx5: Initialize events outside devlink lock net/mlx5: Fix vhca_id access call trace use before alloc bcache: fix improper use of bi_end_io bcache: use bio cloning for detached device requests bcache: fix I/O accounting leak in detached_dev_do_request nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference gpio: rockchip: Stop calling pinctrl for set_direction mm/memory-failure: improve memory failure action_result messages mm/memory-failure: fix redundant updates for already poisoned pages mm/memory-failure: fix missing ->mf_stats count in hugetlb poison mm/memory-failure: teach kill_accessing_process to accept hugetlb tail page pfn gpiolib: acpi: Fix potential out-of-boundary left shift rust: kbuild: support `-Cjump-tables=n` for Rust 1.93.0 pinctrl: qcom: sm8350-lpass-lpi: Merge with SC7280 to fix I2S2 and SWR TX pins UBUNTU: [Config] remove PINCTRL_SM8350_LPASS_LPI UBUNTU: Upstream stable to v6.6.123, v6.12.69 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147543/+subscriptions
[Bug 2152267] [NEW] Dell XPS 9315: rt715-sdca SoundWire bus clash after suspend/resume, persistent across reboots (kernel 7.0.0-14)
Public bug reported: # No audio on Dell XPS 9315 speakers — rt715-sdca SoundWire bus clash on kernel 7.0.0-14 ## Summary No sound from the built-in speakers of a Dell XPS 9315 running Ubuntu 26.04 LTS (kernel 7.0.0-14-generic). Sound works fine on Windows on the same machine, so the hardware is functional. The kernel log shows the `rt715-sdca` SoundWire slave (microphone codec) failing to initialize at boot with a bus clash / parity error, then looping indefinitely with `Slave 6 initialization failed: -61`. Because rt715 fails to attach properly, the shared SoundWire bus stays in a degraded state and the `rt1316-sdca` speaker amplifier (which is otherwise reported as `Attached`) never receives clock/data, leading to ASoC trigger timeouts (`-110`) whenever an audio stream is opened on the Speaker sink. ## Hardware - **Model**: Dell XPS 9315 (Alder Lake-P) - **Audio**: Intel Smart Sound Technology + SoundWire - rt1316-sdca (speaker amplifier, link 2) - rt715-sdca (microphone codec, link 3) - **BIOS**: 1.36.0 (2025-12-24) — latest, no fwupd update available ## Software - **Distro**: Ubuntu 26.04 LTS - **Kernel**: 7.0.0-14-generic (`linux-image-generic-hwe-26.04`) - **firmware-sof-signed**: 2025.12.2-1 - **PipeWire / WirePlumber**: 1.6.2 - **Topology loaded**: `intel/sof-tplg/sof-adl-rt1316-l2-mono-rt714-l3.tplg` - **Firmware**: `intel/sof/sof-adl.ri` — `Firmware ABI 3:22:1`, `Kernel ABI 3:23:1` (mismatch noted in dmesg) ## Symptoms - No sound from built-in speakers in any application - `wpctl status` reports the Speaker sink as default, not muted, volume normal - All relevant ALSA mixer controls (`Speaker Switch`, `rt1316-1 DAC Switch`, `PGA3.0 Master Playback Volume`) are ON / at maximum - PCM state goes to `RUNNING` when audio is played (data is sent to ALSA) but no sound is produced ## Kernel log Key errors at boot (full log attached in `01-dmesg-audio.txt`): ``` rt715-sdca sdw:0:3:025d:0714:01: Bus clash detected before INT mask is enabled rt715-sdca sdw:0:3:025d:0714:01: PARITY error detected before INT mask is enabled rt715-sdca sdw:0:3:025d:0714:01: ASoC error (-5): at snd_soc_component_update_bits() on sdw:0:3:025d:0714:01 for register: [0x40800109] ``` Then an infinite retry loop (5000+ occurrences in a few minutes): ``` rt715-sdca sdw:0:3:025d:0714:01: Slave 6 state check1: UNATTACHED, status was 1 rt715-sdca sdw:0:3:025d:0714:01: SDW_SCP_BUSCLOCK_SCALE_B1 write failed:-61 rt715-sdca sdw:0:3:025d:0714:01: Slave 6 initialization failed: -61 ``` When an application opens the Speaker sink: ``` Speaker: ASoC error (-110): trigger FE cmd: 0 failed sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC error (-110): at soc_component_trigger() on 0000:00:1f.3 sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC error (-110): at snd_soc_pcm_component_hw_free() on 0000:00:1f.3 ``` ## Reproduction 1. Boot Ubuntu 26.04 LTS on Dell XPS 9315 (kernel 7.0.0-14) 2. Observe `sudo dmesg | grep rt715-sdca` — bus clash + UNATTACHED loop from the first second after boot 3. Try to play any audio (browser, `speaker-test`, etc.) — PCM state is `RUNNING` but no sound is produced; ASoC -110 timeout errors appear ## Timeline / first occurrence The bug appeared after a **suspend/resume cycle** on 2026-05-12: - 22:02:53 — system entered s2idle (`PM: suspend entry`) - 22:30:15 — system resumed (`Freezing user space processes` → resume sequence) - 22:30:59 — **first audio error** (43s after resume): ``` rt715-sdca sdw:0:3:025d:0714:01: ASoC error (-16): at soc_component_read_no_lock() on sdw:0:3:025d:0714:01 for register: [0x4080010a] ``` - 22:31:02 — user-triggered reboot due to apparent display freeze / black screen - From this reboot onwards, **every Linux boot** shows the rt715-sdca bus clash + UNATTACHED loop from the first second after the audio stack initializes Audio was working fine under Linux **before** this suspend/resume cycle. The fresh boot at 10:19 (earlier the same day) shows clean SOF init with no rt715-sdca errors. ## Things that do NOT fix the issue - Cold power-off (full shutdown 10s, then power-on) - Reboot - **Reboot into Windows (where audio works) → reboot back into Ubuntu**: audio still broken under Linux, so Windows does not reset the codec to a state that helps Linux re-init - `systemctl --user restart pipewire wireplumber pipewire-pulse` - Forcing volume to 100% and unmuting via `wpctl set-volume / set-mute` - All ALSA mixer controls are already ON and at maximum - BIOS is already at the latest version (1.36.0, 2025-12-24), fwupd reports no updates available - No recent apt upgrades (last apt activity 2026-05-02) — issue persists across many reboots ## Likely diagnosis Since: - Audio works under Windows (so hardware is functional) - Windows → Ubuntu reboot does not fix Linux (so the codec is not in a persistent latched state across OS — or Linux's init sequence re-creates the bad state every time) - Linux audio worked fine until a specific suspend/resume cycle - After that suspend/resume, the bug is reproducible at every Linux boot This looks like a **kernel/driver regression** specific to the `rt715-sdca` init path or the SoundWire bus initialization on this Dell XPS 9315 hardware. The Linux init sequence may now hit a path that the codec or the SDW PHY rejects (possibly related to BIOS 1.36.0 changing some codec/SoundWire init parameter). Windows uses different proprietary init drivers and is unaffected. ## Attempted workaround that failed `sudo modprobe -r snd_soc_rt715_sdca` after stopping PipeWire — fails with `Module is in use` because `snd_soc_sof_sdw` keeps it loaded. ## Attached files - `00-system-info.txt` — distro, kernel, hardware, BIOS, package versions - `01-dmesg-audio.txt` — compacted kernel log (audio-related lines, loop truncated) - `03-pipewire-state.txt` — `wpctl status` and sink inspect - `04-alsa-state.txt` — ALSA card, mixer controls, PCM hw_params - `05-error-summary.txt` — error counters for this boot ## Notes - The topology name references `rt714` but the hardware codec is `rt715`. Both are SDCA-compatible so this matches Linux convention, but worth verifying whether the `rt714-l3` choice is correct for this exact hardware revision. - The ABI mismatch (`FW 3:22:1` vs `Kernel ABI 3:23:1`) is normally backward compatible but may be relevant for this regression. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 12 23:15:31 2026 InstallationDate: Installed on 2026-04-25 (17 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. XPS 9315 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=31da62d7-9d69-4573-9041-4147f1a2652b ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2025 dmi.bios.release: 1.36 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.36.0 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnDellInc.:bvr1.36.0:bd12/24/2025:br1.36:efr1.18:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "audio-bug-report.tar.gz" https://bugs.launchpad.net/bugs/2152267/+attachment/5969947/+files/audio-bug-report.tar.gz -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152267 Title: Dell XPS 9315: rt715-sdca SoundWire bus clash after suspend/resume, persistent across reboots (kernel 7.0.0-14) Status in linux package in Ubuntu: New Bug description: # No audio on Dell XPS 9315 speakers — rt715-sdca SoundWire bus clash on kernel 7.0.0-14 ## Summary No sound from the built-in speakers of a Dell XPS 9315 running Ubuntu 26.04 LTS (kernel 7.0.0-14-generic). Sound works fine on Windows on the same machine, so the hardware is functional. The kernel log shows the `rt715-sdca` SoundWire slave (microphone codec) failing to initialize at boot with a bus clash / parity error, then looping indefinitely with `Slave 6 initialization failed: -61`. Because rt715 fails to attach properly, the shared SoundWire bus stays in a degraded state and the `rt1316-sdca` speaker amplifier (which is otherwise reported as `Attached`) never receives clock/data, leading to ASoC trigger timeouts (`-110`) whenever an audio stream is opened on the Speaker sink. ## Hardware - **Model**: Dell XPS 9315 (Alder Lake-P) - **Audio**: Intel Smart Sound Technology + SoundWire - rt1316-sdca (speaker amplifier, link 2) - rt715-sdca (microphone codec, link 3) - **BIOS**: 1.36.0 (2025-12-24) — latest, no fwupd update available ## Software - **Distro**: Ubuntu 26.04 LTS - **Kernel**: 7.0.0-14-generic (`linux-image-generic-hwe-26.04`) - **firmware-sof-signed**: 2025.12.2-1 - **PipeWire / WirePlumber**: 1.6.2 - **Topology loaded**: `intel/sof-tplg/sof-adl-rt1316-l2-mono-rt714-l3.tplg` - **Firmware**: `intel/sof/sof-adl.ri` — `Firmware ABI 3:22:1`, `Kernel ABI 3:23:1` (mismatch noted in dmesg) ## Symptoms - No sound from built-in speakers in any application - `wpctl status` reports the Speaker sink as default, not muted, volume normal - All relevant ALSA mixer controls (`Speaker Switch`, `rt1316-1 DAC Switch`, `PGA3.0 Master Playback Volume`) are ON / at maximum - PCM state goes to `RUNNING` when audio is played (data is sent to ALSA) but no sound is produced ## Kernel log Key errors at boot (full log attached in `01-dmesg-audio.txt`): ``` rt715-sdca sdw:0:3:025d:0714:01: Bus clash detected before INT mask is enabled rt715-sdca sdw:0:3:025d:0714:01: PARITY error detected before INT mask is enabled rt715-sdca sdw:0:3:025d:0714:01: ASoC error (-5): at snd_soc_component_update_bits() on sdw:0:3:025d:0714:01 for register: [0x40800109] ``` Then an infinite retry loop (5000+ occurrences in a few minutes): ``` rt715-sdca sdw:0:3:025d:0714:01: Slave 6 state check1: UNATTACHED, status was 1 rt715-sdca sdw:0:3:025d:0714:01: SDW_SCP_BUSCLOCK_SCALE_B1 write failed:-61 rt715-sdca sdw:0:3:025d:0714:01: Slave 6 initialization failed: -61 ``` When an application opens the Speaker sink: ``` Speaker: ASoC error (-110): trigger FE cmd: 0 failed sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC error (-110): at soc_component_trigger() on 0000:00:1f.3 sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC error (-110): at snd_soc_pcm_component_hw_free() on 0000:00:1f.3 ``` ## Reproduction 1. Boot Ubuntu 26.04 LTS on Dell XPS 9315 (kernel 7.0.0-14) 2. Observe `sudo dmesg | grep rt715-sdca` — bus clash + UNATTACHED loop from the first second after boot 3. Try to play any audio (browser, `speaker-test`, etc.) — PCM state is `RUNNING` but no sound is produced; ASoC -110 timeout errors appear ## Timeline / first occurrence The bug appeared after a **suspend/resume cycle** on 2026-05-12: - 22:02:53 — system entered s2idle (`PM: suspend entry`) - 22:30:15 — system resumed (`Freezing user space processes` → resume sequence) - 22:30:59 — **first audio error** (43s after resume): ``` rt715-sdca sdw:0:3:025d:0714:01: ASoC error (-16): at soc_component_read_no_lock() on sdw:0:3:025d:0714:01 for register: [0x4080010a] ``` - 22:31:02 — user-triggered reboot due to apparent display freeze / black screen - From this reboot onwards, **every Linux boot** shows the rt715-sdca bus clash + UNATTACHED loop from the first second after the audio stack initializes Audio was working fine under Linux **before** this suspend/resume cycle. The fresh boot at 10:19 (earlier the same day) shows clean SOF init with no rt715-sdca errors. ## Things that do NOT fix the issue - Cold power-off (full shutdown 10s, then power-on) - Reboot - **Reboot into Windows (where audio works) → reboot back into Ubuntu**: audio still broken under Linux, so Windows does not reset the codec to a state that helps Linux re-init - `systemctl --user restart pipewire wireplumber pipewire-pulse` - Forcing volume to 100% and unmuting via `wpctl set-volume / set-mute` - All ALSA mixer controls are already ON and at maximum - BIOS is already at the latest version (1.36.0, 2025-12-24), fwupd reports no updates available - No recent apt upgrades (last apt activity 2026-05-02) — issue persists across many reboots ## Likely diagnosis Since: - Audio works under Windows (so hardware is functional) - Windows → Ubuntu reboot does not fix Linux (so the codec is not in a persistent latched state across OS — or Linux's init sequence re-creates the bad state every time) - Linux audio worked fine until a specific suspend/resume cycle - After that suspend/resume, the bug is reproducible at every Linux boot This looks like a **kernel/driver regression** specific to the `rt715-sdca` init path or the SoundWire bus initialization on this Dell XPS 9315 hardware. The Linux init sequence may now hit a path that the codec or the SDW PHY rejects (possibly related to BIOS 1.36.0 changing some codec/SoundWire init parameter). Windows uses different proprietary init drivers and is unaffected. ## Attempted workaround that failed `sudo modprobe -r snd_soc_rt715_sdca` after stopping PipeWire — fails with `Module is in use` because `snd_soc_sof_sdw` keeps it loaded. ## Attached files - `00-system-info.txt` — distro, kernel, hardware, BIOS, package versions - `01-dmesg-audio.txt` — compacted kernel log (audio-related lines, loop truncated) - `03-pipewire-state.txt` — `wpctl status` and sink inspect - `04-alsa-state.txt` — ALSA card, mixer controls, PCM hw_params - `05-error-summary.txt` — error counters for this boot ## Notes - The topology name references `rt714` but the hardware codec is `rt715`. Both are SDCA-compatible so this matches Linux convention, but worth verifying whether the `rt714-l3` choice is correct for this exact hardware revision. - The ABI mismatch (`FW 3:22:1` vs `Kernel ABI 3:23:1`) is normally backward compatible but may be relevant for this regression. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 12 23:15:31 2026 InstallationDate: Installed on 2026-04-25 (17 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. XPS 9315 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=31da62d7-9d69-4573-9041-4147f1a2652b ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2025 dmi.bios.release: 1.36 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.36.0 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnDellInc.:bvr1.36.0:bd12/24/2025:br1.36:efr1.18:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152267/+subscriptions
[Bug 2152281] Re: net: wwan: t7xx: soft lockup in dpmaif_tx_hw_push_thread during system suspend
Update patch file ** Patch added: "0001-net-wwan-t7xx-fix-race-between-TX-thread-and-system-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152281/+attachment/5970003/+files/0001-net-wwan-t7xx-fix-race-between-TX-thread-and-system-.patch -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152281 Title: net: wwan: t7xx: soft lockup in dpmaif_tx_hw_push_thread during system suspend Status in linux package in Ubuntu: New Bug description: == Summary == A soft lockup (system freeze) occurs in the DPMAIF TX kernel thread when system suspend (s2idle) is triggered while the thread is active. == Environment == Kernel: 6.17.0-1017-oem (Ubuntu OEM) Device: MediaTek MT6880 (FM350-GL) 0000:56:00.0 ASPM: L1 Enabled on endpoint (LnkCtl: ASPM L1 Enabled; ClockPM+) Sleep: s2idle == Reproduction == Trigger: SIM registered + ASPM L1 enabled + repeated suspend/resume (hundreds of cycles) Reproduction script (60s cycle): while true; do systemctl suspend sleep 60 done == Kernel Log == watchdog: BUG: soft lockup - CPU#10 stuck for 26s! [dpmaif_tx_hw_pu:625] RIP: 0010:ktime_get_mono_fast_ns+0x67/0xd0 ... watchdog: BUG: soft lockup - CPU#10 stuck for 52s! [dpmaif_tx_hw_pu:625] RIP: 0010:_raw_spin_unlock_irqrestore+0x3d/0x60 Call Trace: __pm_runtime_resume+0x5b/0x80 t7xx_dpmaif_tx_hw_push_thread+0xc4/0x4e0 [mtk_t7xx] == Root Cause == t7xx_dpmaif_suspend() stops the TX work queue via t7xx_dpmaif_tx_stop() but does NOT signal the TX kthread or update dpmaif_ctrl->state. The kthread can pass the state guard and call pm_runtime_resume_and_get() concurrently with the system PM suspend path, causing a spinlock deadlock. == Fix == See attached patch. Three changes: 1. t7xx_dpmaif_suspend(): set state=PWROFF + wake_up() to signal kthread 2. t7xx_dpmaif_resume(): restore state=PWRON (symmetric) 3. t7xx_dpmaif_tx_hw_push_thread(): add state guard before pm_runtime call == Workaround == Disable ASPM L1 on endpoint: LNKCTL=$(setpci -s 56:00.0 CAP_EXP+10.w) setpci -s 56:00.0 CAP_EXP+10.w=$(printf "%04x" $((16#${LNKCTL} & ~0x2))) (reduces probability but does not fully prevent the race) == Testing == Patched module installed to /lib/modules/.../extra/mtk_t7xx.ko Running suspend/resume loop with SIM registered — no lockup observed (testing in progress, over 4000 cycles completed without regression). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152281/+subscriptions
среда
[Bug 2152163] Re: RX 7900 XTX: dcn32_program_compbuf_size REG_WAIT timeout causes system freeze on kernel 7.0.0-15 (RDNA3)
** Changed in: linux (Ubuntu) Assignee: (unassigned) => ChunAnWu (kiya956) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152163 Title: RX 7900 XTX: dcn32_program_compbuf_size REG_WAIT timeout causes system freeze on kernel 7.0.0-15 (RDNA3) Status in linux package in Ubuntu: New Bug description: ## Summary System freezes with dcn32_program_compbuf_size REG_WAIT timeout on AMD RX 7900 XTX (RDNA3/Navi31) running kernel 7.0.0-15-generic on Ubuntu 26.04. ## Hardware - CPU: AMD Ryzen 9 9950X3D - GPU: Sapphire PULSE RX 7900 XTX (Navi31, rev c8) - RAM: 64GB - Display: HDMI ## Kernel errors observed amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:147 amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:148 workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 11 times ## Steps to reproduce 1. Boot Ubuntu 26.04 with RX 7900 XTX 2. Use GPU-accelerated applications (browser + VS Code + llama.cpp with ROCm) 3. System freezes within minutes to hours 4. REISUB required to recover ## Attempted workarounds (none fully resolved) - amdgpu.dcfeaturemask=0x8 (partial, reduces frequency) - amdgpu.dcdebugmask=0x10 (no effect) - amdgpu.gpu_recovery=1 (recovery attempt fails) ## Additional context - Bug appears related to DCN32 display compression buffer programming - Triggered more frequently under GPU compute load (ROCm/llama.cpp) - Previously reported upstream: https://gitlab.freedesktop.org/drm/amd/-/issues ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon May 11 09:55:17 2026 InstallationDate: Installed on 2026-05-03 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASRock X870E Nova WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=5b6bf59c-b6e2-4ba8-8520-45b350ff8bad ro quiet splash amdgpu.dcfeaturemask=0x8 amdgpu.dcdebugmask=0x10 amdgpu.dc=1 amdgpu.abmlevel=0 acpi_enforce_resources=lax module_blacklist=btusb,bluetooth kho=off amdgpu.gpu_recovery=1 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. RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.20 dmi.board.asset.tag: Default string dmi.board.name: X870E Nova WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.20:bd04/16/2026:br5.41:svnASRock:pnX870ENovaWiFi:pvrDefaultstring:rvnASRock:rnX870ENovaWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: X870E Nova WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152163/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-6.17/6.17.0-1014.14~24.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-6.17 (6.17.0-1014.14~24.04.1) for noble have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/470.256.02-0ubuntu0.24.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/noble/update_excuses.html#linux-restricted-modules-aws-6.17 [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 2149762] Re: Revert "netfilter: conntrack: fix erronous removal of offload bit"
This bug is awaiting verification that the linux-azure/6.8.0-1056.62 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-v2 verification-needed-noble-linux-azure -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149762 Title: Revert "netfilter: conntrack: fix erronous removal of offload bit" Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Committed Bug description: [Impact] With this commit: netfilter: conntrack: fix erronous removal of offload bit We hit the regression on PS6/7, all the nodes with this commit hit soft lockup every 1-2 days and need to reboot the nodes to recover, e.g.: [1022567.831263] watchdog: BUG: soft lockup - CPU#352 stuck for 26s! [kworker/u789:13:1036823] [1022567.831271] Modules linked in: scsi_transport_iscsi mlx5_vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd vhost_net tap xfs act_csum act_pedit act_ct nf_flow_table act_tunnel_key xt_CT xt_tcpudp nft_compat dm_crypt ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat iptable_filter nf_tables veth nf_conntrack_netlink vhost_vsock vmw_vsock_virtio_transport_common vhost vsock nvme_fabrics nvme_keyring act_mirred act_skbedit act_vlan cls_matchall 8021q garp mrp geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink act_gact cls_flower sch_ingress openvswitch nsh nf_conncount nf_nat bridge stp llc bonding sunrpc binfmt_misc intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm irqbypass rapl ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf k10temp ccp ipmi_msghandler mac_hid mlx5_vdpa vringh vhost_iotlb vdpa dm_service_time sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nf_conntrack [1022567.831352] nf_defrag_ipv6 nf_defrag_ipv4 efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 mlx5_ib ib_uverbs macsec ib_core raid10 hid_generic usbhid ses hid enclosure dax_hmem mlx5_core crct10dif_pclmul crc32_pclmul cxl_acpi polyval_clmulni cxl_port mlxfw polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 cxl_core psample nvme mpt3sas ahci raid_class nvme_core tls ast tg3 scsi_transport_sas libahci pci_hyperv_intf nvme_auth i2c_algo_bit xhci_pci xhci_pci_renesas i2c_piix4 aesni_intel crypto_simd cryptd [1022567.831407] CPU: 352 PID: 1036823 Comm: kworker/u789:13 Kdump: loaded Tainted: G L 6.8.0-106-generic #106~22.04.1+hf399032v20260316b0-Ubuntu [1022567.831411] Hardware name: Lenovo ThinkSystem SR665 V3/SB27B75430, BIOS KAE140F-5.70 09/03/2025 [1022567.831413] Workqueue: events_power_efficient nf_flow_offload_work_gc [nf_flow_table] [1022567.831425] RIP: 0010:rhashtable_walk_next+0x17/0xd0 [1022567.831433] Code: 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 48 89 e5 41 57 41 56 41 55 41 54 53 4c 8b 37 48 89 fb 4c 8b 7f 10 <4c> 8b 6f 08 45 0f b6 66 38 41 80 fc 01 0f 87 e4 b1 98 00 41 83 e4 [1022567.831435] RSP: 0018:ff732ea21e2cbda8 EFLAGS: 00000202 [1022567.831438] RAX: ff2b1e3b98ea4058 RBX: ff732ea21e2cbde0 RCX: 0000000000000000 [1022567.831440] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ff732ea21e2cbde0 [1022567.831441] RBP: ff732ea21e2cbdd0 R08: 0000000000000000 R09: 0000000000000000 [1022567.831442] R10: 0000000000000000 R11: 0000000000000000 R12: ff2b1cb8611cbee8 [1022567.831444] R13: ff2b1cb8611cbe40 R14: ff2b1cb8611cbe48 R15: ff2b1e3b98ea4058 [1022567.831445] FS: 0000000000000000(0000) GS:ff2b1fb3bb000000(0000) knlGS:0000000000000000 [1022567.831447] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [1022567.831449] CR2: 0000775a42eee000 CR3: 0000019530ce8003 CR4: 0000000000f71ef0 [1022567.831450] PKRU: 55555554 [1022567.831452] Call Trace: [1022567.831454] <TASK> [1022567.831461] nf_flow_offload_work_gc+0x5a/0xf0 [nf_flow_table] [1022567.831468] process_one_work+0x181/0x3a0 [1022567.831475] worker_thread+0x306/0x440 [1022567.831479] ? __pfx_worker_thread+0x10/0x10 [1022567.831481] kthread+0xef/0x120 [1022567.831485] ? __pfx_kthread+0x10/0x10 [1022567.831487] ret_from_fork+0x44/0x70 [1022567.831492] ? __pfx_kthread+0x10/0x10 [1022567.831494] ret_from_fork_asm+0x1b/0x30 [1022567.831502] </TASK> [1022568.208115] R13: 0000000000000002 R14: 0000000000000002 R15: 0003a1fef9c1d979 [1022568.216666] ? cpuidle_enter_state+0xca/0x720 [1022568.222092] ? tick_nohz_stop_tick+0x70/0x210 [1022568.227521] cpuidle_enter+0x2e/0x50 [1022568.232060] call_cpuidle+0x23/0x60 [1022568.236472] cpuidle_idle_call+0x11d/0x190 [1022568.241562] do_idle+0x87/0xf0 [1022568.245472] cpu_startup_entry+0x2a/0x30 [1022568.250357] start_secondary+0x129/0x160 [1022568.255243] secondary_startup_64_no_verify+0x184/0x18b [1022568.261586] </TASK> [Fix] Without this commit, we spent few weeks to confirm PS6/7 nodes running without any lockup. This commit is a follow-up fix for: netfilter: conntrack: rework offload nf_conn timeout extension logic But the call path and logic starting from flow_offload_fixup_ct changed between these 2 commits. Only manually backport this commit without all the changes in the middle causes issue, and the commit message also says what it fixes is harmless. [Test Plan] We have run a test kernel without this commit on PS6/7 for almost 2 weeks without hitting any soft lockup. [Where problems could occur] The commit we revert, its commit message says what it fixes is harmless, and we have already run the kernel without it for almost 2 weeks without any issue, the risk is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149762/+subscriptions
[Bug 2152259] [NEW] RTL8852AE (PCIe WiFi + USB BT combo) Bluetooth Failure
Public bug reported: Hardware: HP Pavilion Gaming 15-ec2xxx Chip: RTL8852AE (PCIe WiFi + USB BT combo) Symptom: hci0: RTL: Read reg16 failed (-110) crash loop triggered by BT connection attempt Kernel: 6.17.0-23-generic ** 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/2152259 Title: RTL8852AE (PCIe WiFi + USB BT combo) Bluetooth Failure Status in linux package in Ubuntu: New Bug description: Hardware: HP Pavilion Gaming 15-ec2xxx Chip: RTL8852AE (PCIe WiFi + USB BT combo) Symptom: hci0: RTL: Read reg16 failed (-110) crash loop triggered by BT connection attempt Kernel: 6.17.0-23-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152259/+subscriptions