Affects me too. This is a third independent reporter, on a different setup (client/LAC only, xl2tpd in Docker). == Environment == Ubuntu 24.04.4 LTS, x86_64, HP EliteDesk 800 G1 USDT (BIOS L01 v02.57) Kernel-mode L2TP (l2tp_ppp), L2TP over IPsec transport, ESP in UDP 4500, behind NAT. Client only (one [lac], redial=yes). It runs in a privileged Debian bookworm container: xl2tpd 1.3.18-1, ppp 2.4.9-1+1.1+b1, strongswan-charon 5.9.8-5+deb12u5. Last good: 6.8.0-142.142. It ran for 15 days with zero l2tp warnings. == What happened == The host auto-rebooted into 6.8.0-146 at 02:00. The first splat came about 9 minutes later, on the first tunnel bring-up after a container restart. It was followed by a page fault in an unrelated process (ffmpeg, memset_orig), then pppol2tp_xmit warnings, then hard resets. Several boots died within about 6 minutes. refcount_t: addition on 0; use-after-free. WARNING: CPU: 0 PID: 10 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x150 Workqueue: events xfrm_trans_reinject l2tp_tunnel_get_session+0xc8/0xd0 [l2tp_core] l2tp_udp_recv_core+0xb1/0x350 [l2tp_core] l2tp_udp_encap_recv+0x2c/0x54 [l2tp_core] ... xfrm4_rcv_encap_finish2+0x3c/0x60 xfrm_trans_reinject+0xe5/0x170 refcount_t: underflow; use-after-free. (l2tp_session_dec_refcount+0xbb <- l2tp_udp_recv_core+0x103) refcount_t: saturated; leaking memory. BUG: unable to handle page fault ... RIP: memset_orig+0x98/0xb0 (Comm: ffmpeg) WARNING: ... at net/l2tp/l2tp_ppp.c:166 pppol2tp_xmit+0x1e1/0x220 [l2tp_ppp] (Comm: pppd, tailscaled) == Module evidence == The srcversions match the original report: l2tp_ppp 142: 410F7BD8BFBF7AF73E5803E 146: 5FE6350B4BF3E0647293B12 l2tp_core 142 = 146: D5976517E8DDA0096C46F58 Call relocations inside pppol2tp_ioctl (objdump -dr l2tp_ppp.ko): 6.8.0-142: l2tp_session_dec_refcount x2, no sock refcount ops 6.8.0-146: l2tp_session_dec_refcount x3, plus two "lock xadd 0x80(%rbx)" (sk->sk_refcnt) and sk_free Upstream a213a8950414 ("l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl()") relies on the newer pppol2tp_sock_to_session(), which takes a SESSION reference that l2tp_session_put() then releases. In 6.8, pppol2tp_sock_to_session() takes a SOCKET reference (sock_hold(sk)) and returns sk_user_data with no session reference. The 146 backport seems to map the final l2tp_session_put() to l2tp_session_dec_refcount(). If so, each L2TP ioctl drops a session reference it never took, and also leaks a socket reference. That matches the underflow and the "addition on 0" in l2tp_tunnel_get_session on the RX path. I have not seen the backport source (git.launchpad.net returned 403 to me), so this is inferred from the binary. == Workaround == I blocked the modules with "install l2tp_core /bin/false" (plus l2tp_ppp and l2tp_netlink) in /etc/modprobe.d. xl2tpd then falls back to userspace pppd. The host has been stable since then (24h+, no warnings). Booting 6.8.0-142 should also work. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169477 Title: [regression] 6.8.0-146: l2tp/pppol2tp use-after-free -> kernel panic / soft lockup (L2TP/IPsec, xl2tpd) Status in linux package in Ubuntu: Confirmed Bug description: Package: linux (Ubuntu Noble) Affected: linux-image-6.8.0-146-generic 6.8.0-146.146 Last good: 6.8.0-142.142 (also 6.8.0-139.139) == Summary == After upgrading from 6.8.0-142 to 6.8.0-146, a host acting as an L2TP/IPsec server (LNS) and client (LAC) at the same time crashes within 1-10 minutes of boot: kernel panic ("Fatal exception in interrupt") or a permanent soft lockup. 11 crashes in ~2 hours, all on 6.8.0-146, all inside l2tp_core/l2tp_ppp. Booting back into 6.8.0-142 fixes it completely (no warnings at all since). Among the l2tp modules, only l2tp_ppp.ko changed between 142 and 146: l2tp_core srcversion: D5976517E8DDA0096C46F58 (139, 142, 146 - identical) l2tp_ppp srcversion: 410F7BD8BFBF7AF73E5803E (139, 142) 5FE6350B4BF3E0647293B12 (146) Suspected commit (146 changelog, LP: #2164796, CVE-2026-53262): "l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl()" All failures are refcount errors on the L2TP session object and the faults that follow from them, which suggests an unbalanced session reference in the backport. == Environment == Ubuntu 24.04.5 LTS, x86_64 Hardware: YF ADLNN01 (Intel N150), BIOS 5.27 12/17/2025, 4x Intel I226-V (igc) xl2tpd 1.3.18-1build2, ppp 2.4.9-1+1.1ubuntu4, strongswan 5.9.13-2ubuntu4.24.04.5 Kernel-mode L2TP (l2tp_ppp), L2TP over IPsec transport (ESP in UDP 4500), xl2tpd configured with one [lns default] (several clients) plus one [lac] with redial=yes, redial timeout=30. == Reproduction == 1. Boot 6.8.0-146 with xl2tpd (LNS + LAC) over strongswan IPsec. 2. Let 2-3 L2TP tunnels come up; reconnects / session teardown happen. 3. Within 1-10 minutes: refcount warnings, then panic or soft lockup. Not reproducible on 6.8.0-142 (4 boots, hours of uptime, zero warnings). == Crash signatures (6.8.0-146) == 1) refcount UAF on RX path (first symptom on every bad boot) refcount_t: addition on 0; use-after-free. WARNING: CPU: 1 PID: 42 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x150 Workqueue: events xfrm_trans_reinject l2tp_tunnel_get_session+0xc8/0xd0 [l2tp_core] l2tp_udp_recv_core+0xb1/0x350 [l2tp_core] l2tp_udp_encap_recv+0x2c/0x54 [l2tp_core] udp_queue_rcv_one_skb / __udp4_lib_rcv / udp_rcv followed by: refcount_t: underflow; use-after-free. (l2tp_session_dec_refcount+0xbb <- l2tp_udp_recv_core+0x103) refcount_t: saturated; leaking memory. 2) NULL pointer dereference on TX path -> panic BUG: kernel NULL pointer dereference, address: 000000000000002d CPU: 2 PID: 2608 Comm: pppd Tainted: G W 6.8.0-146-generic #146-Ubuntu xfrm_dst_check+0x24/0x40 __sk_dst_check+0x8f/0xa0 __ip_queue_xmit+0x2a0/0x510 l2tp_xmit_core.constprop.0+0x225/0x460 [l2tp_core] l2tp_xmit_skb+0x30/0xa0 [l2tp_core] pppol2tp_xmit+0x114/0x220 [l2tp_ppp] Kernel panic - not syncing: Fatal exception in interrupt (other instances: RIP _raw_spin_lock+0x13 / pppol2tp_xmit+0x1e1) 3) Soft lockup in tunnel deletion (host hangs, no auto-reboot) watchdog: BUG: soft lockup - CPU#1 stuck for 26s..130s! [kworker/u8:3:176] Workqueue: l2tp l2tp_tunnel_del_work [l2tp_core] RIP: _raw_spin_lock_bh+0x1b / l2tp_tunnel_del_work+0x98 l2tp_tunnel_del_work+0x8d/0x1b0 [l2tp_core] process_one_work / worker_thread / kthread preceded by a warning in pppol2tp_release+0x153 [l2tp_ppp] (sock close path). Some dumps also show faults in __mptcp_close_ssk / tcp_release_cb_override / xfrm_bundle_ok after the l2tp refcount warnings. These are most likely secondary memory corruption. == Boot statistics == 6.8.0-139: 16 days uptime, no issues 6.8.0-146: 13 boots in 2h, 11 pstore crash dumps (all l2tp), boots in between ended in hard hangs 6.8.0-142: 4 boots, 0 refcount warnings, 0 soft lockups, 0 l2tp traces == Attachments == pstore/*.txt - EFI pstore dumps (systemd-pstore). Inside each file the parts are in reverse order (PartN first). IPv4/MAC addresses redacted. == Workaround == Pin 6.8.0-142 in GRUB and hold linux-image-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169477/+subscriptions
воскресенье
[Bug 2170296] Re: DisplayLink monitor remains black after kernel upgrade because EVDI module package is not installed
Hi, Thanks for filing a bug report. In Resolute a lot of DKMS modules were made available to users through linux-modules-* packages. This saves time and reduces the risk of DKMS breakage. Since evdi-dkms isn't installed by default on noble the linux-modules-* version is not installed by default either. That being said, the evdi-dkms package still exists on resolute, so I'm unsure why your DKMS module wasn't carried over. Do you remember how your evdi module was initially installed? The module version you installed is listed as 1.14.11 but the latest version in the noble package archive is 1.14.2 (plus Ubuntu patches). A theory - if this dkms module was installed by a third party installer (e.g. a manufacturer's .run file) then it's possible that no Ubuntu package was installed through apt and was just loaded directly as a kernel module. It would dynamically build against each new 6.8 kernel release, but when it came to a big version-breaking upgrade like 6.8 -> 7.0 the module didn't get any updates for building against 7.0. Then, when the dkms module tried to build against the 7.0 kernel it failed. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170296 Title: DisplayLink monitor remains black after kernel upgrade because EVDI module package is not installed Status in linux package in Ubuntu: New Bug description: Title: DisplayLink monitor remains black after kernel upgrade because EVDI module package is not installed Package: linux-generic or the relevant Ubuntu kernel packaging component (maintainers can redirect if necessary) Description: Summary After upgrading to Ubuntu kernel 7.0.0-38-generic, my third monitor connected through a DisplayLink USB graphics adapter stopped working. The adapter was detected by USB, but the monitor remained black because the EVDI kernel module was not available for the running kernel. Installing linux-modules-evdi-generic resolved the problem. I am reporting this because it may indicate an opportunity to improve Ubuntu's kernel packaging, DisplayLink integration, or documentation for users who rely on EVDI. System information Ubuntu release: Ubuntu Resolute (26.04) Working kernel before the issue: 6.8.0-142-generic Affected kernel: 7.0.0-38-generic EVDI package: evdi 1.14.11-160 DisplayLink adapter: HP Dual Output USB Graphic Adapter USB vendor/product ID: 17e9:431a Third monitor: DLOGIC Ltd., 1366×768, VGA The adapter is connected through USB, with its DVI output converted to VGA. Steps to reproduce Use a DisplayLink USB graphics adapter with a monitor connected. Boot into kernel 6.8.0-142-generic, where EVDI is installed. All three monitors work. Boot into kernel 7.0.0-38-generic. Observe that the DisplayLink monitor remains black. Observed behavior The DisplayLink USB device is detected correctly. However, EVDI is unavailable for the running kernel. Before installing the fix, dkms status showed: evdi/1.14.11, 6.8.0-142-generic, x86_64: installed There was no EVDI entry for kernel 7.0.0-38-generic. Running: modinfo evdi returned: modinfo: ERROR: Module evdi not found. Similarly: lsmod | grep evdi returned no output. The package information showed that linux-modules-evdi-generic was available but not installed: linux-modules-evdi-generic: Installed: (none) Candidate: 7.0.0-38.38 The standard linux-generic metapackage depends on linux-image-generic and linux-headers-generic, but does not list linux-modules-evdi- generic as a dependency or recommendation. Workaround I installed the missing package: sudo apt update sudo apt install linux-modules-evdi-generic After rebooting, the EVDI module was available and loaded: evdi 94208 3 modinfo evdi then showed: filename: /lib/modules/7.0.0-38-generic/ubuntu/dkms/evdi/evdi.ko.zst vermagic: 7.0.0-38-generic SMP preempt mod_unload modversions The command: xrandr --listmonitors then detected all three monitors, including the DisplayLink monitor at its native resolution: Monitors: 3 0: +HDMI-1 2048/700x1152/390+1366+0 HDMI-1 1: +eDP-1 1920/380x1080/210+3414+72 eDP-1 2: +DVI-I-1 1366/361x768/203+0+384 DVI-I-1 The monitor now works correctly on kernel 7.0.0-38-generic. Expected behavior For users with supported DisplayLink hardware, I would expect Ubuntu to provide clear guidance about the additional EVDI package required for DisplayLink monitors, particularly when upgrading to a new kernel. If EVDI is intentionally optional and should not be installed automatically, documenting the requirement or making the installation process clearer could prevent users from mistaking a missing module for a kernel or hardware failure. Request Could the Ubuntu maintainers clarify whether the separate installation of linux-modules-evdi-generic is intentional? If so, could the documentation or user guidance be improved to make this requirement clear? If automatic installation is intended for supported DisplayLink configurations, could the relevant packaging dependencies or recommendations be reviewed? Thank you. Version: $ cat /proc/version_signature Ubuntu 7.0.0-38.38-generic 7.0.14 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: matthias 4204 F.... wireplumber /dev/snd/controlC0: matthias 4204 F.... wireplumber /dev/snd/seq: matthias 4186 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 9 09:50:36 2026 InstallationDate: Installed on 2021-01-05 (2103 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwDevWlp3s0Link: Not connected. MachineType: Dell Inc. Inspiron 3793 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=04a3216e-eda8-440c-ae4e-4cc67de7ed4b ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-06 (3 days ago) dmi.bios.date: 03/07/2024 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 0JF2P0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd03/07/2024:br1.30:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0JF2P0:rvrA00:cvnDellInc.:ct10:cvr:sku097A:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 3793 dmi.product.sku: 097A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170296/+subscriptions
[Bug 2167995] Re: HMC error triggers cascading PF resets and tears down RDMA connections
** Description changed: [ Impact ] - A single HMC error triggers cascading PF resets and tears down RDMA connections on the device: - kernel: ice 0000:17:00.1 irdma1: HMC Error - kernel: ice 0000:17:00.1 irdma1: Requesting a reset - kernel: DMAR: DRHD: handling fault status reg 2 - kernel: DMAR: [DMA Read NO_PASID] Request device [17:00.1] fault addr 0xfddce000 [fault reason 0x06] PTE Read access is not set - kernel: bond1: (slave enp23s0f1np1): link status definitely down, disabling slave - kernel: bond1: active interface up! - kernel: ice 0000:17:00.1: PTP reset successful - ice 0000:17:00.1: VSI rebuilt. VSI index 0, type ICE_VSI_PF - ice 0000:17:00.1: VSI rebuilt. VSI index 1, type ICE_VSI_CTRL - bond1: (slave enp23s0f1np1): link status definitely up, 25000 Mbps full duplex - - This causes a short network outage on intel ice NIC, but not i40e which already has a fix. - upstream commit: - https://github.com/torvalds/linux/commit/4dc9c884c0aafac1e8d37536d88d485135e26883 - applys the same fix to ice. + A single HMC error triggers cascading PF resets and tears down RDMA connections on the device: + kernel: ice 0000:17:00.1 irdma1: HMC Error + kernel: ice 0000:17:00.1 irdma1: Requesting a reset + kernel: DMAR: DRHD: handling fault status reg 2 + kernel: DMAR: [DMA Read NO_PASID] Request device [17:00.1] fault addr 0xfddce000 [fault reason 0x06] PTE Read access is not set + kernel: bond1: (slave enp23s0f1np1): link status definitely down, disabling slave + kernel: bond1: active interface up! + kernel: ice 0000:17:00.1: PTP reset successful + ice 0000:17:00.1: VSI rebuilt. VSI index 0, type ICE_VSI_PF + ice 0000:17:00.1: VSI rebuilt. VSI index 1, type ICE_VSI_CTRL + bond1: (slave enp23s0f1np1): link status definitely up, 25000 Mbps full duplex + + This causes a short network outage on intel ice NIC, but not i40e which + already has a fix. + + [ Fix ] + upstream commit: + https://github.com/torvalds/linux/commit/4dc9c884c0aafac1e8d37536d88d485135e26883 + applies the same fix to ice. [ Test Plan ] - Make sure machine with intel ice works fine by running basic network traffic test - and then reproduce the issue in a lab environment. - Confirm the issue can not be reproduced with the above commit. + Make sure machine with intel ice works fine by running basic network traffic test + and then reproduce the issue in a lab environment. + Confirm the issue can not be reproduced with the above commit. [ Where problems could occur ] - The same fix has been applied to intel i40e, the commit does the same thing. - If something goes wrong in the path, and PF is not reset, it may hit the same network outage when using intel ice + The same fix has been applied to intel i40e, the commit does the same thing. + If something goes wrong in the path, and PF is not reset, it may hit the same network outage when using intel ice -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167995 Title: HMC error triggers cascading PF resets and tears down RDMA connections Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Resolute: In Progress Bug description: [ Impact ] A single HMC error triggers cascading PF resets and tears down RDMA connections on the device: kernel: ice 0000:17:00.1 irdma1: HMC Error kernel: ice 0000:17:00.1 irdma1: Requesting a reset kernel: DMAR: DRHD: handling fault status reg 2 kernel: DMAR: [DMA Read NO_PASID] Request device [17:00.1] fault addr 0xfddce000 [fault reason 0x06] PTE Read access is not set kernel: bond1: (slave enp23s0f1np1): link status definitely down, disabling slave kernel: bond1: active interface up! kernel: ice 0000:17:00.1: PTP reset successful ice 0000:17:00.1: VSI rebuilt. VSI index 0, type ICE_VSI_PF ice 0000:17:00.1: VSI rebuilt. VSI index 1, type ICE_VSI_CTRL bond1: (slave enp23s0f1np1): link status definitely up, 25000 Mbps full duplex This causes a short network outage on intel ice NIC, but not i40e which already has a fix. [ Fix ] upstream commit: https://github.com/torvalds/linux/commit/4dc9c884c0aafac1e8d37536d88d485135e26883 applies the same fix to ice. [ Test Plan ] Make sure machine with intel ice works fine by running basic network traffic test and then reproduce the issue in a lab environment. Confirm the issue can not be reproduced with the above commit. [ Where problems could occur ] The same fix has been applied to intel i40e, the commit does the same thing. If something goes wrong in the path, and PF is not reset, it may hit the same network outage when using intel ice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167995/+subscriptions
[Bug 2170506] Re: Problemas de conexão Wifi/Bluetooth
** 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/2170506 Title: Problemas de conexão Wifi/Bluetooth Status in linux package in Ubuntu: New Bug description: # Falha de Wi-Fi e Bluetooth Realtek no Ubuntu 26.04.1 — Kernel 7.0.0-38 **Sistema e hardware:** - Notebook: Lenovo K14 Gen 1 (21CUS0FB00) - Processador: AMD Ryzen 5 5600U - Sistema: Ubuntu 26.04.1 LTS - Kernel: 7.0.0-38-generic - Wi-Fi: Realtek RTL8852BE (driver `rtw89_8852be`) - Bluetooth: Realtek USB (ID `0bda:4853`) - Headset: Baseus Bass BH1 NC - Rede Wi-Fi: Matrix_5.0 (5 GHz) ## Descrição do problema Ao conectar e utilizar o headset Bluetooth Baseus Bass BH1 NC, o Wi-Fi do notebook apresenta falhas graves de comunicação, chegando a perder completamente a conectividade. O problema ocorre mesmo conectado a uma rede Wi-Fi de 5 GHz. Durante um teste monitorado em 11/10/2026, foi registrada a seguinte sequência: - **18:13:43,955:** dispositivo Bluetooth desapareceu do barramento USB. - **18:13:45,766:** começaram os erros no subsistema Wi-Fi. - A interface Wi-Fi permaneceu aparentemente associada ao ponto de acesso, mas perdeu a comunicação com o gateway. - O monitoramento registrou três falhas consecutivas de ping. - A conexão foi restabelecida após reinicializar o Ubuntu. ## Erros identificados nos logs do kernel ``` timed out to flush pci txch failed to remove key from hardware (-5) WARNING: mac80211 ieee80211_restart_work Err: ser L2 re-config timeout ``` ## Testes realizados - Economia de energia do Wi-Fi desativada, sem solucionar o problema. - Monitoramento simultâneo de Bluetooth, Wi-Fi e conectividade. - Verificação dos eventos do kernel e desaparecimento do dispositivo USB Bluetooth. - Reinicialização do sistema, restaurando a conectividade. ## Suspeita técnica Possível falha na interação entre os drivers Realtek `rtw89`, Bluetooth USB, subsistema PCIe/USB e kernel Linux. A sequência temporal sugere uma possível falha de coexistência ou recuperação dos dispositivos, mas a causa ainda não foi confirmada. Pretendo comparar o comportamento com o kernel `7.0.0-34-generic`, preservando o `7.0.0-38-generic`, para investigar uma possível regressão. **Solicitação:** peço que a equipe do Ubuntu investigue a instabilidade dos dispositivos Realtek Bluetooth e Wi-Fi no kernel 7.0.0-38, especialmente os erros de recuperação do driver `rtw89_8852be` após a falha do Bluetooth USB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170506/+subscriptions
[Bug 2170506] [NEW] Problemas de conexão Wifi/Bluetooth
Public bug reported: # Falha de Wi-Fi e Bluetooth Realtek no Ubuntu 26.04.1 — Kernel 7.0.0-38 **Sistema e hardware:** - Notebook: Lenovo K14 Gen 1 (21CUS0FB00) - Processador: AMD Ryzen 5 5600U - Sistema: Ubuntu 26.04.1 LTS - Kernel: 7.0.0-38-generic - Wi-Fi: Realtek RTL8852BE (driver `rtw89_8852be`) - Bluetooth: Realtek USB (ID `0bda:4853`) - Headset: Baseus Bass BH1 NC - Rede Wi-Fi: Matrix_5.0 (5 GHz) ## Descrição do problema Ao conectar e utilizar o headset Bluetooth Baseus Bass BH1 NC, o Wi-Fi do notebook apresenta falhas graves de comunicação, chegando a perder completamente a conectividade. O problema ocorre mesmo conectado a uma rede Wi-Fi de 5 GHz. Durante um teste monitorado em 11/10/2026, foi registrada a seguinte sequência: - **18:13:43,955:** dispositivo Bluetooth desapareceu do barramento USB. - **18:13:45,766:** começaram os erros no subsistema Wi-Fi. - A interface Wi-Fi permaneceu aparentemente associada ao ponto de acesso, mas perdeu a comunicação com o gateway. - O monitoramento registrou três falhas consecutivas de ping. - A conexão foi restabelecida após reinicializar o Ubuntu. ## Erros identificados nos logs do kernel ``` timed out to flush pci txch failed to remove key from hardware (-5) WARNING: mac80211 ieee80211_restart_work Err: ser L2 re-config timeout ``` ## Testes realizados - Economia de energia do Wi-Fi desativada, sem solucionar o problema. - Monitoramento simultâneo de Bluetooth, Wi-Fi e conectividade. - Verificação dos eventos do kernel e desaparecimento do dispositivo USB Bluetooth. - Reinicialização do sistema, restaurando a conectividade. ## Suspeita técnica Possível falha na interação entre os drivers Realtek `rtw89`, Bluetooth USB, subsistema PCIe/USB e kernel Linux. A sequência temporal sugere uma possível falha de coexistência ou recuperação dos dispositivos, mas a causa ainda não foi confirmada. Pretendo comparar o comportamento com o kernel `7.0.0-34-generic`, preservando o `7.0.0-38-generic`, para investigar uma possível regressão. **Solicitação:** peço que a equipe do Ubuntu investigue a instabilidade dos dispositivos Realtek Bluetooth e Wi-Fi no kernel 7.0.0-38, especialmente os erros de recuperação do driver `rtw89_8852be` após a falha do Bluetooth USB. ** 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/2170506 Title: Problemas de conexão Wifi/Bluetooth Status in linux package in Ubuntu: New Bug description: # Falha de Wi-Fi e Bluetooth Realtek no Ubuntu 26.04.1 — Kernel 7.0.0-38 **Sistema e hardware:** - Notebook: Lenovo K14 Gen 1 (21CUS0FB00) - Processador: AMD Ryzen 5 5600U - Sistema: Ubuntu 26.04.1 LTS - Kernel: 7.0.0-38-generic - Wi-Fi: Realtek RTL8852BE (driver `rtw89_8852be`) - Bluetooth: Realtek USB (ID `0bda:4853`) - Headset: Baseus Bass BH1 NC - Rede Wi-Fi: Matrix_5.0 (5 GHz) ## Descrição do problema Ao conectar e utilizar o headset Bluetooth Baseus Bass BH1 NC, o Wi-Fi do notebook apresenta falhas graves de comunicação, chegando a perder completamente a conectividade. O problema ocorre mesmo conectado a uma rede Wi-Fi de 5 GHz. Durante um teste monitorado em 11/10/2026, foi registrada a seguinte sequência: - **18:13:43,955:** dispositivo Bluetooth desapareceu do barramento USB. - **18:13:45,766:** começaram os erros no subsistema Wi-Fi. - A interface Wi-Fi permaneceu aparentemente associada ao ponto de acesso, mas perdeu a comunicação com o gateway. - O monitoramento registrou três falhas consecutivas de ping. - A conexão foi restabelecida após reinicializar o Ubuntu. ## Erros identificados nos logs do kernel ``` timed out to flush pci txch failed to remove key from hardware (-5) WARNING: mac80211 ieee80211_restart_work Err: ser L2 re-config timeout ``` ## Testes realizados - Economia de energia do Wi-Fi desativada, sem solucionar o problema. - Monitoramento simultâneo de Bluetooth, Wi-Fi e conectividade. - Verificação dos eventos do kernel e desaparecimento do dispositivo USB Bluetooth. - Reinicialização do sistema, restaurando a conectividade. ## Suspeita técnica Possível falha na interação entre os drivers Realtek `rtw89`, Bluetooth USB, subsistema PCIe/USB e kernel Linux. A sequência temporal sugere uma possível falha de coexistência ou recuperação dos dispositivos, mas a causa ainda não foi confirmada. Pretendo comparar o comportamento com o kernel `7.0.0-34-generic`, preservando o `7.0.0-38-generic`, para investigar uma possível regressão. **Solicitação:** peço que a equipe do Ubuntu investigue a instabilidade dos dispositivos Realtek Bluetooth e Wi-Fi no kernel 7.0.0-38, especialmente os erros de recuperação do driver `rtw89_8852be` após a falha do Bluetooth USB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170506/+subscriptions
[Bug 2169181] Re: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060
I just installed the test kernel, and I don't see any obvious artifacting using my usual methods. It was pretty easy to reproduce before, so it's looking promising. I'll keep this kernel installed for a few days and see if any problems happen though. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169181 Title: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing intermittent pixel corruption and flickering artifacts in the background/desktop UI after updating to kernel version 7.0.0-38. Behavior: Random pixels/artifacts briefly flicker in the background from time to time. This issue was NOT present in kernel 7.0.0-34. The issue started immediately after updating to kernel 7.0.0-38. CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz GPU: AMD Radeon RX 9060 XT 16 GB[Discrete] P.S. I was planning to upgrade to the 26.10 beta this weekend, but I will stay on Resolute to help resolve this issue with any testing you might need. Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 18:29:50 2026 InstallationDate: Installed on 2026-08-31 (31 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=1bdfa414-371c-4c93-9288-8cdc845cb610 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: 02/25/2026 dmi.bios.release: 38.41 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3841 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3841:bd02/25/2026:br38.41:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181/+subscriptions
суббота
[Bug 2170475] [NEW] Closing the lid resulted in a dead-lock
Public bug reported: After closing the lid of the Laptop (HP Elitebook 840) the system did hang partly. After opening again, the Kubuntu/KDE Ui did work, but some commands in the shell like "sudo" stopped working. Trying to restart the either through the shell or the menu did not work. BIOS is up-to-date. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mitosch 2055 F.... pipewire mitosch 2059 F.... wireplumber /dev/snd/pcmC0D0p: mitosch 2055 F...m pipewire /dev/snd/seq: mitosch 2055 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 11 08:15:59 2026 InstallationDate: Installed on 2026-10-06 (5 days ago) InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) MachineType: HP HP EliteBook 840 14 inch G10 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=f56dacf8-dc22-4b6e-b2a0-b04d7b15d900 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2026 dmi.bios.release: 13.1 dmi.bios.vendor: HP dmi.bios.version: V70 Ver. 01.13.01 dmi.board.name: 8B41 dmi.board.vendor: HP dmi.board.version: KBC Version 51.47.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.71 dmi.modalias: dmi:bvnHP:bvrV70Ver.01.13.01:bd07/08/2026:br13.1:efr81.71:svnHP:pnHPEliteBook84014inchG10NotebookPC:pvrSBKPFV3:rvnHP:rn8B41:rvrKBCVersion51.47.00:cvnHP:ct10:cvr:sku6V5W7AV:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 14 inch G10 Notebook PC dmi.product.sku: 6V5W7AV dmi.product.version: SBKPFV3 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "stack trace of the deadlock causing the hang" https://bugs.launchpad.net/bugs/2170475/+attachment/6008075/+files/ec-deadlock-trace.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170475 Title: Closing the lid resulted in a dead-lock Status in linux package in Ubuntu: New Bug description: After closing the lid of the Laptop (HP Elitebook 840) the system did hang partly. After opening again, the Kubuntu/KDE Ui did work, but some commands in the shell like "sudo" stopped working. Trying to restart the either through the shell or the menu did not work. BIOS is up-to-date. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mitosch 2055 F.... pipewire mitosch 2059 F.... wireplumber /dev/snd/pcmC0D0p: mitosch 2055 F...m pipewire /dev/snd/seq: mitosch 2055 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 11 08:15:59 2026 InstallationDate: Installed on 2026-10-06 (5 days ago) InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) MachineType: HP HP EliteBook 840 14 inch G10 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=f56dacf8-dc22-4b6e-b2a0-b04d7b15d900 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2026 dmi.bios.release: 13.1 dmi.bios.vendor: HP dmi.bios.version: V70 Ver. 01.13.01 dmi.board.name: 8B41 dmi.board.vendor: HP dmi.board.version: KBC Version 51.47.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.71 dmi.modalias: dmi:bvnHP:bvrV70Ver.01.13.01:bd07/08/2026:br13.1:efr81.71:svnHP:pnHPEliteBook84014inchG10NotebookPC:pvrSBKPFV3:rvnHP:rn8B41:rvrKBCVersion51.47.00:cvnHP:ct10:cvr:sku6V5W7AV:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 14 inch G10 Notebook PC dmi.product.sku: 6V5W7AV dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170475/+subscriptions
[Bug 2160416] Re: Unable to connect to 6 GHz networks with MT7921K
apport information ** Tags added: apport-collected stonking ** Description changed: I am unable to use 6ghz WiFi with this chipset in Kubuntu 26.04. Only just noticed it because I upgraded my mesh WiFi at home to ASUS BT8, and my other devices work fine. Running "iw list" shows all 6ghz disabled. I tried forcing Swedish region with "sudo iw reg set SE" but no change. I found a bug report here, not sure if this is the same or not https://bugzilla.kernel.org/show_bug.cgi?id=218731 Happy to provide any additional information needed to help solve this. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jul 11 12:43:37 2026 InstallationDate: Installed on 2023-01-16 (1272 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-27 (106 days ago) 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: B650E PG Riptide 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:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock + --- + ProblemType: Bug + ApportVersion: 2.36.0-0ubuntu1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 26.10 + InstallationDate: Installed on 2023-01-16 (1364 days ago) + InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) + MachineType: ASRock B650E PG Riptide WiFi + Package: linux (not installed) + ProcEnviron: + LANG=sv_SE.UTF-8 + LANGUAGE= + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 amdgpu.lttpr_enable=0 + ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + Tags: stonking + Uname: Linux 7.3.0-9-generic x86_64 + UpgradeStatus: Upgraded to stonking on 2026-10-10 (1 days ago) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 06/02/2026 + dmi.bios.release: 5.41 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: 4.41 + dmi.board.asset.tag: Default string + dmi.board.name: B650E PG Riptide 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.41:bd06/02/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: + dmi.product.family: Default string + dmi.product.name: B650E PG Riptide WiFi + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: ASRock ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2160416/+attachment/6008035/+files/AlsaInfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160416 Title: Unable to connect to 6 GHz networks with MT7921K Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: I am unable to use 6ghz WiFi with this chipset in Kubuntu 26.04. Only just noticed it because I upgraded my mesh WiFi at home to ASUS BT8, and my other devices work fine. Running "iw list" shows all 6ghz disabled. I tried forcing Swedish region with "sudo iw reg set SE" but no change. I found a bug report here, not sure if this is the same or not https://bugzilla.kernel.org/show_bug.cgi?id=218731 Happy to provide any additional information needed to help solve this. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jul 11 12:43:37 2026 InstallationDate: Installed on 2023-01-16 (1272 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-27 (106 days ago) 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: B650E PG Riptide 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:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock --- ProblemType: Bug ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 26.10 InstallationDate: Installed on 2023-01-16 (1364 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi Package: linux (not installed) ProcEnviron: LANG=sv_SE.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 amdgpu.lttpr_enable=0 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: stonking Uname: Linux 7.3.0-9-generic x86_64 UpgradeStatus: Upgraded to stonking on 2026-10-10 (1 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/02/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.41 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide 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.41:bd06/02/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide 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/2160416/+subscriptions
[Bug 2163126] Re: CMI8738 PCI audio device disappears with kernel 6.8.0-137
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (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/2163126 Title: CMI8738 PCI audio device disappears with kernel 6.8.0-137 Status in linux package in Ubuntu: Expired Bug description: I am reporting a possible kernel regression affecting a C-Media CMI8738/CMI8768 PCI audio card in a Dell OptiPlex 9020. With Ubuntu kernel 6.8.0-136-generic, the CMI8738 has remained stable during normal operation. After upgrading to kernel 6.8.0-137-generic, the CMI8738 initially works normally, but after approximately two hours the sound card disappears. When the failure occurs, the device disappears from both: aplay -l and: lspci The PCI device normally appears as: 05:00.0 Multimedia audio controller: C-Media Electronics Inc CMI8738/CMI8768 PCI Audio (rev 10) Because the device disappears from lspci, this appears to be below the PipeWire/ALSA user-space audio stack. Rebooting restores the device. The same hardware and Ubuntu installation remain stable when booted with 6.8.0-136-generic. Expected behavior: The CMI8738 PCI audio device should remain available during normal operation. Actual behavior: The device disappears after approximately two hours when running 6.8.0-137-generic. This appears to be a possible regression between kernel 6.8.0-136-generic and 6.8.0-137-generic. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-136-generic 6.8.0-136.136 ProcVersionSignature: Ubuntu 6.8.0-136.136-generic 6.8.12 Uname: Linux 6.8.0-136-generic x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 9 16:00:32 2026 InstallationDate: Installed on 2024-01-09 (943 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IwConfig: lo no wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9020 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-6.8.0-136-generic root=UUID=4b74565e-7d6f-48f1-80b4-0e0e3fd569ad 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. RelatedPackageVersions: linux-restricted-modules-6.8.0-136-generic N/A linux-backports-modules-6.8.0-136-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.release: 65.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0N4YC8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd12/27/2017:br65.21:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:sku05A4: dmi.product.name: OptiPlex 9020 dmi.product.sku: 05A4 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163126/+subscriptions
[Bug 2169326] Re: Ubuntu 26.10 Concept - Wifi does not work after sleep [Lenovo Yoga Slim 7x]
The workaround I used was a script that reset the wifi hardware when it came out of standby. It might make it take a few seconds longer than a correct fix, but it worked well enough: Create the script: sudo nano /lib/systemd/system-sleep/wifi-unbind.sh Script contents: #!/bin/bash case "$1/$2" in pre/*) # Physically remove the Wi-Fi endpoint from the PCI bus before suspend if [ -d /sys/bus/pci/devices/0004:01:00.0 ]; then echo 1 > /sys/bus/pci/devices/0004:01:00.0/remove sleep 1 fi ;; post/*) # Rescan the PCI bus to rediscover and re-probe the Wi-Fi card echo 1 > /sys/bus/pci/rescan ;; esac It should apply immediately but might have to reboot if wifi is already borked. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169326 Title: Ubuntu 26.10 Concept - Wifi does not work after sleep [Lenovo Yoga Slim 7x] Status in ubuntu-concept: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Stonking: New Bug description: Ubuntu 26.10 Concept - Wifi does not work after sleep [Lenovo Yoga Slim 7x] Issue with Lenovo Yoga Slim 7x - Snapdragon X Elite. This error is reproducable. I did a fresh clean install of Ubuntu Concept 26.10 (Stonking Stingray Development Branch) using the ISO (I updated the installer during the install). The kernel version installed was 7.> After the install: - i close to lid to put the laptop into sleep - wait 30 seoncs to 5 mins - re-open the lid At this point, the wifi never starts up again. It appears active but does not see any networks. Doing a dmesg, i get the following errors: [ 318.682061] ath12k_wifi7_pci 0004:01:00.0: timeout while waiting for restart complete [ 318.682064] ath12k_wifi7_pci 0004:01:00.0: failed to resume core: -110 [ 318.682066] ath12k_wifi7_pci 0004:01:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110 [ 318.682075] ath12k_wifi7_pci 0004:01:00.0: PM: failed to resume async: error -110 [ 318.684876] OOM killer enabled. [ 318.684877] Restarting tasks: Starting [ 318.685569] Restarting tasks: Done [ 318.685586] efivarfs: resyncing variable state [ 318.792619] efivarfs: finished resyncing variable state [ 318.792684] random: crng reseeded on system resumption [ 318.805146] PM: suspend exit [ 318.838513] audit: type=1400 audit(1790960536.665:291): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=15472 comm="(ubuntu-insigh)" requested="userns_create" target="unprivileged_userns" execpath="/usr/lib/systemd/systemd-executor" [ 318.839115] audit: type=1400 audit(1790960536.666:292): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=15472 comm="(ubuntu-insigh)" capability=21 capname="sys_admin" [ 318.881100] audit: type=1400 audit(1790960536.708:293): apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 profile="unprivileged_userns" name="" pid=15505 comm="systemd-detect-" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 321.884027] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 321.884040] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 321.884047] ath12k_wifi7_pci 0004:01:00.0: failed to set ac override for ARP: -11 [ 321.884051] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 [ 324.892068] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 324.892081] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 324.892088] ath12k_wifi7_pci 0004:01:00.0: failed to enable PMF QOS: -11 [ 324.892093] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 [ 337.821974] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 337.821987] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 337.821994] ath12k_wifi7_pci 0004:01:00.0: failed to enable PMF QOS: -11 [ 337.821999] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 [ 350.809887] ath12k_wifi7_pci 0004:01:00.0: wmi command 16387 timeout [ 350.809899] ath12k_wifi7_pci 0004:01:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 350.809906] ath12k_wifi7_pci 0004:01:00.0: failed to enable PMF QOS: -11 [ 350.809910] ath12k_wifi7_pci 0004:01:00.0: fail to start mac operations in pdev idx 0 ret -11 I tried the following to troublesshhot - ran "qcom-firmware-extract" from an updated copy of windows 11 - I tried "systemctl restart NetworkManager" This behavior was not present with my hardware in Ubuntu 26.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-concept/+bug/2169326/+subscriptions
[Bug 2170457] Re: Regression: Intel i915 HDMI flickering and CPU pipe B FIFO underrun with eDP 1368x768 + HDMI 1920x1080@60 after Ubuntu 26.04 upgrade
** 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/2170457 Title: Regression: Intel i915 HDMI flickering and CPU pipe B FIFO underrun with eDP 1368x768 + HDMI 1920x1080@60 after Ubuntu 26.04 upgrade Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 26.04.1 LTS, an external HDMI monitor started flickering when used together with the laptop internal display in a specific display mode combination. Hardware: - Dell Latitude 3400 - Intel UHD Graphics 620 / WhiskeyLake-U GT2 [8086:3ea0] - Kernel driver: i915 - X11 session - Xorg modesetting driver + glamor - Ubuntu 26.04.1 LTS - Current kernel: 7.0.0-38-generic Problematic configuration: - Internal eDP-1: 1368x768 @ 60.05 Hz - External HDMI-1: 1920x1080 @ 60 Hz In this configuration, the external HDMI monitor flickers heavily and the kernel logs: i915 0000:00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun This exact setup worked normally before the Ubuntu 26.04 upgrade. The issue is reproducible with multiple hardware combinations: - Tested with 2 different external monitors - Tested with 3 different HDMI cables - Same behavior Tests performed: 1. eDP-1 1368x768 @60 + HDMI 1920x1080 @60 Result: flickering, CPU pipe B FIFO underrun 2. eDP-1 1368x768 @60 + HDMI 1920x1080 @30 Result: stable 3. eDP-1 disabled + HDMI 1920x1080 @60 Result: stable 4. eDP-1 1920x1080 @60 + HDMI 1920x1080 @60 Result: stable 5. eDP-1 1600x900 @60 + HDMI 1920x1080 @60 Result: stable 6. eDP-1 1280x720 @60 + HDMI 1920x1080 @60 Result: stable Changing the internal display scaling mode from "Full aspect" to "Center" does NOT solve the issue. The problematic internal display mode reported by xrandr is: 1368x768 (72.486 MHz) h: 1368 1416 1448 1528 v: 768 771 781 790 refresh: 60.05 Hz The working 1600x900 mode is: 1600x900 (97.866 MHz) h: 1600 1648 1680 1760 v: 900 903 908 926 refresh: 60.05 Hz Historical kernel logs: - Before the distribution upgrade, kernels 6.8.0-139, 6.8.0-142 and 6.8.0-146 were used. - No CPU pipe FIFO underrun was found in the reviewed historical logs for those kernels. - Ubuntu distribution upgrade occurred on 2026-09-30. - Kernel 7.0.0-34-generic was booted afterwards. - First recorded CPU pipe B FIFO underrun appeared on 2026-10-01 while running 7.0.0-34-generic. - The errors continue with 7.0.0-38-generic. Current workaround: - Internal display: 1600x900 @60 - External HDMI display: 1920x1080 @60 Another workaround: - Internal display: 1368x768 @60 - External HDMI display: 1920x1080 @30 Additional observation: Cinnamon stores the problematic display profile and reapplies HDMI 1920x1080@60 after HDMI hotplug, so disconnecting and reconnecting the monitor makes the flickering return. This appears to be a regression in the Intel i915/DRM display pipeline after the Ubuntu 26.04 upgrade, triggered specifically by the eDP 1368x768 mode while HDMI is active at 1920x1080@60. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: sobreiro 11396 F.... wireplumber /dev/snd/seq: sobreiro 11377 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon Date: Sat Oct 10 16:06:18 2026 InstallationDate: Installed on 2026-03-25 (199 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Latitude 3400 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=f2fc313e-7088-4155-9ae8-ba73e7ae9a15 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-01 (10 days ago) dmi.bios.date: 03/26/2025 dmi.bios.release: 1.38 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.38.0 dmi.board.name: 0XWHC2 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.38.0:bd03/26/2025:br1.38:svnDellInc.:pnLatitude3400:pvr:rvnDellInc.:rn0XWHC2:rvrA05:cvnDellInc.:ct10:cvr:sku08BC:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 3400 dmi.product.sku: 08BC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170457/+subscriptions
[Bug 2169181] Re: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060
I experience the same on my system, RX 7800 XT and Ryzen 5 5600, Ubuntu 26.04 + 1440p + 1080p monitor setup It comes out faster and more frequently when I hog the CPU, for example with stress --cpu 12 and moving some windows or enabling and disabling night light. Doesn't happen on weston or x11 session, however its mostly sure a kernel regression, as I tested the latest mainline 7.2.6 and Ubuntu's 7.0.0.34 and everything is fine here. The only different thing is the following kernel log line at startup when booting on the buggy kernel [ 16.477207] amdgpu 0000:2d:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:148 I also tried my Thinkpad L15 which has an AMD APU Pro 5650u, its still present here but less noticeable even with huge CPU load. Found this on amdgpu drm bugzilla https://gitlab.freedesktop.org/drm/amd/-/work_items/5952 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169181 Title: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing intermittent pixel corruption and flickering artifacts in the background/desktop UI after updating to kernel version 7.0.0-38. Behavior: Random pixels/artifacts briefly flicker in the background from time to time. This issue was NOT present in kernel 7.0.0-34. The issue started immediately after updating to kernel 7.0.0-38. CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz GPU: AMD Radeon RX 9060 XT 16 GB[Discrete] P.S. I was planning to upgrade to the 26.10 beta this weekend, but I will stay on Resolute to help resolve this issue with any testing you might need. Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 18:29:50 2026 InstallationDate: Installed on 2026-08-31 (31 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=1bdfa414-371c-4c93-9288-8cdc845cb610 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: 02/25/2026 dmi.bios.release: 38.41 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3841 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3841:bd02/25/2026:br38.41:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181/+subscriptions
пятница
[Bug 2163642] Re: Kernel panic "Attempted to kill the idle task" on AMD Opteron multi-node NUMA under KVM (6.8.0-137)
Hi Radovan, Yes, the stopper panic is definitely a secondary crash from the KVM oops. Notice the faulting address 0xfffb77e9d05d8b4c in kvm_replace_memslot - bit 50 is flipped from the canonical 0xffff range. Once that vCPU thread oopsed and tainted the kernel with 'D', corrupted structures were left behind. Surviving 6 days after an oops on a 4-node NUMA host is actually impressive, but the scheduler eventually trips over it during migrate_swap. The hpilo IO_PAGE_FAULT at 0xbde0e000 is a side effect - pstore ERST tried to save the oops into ACPI reserved memory and AMD-Vi blocked it. On the journal- no need for gigabytes of userspace noise, but pls attach the snippet from those ~4 minutes before the freeze. Curious if any RCU stalls, soft lockups, or MCEs showed up right before the console went down. As for srv05 and srv07, I'd just let them keep running their soak test. But IMHO, 21 days on srv04 vs 3d and 8d without the params speaks for itself. I'd just keep processor.max_cstate=1 idle=nomwait on prod hosts. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163642 Title: Kernel panic "Attempted to kill the idle task" on AMD Opteron multi- node NUMA under KVM (6.8.0-137) Status in linux package in Ubuntu: Confirmed Bug description: **Title:** Kernel panic "Attempted to kill the idle task" on AMD Opteron 6300 series (multi-node NUMA) under KVM load - linux 6.8.0-137-generic (24.04) **Summary:** On 5 out of 5 identical HP ProLiant DL385p Gen8 servers (AMD Opteron 6386 SE, 4 NUMA nodes each, running as KVM/libvirt hypervisors with multiple guest VMs), kernel panics with "Attempted to kill the idle task!" occurred within roughly 1 to 24 hours after upgrading from Ubuntu 22.04 (kernel 5.15.0-187-generic, stable in production for years) to Ubuntu 24.04 (kernel 6.8.0-137-generic) via do-release- upgrade. Pinning the boot kernel back to 5.15.0-187-generic (via GRUB_DEFAULT) while keeping the 24.04 userspace fully resolved the instability on all affected hosts, with no further crashes since. **Hardware:** - HP ProLiant DL385p Gen8, BIOS A28 (03/14/2018) - AMD Opteron 6386 SE, microcode 0x6000852 - 4 NUMA nodes per host - KVM/libvirt hypervisor, 9-20 guest VMs per host under production load (mixed Kubernetes control-plane/worker nodes, haproxy, monitoring, storage services) **Steps to reproduce:** 1. Fresh `do-release-upgrade` from 22.04 (5.15.0-187-generic) to 24.04 (6.8.0-137-generic) on the described hardware 2. Boot into 6.8.0-137-generic with multiple KVM guests running under moderate-to-high, mixed CPU/memory load 3. Panic occurs non-deterministically, anywhere from ~1 hour to ~24 hours after boot; not tied to any single reproducible user action **Observed panic signature (consistent across all 5 affected hosts):** ``` Kernel panic - not syncing: Attempted to kill the idle task! Call Trace: <TASK> ? multi_cpu_stop+0xa0/0x120 ? __pfx_multi_cpu_stop+0x10/0x10 cpu_stopper_thread+0x9c/0x170 ? __pfx_smpboot_thread_fn+0x10/0x10 smpboot_thread_fn+0xe3/0x1e0 kthread+0xf2/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x47/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> ``` One instance on a related host (same hardware) additionally showed `membarrier_private_expedited+0x1cf/0x2d0` in RIP immediately preceding the panic. **Possible related upstream discussion:** A 2018 LKML thread by Matt Fleming (SUSE), "cpu stopper threads and load balancing leads to deadlock" (https://lkml.iu.edu/hypermail/linux/kernel/1804.2/01642.html), describes a closely matching mechanism: a CPU stopper thread entering idle/active load balancing while, concurrently, NUMA balancing on another CPU attempts to migrate a task via `stop_two_cpus()`, resulting in a deadlock over the stopper lock. Given that our affected hosts are multi-node NUMA systems (4 nodes) and the panic call trace centers on `cpu_stopper_thread`/`multi_cpu_stop`, this looks like a strong candidate mechanism, though we cannot confirm whether it is the same unresolved issue, a regression of a past fix, or a new but related bug in 6.8. **Workaround applied:** GRUB kernel pinning to boot `5.15.0-187-generic` while keeping the 24.04 userspace intact (`GRUB_DEFAULT` set to the jammy kernel's advanced boot entry ID, `update-grub`, reboot). All 5 hosts stable since applying this workaround. **Additional diagnostics performed:** - Hardware (BIOS version, CPU model, microcode) verified identical across all 5 affected hosts - Memtester (4GB sample, full test cycle) passed clean on the two hosts tested - HP Integrated Management Log (IML) reviewed on two hosts: one shows a documented Uncorrectable CPU Machine Check Exception from 2020 (Bank 0x04, both physical processors) - possibly a contributing factor for that specific host, but does not explain the same panic signature occurring on hosts without such MCE history - Network/bonding layers (LACP, active-backup) verified healthy and unrelated to the panics - `dmesg`/`journalctl` EDAC output shows no correctable/uncorrectable memory errors logged around panic times on the hosts checked **Please let me know what additional information (full dmesg, kernel config, /proc/cpuinfo, NUMA topology via `numactl --hardware`, etc.) would help diagnose this further.** --- ProblemType: Bug AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Aug 18 15:57 seq crw-rw---- 1 root audio 116, 33 Aug 18 15:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: 20240524 DistroRelease: Ubuntu 24.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL385p Gen8 Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-137-generic root=UUID=9d93cee9-3b2d-4aff-b422-59c0ba9a1198 ro console=ttyS0,115200n8 console=tty0 vga=normal nomodeset nointremap ProcVersionSignature: Ubuntu 6.8.0-137.137-generic 6.8.12 RelatedPackageVersions: linux-restricted-modules-6.8.0-137-generic N/A linux-backports-modules-6.8.0-137-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image noble Uname: Linux 6.8.0-137-generic x86_64 UpgradeStatus: Upgraded to noble on 2026-08-13 (5 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: HP dmi.bios.version: A28 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.82 dmi.modalias: dmi:bvnHP:bvrA28:bd03/14/2018:efr2.82:svnHP:pnProLiantDL385pGen8:pvr:cvnHP:ct23:cvr:sku653203-B21: dmi.product.family: ProLiant dmi.product.name: ProLiant DL385p Gen8 dmi.product.sku: 653203-B21 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163642/+subscriptions