** 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/2167009 Title: Regression in 6.8.0-139: resume from hibernation hangs (GSC proxy bind timeout); 6.8.0-138 unaffected with identical userspace Status in linux package in Ubuntu: New Bug description: Hardware: CyberPowerPC / ASUS Z890 MAX GAMING WIFI7, BIOS 3002 (01/29/2026) CPU: Intel Core Ultra 9 285K (Arrow Lake) GPU: Intel Arrow Lake iGPU (i915) + NVIDIA RTX 4070 Ti SUPER (nvidia 595.84, DKMS) Kubuntu 24.04, X11/KDE Plasma Summary: Resume from hibernation reliably hangs on 6.8.0-139-generic. Booting 6.8.0-138-generic, with no other package changes, resumes from hibernation without any issues. This isolates the regression to the kernel package itself, not to userspace, initramfs, or firmware shipped alongside it. Details: The hibernation image is written and read back successfully. The restored kernel begins resuming devices and then never completes -- "PM: resume of devices complete" never prints. The machine is not frozen: it continues servicing timers indefinitely (observed for 5+ minutes without a hang or watchdog panic). Console output (captured with no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon): [ 52.940] PM: hibernation: Read 12721052 kbytes in 11.76 seconds [ 52.941] PM: Image successfully loaded [174.845] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin [174.865] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads [194.867] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout [194.873] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init [228.539] page_pool_release_retry() stalled pool shutdown: id 29, 7 inflight 60 sec (repeats at 120, 181, 241, 302, 362 sec ...) Note: mei_gsc_proxy binds correctly on resume from S3 (suspend-to-RAM) on this same machine; it only fails to bind after hibernation (S4). Also observed on the hibernate-entry path, one WARNING per CPU offlined (may be unrelated, noting for completeness): sysfs group 'package_00_die_00' not found for kobject 'intel_uncore_frequency' WARNING: at fs/sysfs/group.c:282 sysfs_remove_group+0x85/0x90 Call Trace: uncore_freq_remove_die_entry -> uncore_event_cpu_offline -> cpuhp_invoke_callback Steps to reproduce: 1. Boot 6.8.0-139-generic. 2. sudo systemctl hibernate (or via suspend-then-hibernate). 3. Power the machine back on. Expected: resumes normally. Actual: hangs indefinitely during device resume; only page_pool_release_retry warnings continue printing every ~60 seconds. Regression confirmed: Booted 6.8.0-138-generic with identical userspace/initramfs/firmware packages (only the running kernel differs). Hibernate/resume completed successfully with no issues. This confirms the regression is isolated to the 6.8.0-139 kernel package itself. Already ruled out: - nvidia DKMS module builds cleanly for 6.8.0-139; vermagic matches uname -r - Unloading all nvidia modules (nvidia_drm, nvidia_modeset, nvidia_uvm, nvidia) before hibernating does NOT fix the hang - CONFIG_DPM_WATCHDOG is not set in this kernel build, so no automatic panic/device name is produced on the hang; diagnosis required manual console capture via no_console_suspend Workaround in use: booting 6.8.0-138-generic until this is resolved. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: pm 3425 F.... wireplumber /dev/snd/controlC1: pm 3425 F.... wireplumber /dev/snd/controlC0: pm 3425 F.... wireplumber /dev/snd/seq: pm 3423 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 10 13:22:26 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (628 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-139-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=0 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-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2026 dmi.bios.release: 30.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 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.:bvr3002:bd01/29/2026:br30.2:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167009/+subscriptions
четверг
[Bug 2166998] Re: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701)
Confirmed working. Two notes: On kernel 7.0, hda_model is a parameter of snd_sof_intel_hda_generic, not snd_sof_intel_hda_common. The original suggestion had no effect because /sys/module/snd_sof_intel_hda_common/parameters/hda_model does not exist on this kernel. With the corrected module name, internal speakers work: options snd-sof-intel-hda-generic hda_model=1043:1f1f /sys/module/snd_sof_intel_hda_generic/parameters/hda_model now reads 1043:1f1f and audio outputs correctly from the internal speakers on ASUS ExpertBook P5406CCA (subsystem 0x10433701). Thanks a lot. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166998 Title: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701) Status in linux package in Ubuntu: Confirmed Bug description: speakers silent while HDMI, Bluetooth and headphone jack work; audio worked under Windows; subsystem ID 0x10433701; dmesg showing speaker_outs=0 with the generic driver; mixer unmuted with Auto-Mute disabled; and the workarounds that failed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: alsa-base 1.0.25+dfsg-0ubuntu9 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ajit 4051 F.... pipewire ajit 4064 F.... wireplumber /dev/snd/seq: ajit 4051 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 21:42:10 2026 InstallationDate: Installed on 2026-09-06 (4 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK P5406CCA PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 5.32 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: P5406CCA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P5406CCA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 2.11 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrP5406CCA.203:bd03/20/2026:br5.32:efr2.11:svnASUS:pnASUSEXPERTBOOKP5406CCA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP5406CCA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK P5406CCA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166998/+subscriptions
[Bug 2158229] Re: MT7925 wifi is hard blocked on Dell's machine
It looks like this "fix" completely destroyed MT7925 on Lenovo Thinkpad P14s (and probably others). Previously the hardware was woken up every second and now it silently goes to sleep and wakes - never. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158229 Title: MT7925 wifi is hard blocked on Dell's machine Status in linux package in Ubuntu: New Status in linux-hwe-7.0 package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-hwe-7.0 source package in Noble: Fix Released Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Won't Fix Status in linux-hwe-7.0 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Fix Released Status in linux-hwe-7.0 source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux source package in Stonking: New Status in linux-hwe-7.0 source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Impact] The Wi-Fi is hard blocked on Dell systems (CIDs: 202505-36757, 202501-36195, 202501-36253) and HP systems with Mediatek MT7925 cards. The wireless connection cannot be used. The rfkill state shows: $ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Fix] We revert the hardware rfkill polling feature for Mediatek MT7925 cards. This polling feature was introduced upstream in v6.16. We also revert the local DMI quirk for HP systems since polling is now disabled. Reverted commits: • Revert "wifi: mt76: mt7925: add rfkill_poll for hardware rfkill" (reverts upstream commit e54b870212c079bef4ff61238f8c1278a14d1863 from v6.16) • Revert local DMI quirk commit for HP systems (reverts local commit 20c9b07dcea9d49c876c9532a48a6dc88f43d0f9) [Test Plan] Check the rfkill state on affected hardware: $ rfkill list Without the patches: The Wireless LAN interface shows "Hard blocked: yes". The Wi-Fi connection does not work. With the patches: The Wireless LAN interface shows "Hard blocked: no". The Wi-Fi connection works. [Where problems could occur] This change affects the mt76 Mediatek wireless driver. If a system has a physical wireless switch that needs software polling, the switch will stop working. Toggling the physical switch would not change the Wi-Fi block state. ========================================================= [Impact] The wifi is hard blocked and can't be used randomly. [Test] 1. Boot up Machine 2. Run `rfkill list` to check wlan0 block state Wireless: Mediatek Inc. - 14c3:7925 ubuntu@localhost:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Affected Machines] 202505-36757 202501-36195 202501-36253 [Similar Issue] https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.14/+bug/2127044 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1020-oem 6.17.0-1020.20 ProcVersionSignature: Ubuntu 6.17.0-1020.20-oem 6.17.13 Uname: Linux 6.17.0-1020-oem x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1918 F.... pipewire ubuntu 1922 F.... wireplumber /dev/snd/controlC0: ubuntu 1922 F.... wireplumber /dev/snd/seq: ubuntu 1918 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Jun 25 05:43:16 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-proposed-20250604-520 InstallationDate: Installed on 2026-05-07 (49 days ago) InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250603) IwConfig: lo no wireless extensions. enp195s0f0 no wireless extensions. wlp194s0 no wireless extensions. MachineType: Dell Inc. Dell Pro Max 14 MC14255 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1020-oem root=UUID=881d0e73-6adc-444d-90b2-9491672e82b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.17.0-1020-oem N/A linux-backports-modules-6.17.0-1020-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2025 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0WT010 dmi.board.vendor: Dell Inc. dmi.board.version: D01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd09/09/2025:br1.4:efr1.3:svnDellInc.:pnDellProMax14MC14255:pvr:rvnDellInc.:rn0WT010:rvrD01:cvnDellInc.:ct10:cvr:sku0D80: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 MC14255 dmi.product.sku: 0D80 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158229/+subscriptions
[Bug 2161004] Re: [SRU] HPE: Fix for UBSAN array-index-out-of-bounds
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161004 Title: [SRU] HPE: Fix for UBSAN array-index-out-of-bounds Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux source package in Stonking: Fix Committed Bug description: [ Impact ] When UBSAN is enabled, multiple array-index-out-of-bounds messages are printed: [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:276:23 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:277:32 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:282:16 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.515850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1344:23 [ 0.519851] [ T1] index 1 is out of range for type '<unknown> [1]' ... [ 0.603850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1345:32 [ 0.607850] [ T1] index 1 is out of range for type '<unknown> [1]' ... [ 0.691850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1353:20 [ 0.695850] [ T1] index 1 is out of range for type '<unknown> [1]' One-element arrays have been deprecated: [ Fix ] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=21433d3e3ca14d20f9b0c2237b3d3a1355af7907 [ Test Plan ] Installed 24.04. apt upgrade to install the latest kernel (6.8.0-136). Reboot with 6.8.0-136. Confirmed UBSAN warning messages (same as bug description). Installed lp_2161004_ubsan_array_index deb packages. Reboot with new kernel Confirmed no UBSAM warning messages. Kernel without the fix (July 1 build date): [ 0.000000] Linux version 6.8.0-136-generic (buildd@lcy02-amd64-041) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #136-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 21:53:05 UTC 2026 (Ubuntu 6.8.0-136.136-generic 6.8.12) Kernel with the fix (July 16 build date): [ 0.000000] Linux version 6.8.0-136-generic (root@buildnoble) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #136 SMP PREEMPT_DYNAMIC Thu Jul 16 20:05:25 UTC 2026 (Ubuntu 6.8.0-136.136-generic 6.8.12) [ Where problems could occur ] The regression risk is low [ Other Info ] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/ubsan_array_index To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161004/+subscriptions
[Bug 2167019] [NEW] MT7925 Wi-Fi: silent data-path packet loss on associated link after pc-kernel 7.0.0-31.31
Public bug reported: The pc-kernel snap refresh from 7.0.0-28.28 (rev 3672) to 7.0.0-31.31 (rev 3699) breaks Wi-Fi data traffic on a MediaTek MT7925 [14c3:7925] (Filogic 360). The distinguishing symptom is that connection management keeps working while the data path does not. The card scans, authenticates, completes the WPA 4-way handshake and obtains its DHCP lease -- the same address every time -- then sits in the "activated" state looking healthy while almost no traffic completes. DNS resolution fails essentially continuously. No firmware crash, watchdog reset, or driver error is logged at any point. The link reports itself as connected with strong signal throughout, which makes this easy to misdiagnose as a DNS, VPN, or upstream network problem. Reverting to 7.0.0-28.28 restores full function immediately and reproducibly. [KEY EVIDENCE: FAILURE WHILE THE LINK IS PROVABLY STABLE] On a 12-minute boot of 7.0.0-31 there is a window from 12:21:11 to 12:29:20 -- just over eight minutes -- during which the interface was continuously associated, with ZERO deauthentication events and the DHCP lease held. Within that stable window there were 12 distinct DNS resolution failures, roughly one per minute, spread evenly across it. This rules out reconnection churn as the cause. The link was up, authenticated and addressed, and traffic still did not pass. The packet loss is the primary fault; the disconnects are secondary. [DNS FAILURES, BAD VS GOOD KERNEL] boot kernel duration "Temporary failure NoDnsConnectivity in name resolution" ---- ---------------- -------- ------------------ ----------------- -4 7.0.0-28-generic 16h 09m 0 0 -1 7.0.0-31-generic 12m 42 12 Zero failures in sixteen hours on the old kernel; 42 in twelve minutes on the new. [VERSIONS] GOOD BAD snap revision pc-kernel rev 3672 pc-kernel rev 3699 version 7.0.0-28.28 7.0.0-31.31 kernel 7.0.0-28-generic 7.0.0-31-generic MT7925 HW/SW build 20260106153007a 20260605184651a MT7925 WM firmware 20260106153120 20260605184805 PRIME SUSPECT: the kernel snap carries the MT7925 firmware blobs, and 7.0.0-31 bumps them from a 2026-01-06 build to a 2026-06-05 build. Given that association and control-plane exchanges succeed while bulk data silently fails, a firmware-side RX/TX data-path fault (aggregation, offload, or data-path key handling) seems more likely than a change in the mt7925e/mt76 driver code. These two should be bisected independently. [REPRODUCTION] 1. On MT7925 hardware, run pc-kernel 7.0.0-28.28 -- Wi-Fi is stable. 2. snap refresh pc-kernel to 7.0.0-31.31 (rev 3699). Reboot. 3. Associate to a 5 GHz AP. Association, 4-way handshake and DHCP all succeed; the interface reaches "activated" and holds a valid lease. 4. Attempt normal use. Traffic largely does not complete; DNS fails repeatedly while the link continues to report itself as connected. 5. snap revert pc-kernel to rev 3672 and reboot -- problem disappears entirely. Performed twice on this machine (two separate boots of 7.0.0-31, two reverts). [DISCONNECTS, CORRECTLY ATTRIBUTED] Six deauthentications occurred on the 12-minute boot, but they are not all spontaneous. By the NetworkManager state-change reason recorded at the same instant: 12:20:12 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:21:04 activated -> deactivating ('new-activation') operator reconnect 12:21:06 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:29:20 activated -> deactivating ('new-activation') operator reconnect 12:29:21 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:30:25 activated -> deactivating ('unmanaged') shutdown for reboot So three spontaneous interface resets in 12 minutes, not six; the rest were the operator manually reconnecting to try to recover, plus shutdown. The 16-hour 7.0.0-28 boot recorded two deauthentications in total. The spontaneous ones show the supplicant returning to "internal-starting", indicating the interface was re-initialised underneath userspace rather than roamed by choice -- consistent with a driver- or firmware-level reset. [HEALTHY BASELINE ON 7.0.0-28, FOR CONTRAST] ping 172.16.96.1 (gateway) 20 packets, 0% loss, rtt 2.203/2.825/6.265 ms ping 1.1.1.1 20 packets, 0% loss, rtt 7.042/9.424/15.675 ms ping 8.8.8.8 20 packets, 0% loss, rtt 7.739/10.719/15.754 ms signal -46 dBm rx bitrate 258.0 MBit/s HE-MCS 10 HE-NSS 2 tx bitrate 286.7 MBit/s HE-MCS 11 HE-NSS 2 tx retries 6 (of 9429 tx packets) tx failed 0 beacon loss 0 Signal is strong and error counters are essentially zero, so this is not a weak-signal or RF-congestion problem that merely coincided with the update. [CAVEATS FOR ANYONE REPRODUCING] 1. THE LOSS PERCENTAGE WAS NOT MEASURED. I observed roughly 80% packet loss while running 7.0.0-31, severe enough to make the machine unusable, but no ping statistics or interface counters were captured during either 7.0.0-31 boot and those counters do not survive a reboot. Treat 80% as a reported magnitude, not a measurement. What the logs independently establish is the 42 DNS failures, the 12 failures inside a provably stable 8-minute window, and the three spontaneous interface resets -- all specific to 7.0.0-31. 2. DNS ON THIS HOST IS DoH THROUGH A CLOUDFLARE WARP TUNNEL (operation_mode: WarpWithDnsOverHttps, tunnel MTU 1280), not plain UDP/53. DNS therefore depends on the tunnel, which depends on the Wi-Fi data path -- which is why DNS failure is such a visible symptom here. A machine without WARP may present less dramatically, as general packet loss rather than near-total DNS failure. Do not assume the absence of total DNS failure means the bug is absent; test the data path directly. The most useful capture on 7.0.0-31, while associated and stable, is: ping -c 200 -i 0.2 <gateway> # on-link, bypasses both tunnel and DNS ip -s link show wlp194s0 iw dev wlp194s0 station dump [IMPACT] linux-image-generic-hwe-26.04 currently has candidate 7.0.0-31.31 in resolute-updates, so this is the version being handed out. Any MT7925 (Filogic 360) system taking the update is likely to hit this. The MT7925 is common in current AMD laptops. The silent nature of the failure makes it worse than an outright breakage: the card reports itself as connected with a valid lease and good signal, so affected users are likely to blame their router, ISP, or VPN rather than the kernel. [CURRENT MITIGATION] snap revert pc-kernel # back to rev 3672 / 7.0.0-28.28 snap refresh --hold pc-kernel # prevents automatic re-update Both revisions are held; rev 3699 is retained but disabled, so it remains available for further testing without a re-download. [REQUESTED] 1. Confirm whether the MT7925 firmware bump (2026-01-06 -> 2026-06-05) is the cause, independent of the mt76/mt7925e driver changes in 7.0.0-31. 2. If so, consider reverting the firmware blob or gating it pending a fix. 3. Investigate why the data path fails silently while association, EAPOL and DHCP all succeed -- the absence of any logged error is itself a defect. [SYSTEM] Ubuntu 26.04.1 LTS (resolute), Ubuntu Core / snap-delivered kernel, x86_64 Wi-Fi: MEDIATEK MT7925 802.11be 160MHz 2x2 PCIe [Filogic 360] [14c3:7925] Subsystem: Lenovo [17aa:e025], PCI c2:00.0, driver mt7925e (mt76) AP: ch 116 (5580 MHz), 20 MHz, WPA2/3 Full diagnostics attached (mt7925-diagnostics.txt). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "regression-update resolute mt7925" https://bugs.launchpad.net/bugs/2167019/+attachment/5999324/+files/mt7925-diagnostics.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167019 Title: MT7925 Wi-Fi: silent data-path packet loss on associated link after pc-kernel 7.0.0-31.31 Status in linux package in Ubuntu: New Bug description: The pc-kernel snap refresh from 7.0.0-28.28 (rev 3672) to 7.0.0-31.31 (rev 3699) breaks Wi-Fi data traffic on a MediaTek MT7925 [14c3:7925] (Filogic 360). The distinguishing symptom is that connection management keeps working while the data path does not. The card scans, authenticates, completes the WPA 4-way handshake and obtains its DHCP lease -- the same address every time -- then sits in the "activated" state looking healthy while almost no traffic completes. DNS resolution fails essentially continuously. No firmware crash, watchdog reset, or driver error is logged at any point. The link reports itself as connected with strong signal throughout, which makes this easy to misdiagnose as a DNS, VPN, or upstream network problem. Reverting to 7.0.0-28.28 restores full function immediately and reproducibly. [KEY EVIDENCE: FAILURE WHILE THE LINK IS PROVABLY STABLE] On a 12-minute boot of 7.0.0-31 there is a window from 12:21:11 to 12:29:20 -- just over eight minutes -- during which the interface was continuously associated, with ZERO deauthentication events and the DHCP lease held. Within that stable window there were 12 distinct DNS resolution failures, roughly one per minute, spread evenly across it. This rules out reconnection churn as the cause. The link was up, authenticated and addressed, and traffic still did not pass. The packet loss is the primary fault; the disconnects are secondary. [DNS FAILURES, BAD VS GOOD KERNEL] boot kernel duration "Temporary failure NoDnsConnectivity in name resolution" ---- ---------------- -------- ------------------ ----------------- -4 7.0.0-28-generic 16h 09m 0 0 -1 7.0.0-31-generic 12m 42 12 Zero failures in sixteen hours on the old kernel; 42 in twelve minutes on the new. [VERSIONS] GOOD BAD snap revision pc-kernel rev 3672 pc-kernel rev 3699 version 7.0.0-28.28 7.0.0-31.31 kernel 7.0.0-28-generic 7.0.0-31-generic MT7925 HW/SW build 20260106153007a 20260605184651a MT7925 WM firmware 20260106153120 20260605184805 PRIME SUSPECT: the kernel snap carries the MT7925 firmware blobs, and 7.0.0-31 bumps them from a 2026-01-06 build to a 2026-06-05 build. Given that association and control-plane exchanges succeed while bulk data silently fails, a firmware-side RX/TX data-path fault (aggregation, offload, or data-path key handling) seems more likely than a change in the mt7925e/mt76 driver code. These two should be bisected independently. [REPRODUCTION] 1. On MT7925 hardware, run pc-kernel 7.0.0-28.28 -- Wi-Fi is stable. 2. snap refresh pc-kernel to 7.0.0-31.31 (rev 3699). Reboot. 3. Associate to a 5 GHz AP. Association, 4-way handshake and DHCP all succeed; the interface reaches "activated" and holds a valid lease. 4. Attempt normal use. Traffic largely does not complete; DNS fails repeatedly while the link continues to report itself as connected. 5. snap revert pc-kernel to rev 3672 and reboot -- problem disappears entirely. Performed twice on this machine (two separate boots of 7.0.0-31, two reverts). [DISCONNECTS, CORRECTLY ATTRIBUTED] Six deauthentications occurred on the 12-minute boot, but they are not all spontaneous. By the NetworkManager state-change reason recorded at the same instant: 12:20:12 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:21:04 activated -> deactivating ('new-activation') operator reconnect 12:21:06 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:29:20 activated -> deactivating ('new-activation') operator reconnect 12:29:21 activated -> unavailable (reason 'none') SPONTANEOUS reset 12:30:25 activated -> deactivating ('unmanaged') shutdown for reboot So three spontaneous interface resets in 12 minutes, not six; the rest were the operator manually reconnecting to try to recover, plus shutdown. The 16-hour 7.0.0-28 boot recorded two deauthentications in total. The spontaneous ones show the supplicant returning to "internal-starting", indicating the interface was re-initialised underneath userspace rather than roamed by choice -- consistent with a driver- or firmware-level reset. [HEALTHY BASELINE ON 7.0.0-28, FOR CONTRAST] ping 172.16.96.1 (gateway) 20 packets, 0% loss, rtt 2.203/2.825/6.265 ms ping 1.1.1.1 20 packets, 0% loss, rtt 7.042/9.424/15.675 ms ping 8.8.8.8 20 packets, 0% loss, rtt 7.739/10.719/15.754 ms signal -46 dBm rx bitrate 258.0 MBit/s HE-MCS 10 HE-NSS 2 tx bitrate 286.7 MBit/s HE-MCS 11 HE-NSS 2 tx retries 6 (of 9429 tx packets) tx failed 0 beacon loss 0 Signal is strong and error counters are essentially zero, so this is not a weak-signal or RF-congestion problem that merely coincided with the update. [CAVEATS FOR ANYONE REPRODUCING] 1. THE LOSS PERCENTAGE WAS NOT MEASURED. I observed roughly 80% packet loss while running 7.0.0-31, severe enough to make the machine unusable, but no ping statistics or interface counters were captured during either 7.0.0-31 boot and those counters do not survive a reboot. Treat 80% as a reported magnitude, not a measurement. What the logs independently establish is the 42 DNS failures, the 12 failures inside a provably stable 8-minute window, and the three spontaneous interface resets -- all specific to 7.0.0-31. 2. DNS ON THIS HOST IS DoH THROUGH A CLOUDFLARE WARP TUNNEL (operation_mode: WarpWithDnsOverHttps, tunnel MTU 1280), not plain UDP/53. DNS therefore depends on the tunnel, which depends on the Wi-Fi data path -- which is why DNS failure is such a visible symptom here. A machine without WARP may present less dramatically, as general packet loss rather than near-total DNS failure. Do not assume the absence of total DNS failure means the bug is absent; test the data path directly. The most useful capture on 7.0.0-31, while associated and stable, is: ping -c 200 -i 0.2 <gateway> # on-link, bypasses both tunnel and DNS ip -s link show wlp194s0 iw dev wlp194s0 station dump [IMPACT] linux-image-generic-hwe-26.04 currently has candidate 7.0.0-31.31 in resolute-updates, so this is the version being handed out. Any MT7925 (Filogic 360) system taking the update is likely to hit this. The MT7925 is common in current AMD laptops. The silent nature of the failure makes it worse than an outright breakage: the card reports itself as connected with a valid lease and good signal, so affected users are likely to blame their router, ISP, or VPN rather than the kernel. [CURRENT MITIGATION] snap revert pc-kernel # back to rev 3672 / 7.0.0-28.28 snap refresh --hold pc-kernel # prevents automatic re-update Both revisions are held; rev 3699 is retained but disabled, so it remains available for further testing without a re-download. [REQUESTED] 1. Confirm whether the MT7925 firmware bump (2026-01-06 -> 2026-06-05) is the cause, independent of the mt76/mt7925e driver changes in 7.0.0-31. 2. If so, consider reverting the firmware blob or gating it pending a fix. 3. Investigate why the data path fails silently while association, EAPOL and DHCP all succeed -- the absence of any logged error is itself a defect. [SYSTEM] Ubuntu 26.04.1 LTS (resolute), Ubuntu Core / snap-delivered kernel, x86_64 Wi-Fi: MEDIATEK MT7925 802.11be 160MHz 2x2 PCIe [Filogic 360] [14c3:7925] Subsystem: Lenovo [17aa:e025], PCI c2:00.0, driver mt7925e (mt76) AP: ch 116 (5580 MHz), 20 MHz, WPA2/3 Full diagnostics attached (mt7925-diagnostics.txt). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167019/+subscriptions
[Bug 2167015] [NEW] System hangs on poweroff since kernel 7.0.0 series (regression) on ThinkPad L14 Gen1 AMD
Public bug reported: Since upgrading to kernel 7.0.0-28-generic (and confirmed also in 7.0.0-30 and 7.0.0-31), my system no longer powers off cleanly. This is a clear regression: kernel 6.17.0-40-generic works reliably on the exact same hardware/install. Hardware: Lenovo ThinkPad L14 Gen 1 AMD (Type 20U5/20U6), AMD Ryzen 5 PRO 4650U, BIOS R19ET56W (1.40). Distro: Linux Mint (based on Ubuntu 24.04 / noble, HWE kernel stack) Symptom: When shutting down, all systemd services stop cleanly and the log reaches "Reached target poweroff.target", "Syncing filesystems and block devices", "Sending SIGTERM to remaining processes" - then the journal stops. The screen goes black, but the fans keep spinning and the power LED stays on. The system never actually powers off; it requires a hard power-button hold to turn off. Tested and confirmed: - Broken: 7.0.0-28-generic, 7.0.0-30-generic, 7.0.0-31-generic - Working: 6.17.0-40-generic, 6.17.0-35-generic (both shut down cleanly every time) No custom kernel parameters were needed on the working kernels (default "quiet splash"). Testing with acpi=force / reboot=acpi / acpi_osi=Linux on the broken kernel did not help and even caused reboot to hang as well. This looks like a regression in ACPI/power-management handling introduced somewhere between 6.17.0-40 and 7.0.0-28. Steps to reproduce: 1. Boot into kernel 7.0.0-31-generic (or 7.0.0-28/30) 2. Run "sudo poweroff" or shut down via the desktop menu 3. Observe: screen turns black, fans keep running, power LED stays on, system never actually powers off Expected result: System powers off completely. Actual result: System hangs indefinitely until a hard power-button shutdown is performed. ** 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/2167015 Title: System hangs on poweroff since kernel 7.0.0 series (regression) on ThinkPad L14 Gen1 AMD Status in linux package in Ubuntu: New Bug description: Since upgrading to kernel 7.0.0-28-generic (and confirmed also in 7.0.0-30 and 7.0.0-31), my system no longer powers off cleanly. This is a clear regression: kernel 6.17.0-40-generic works reliably on the exact same hardware/install. Hardware: Lenovo ThinkPad L14 Gen 1 AMD (Type 20U5/20U6), AMD Ryzen 5 PRO 4650U, BIOS R19ET56W (1.40). Distro: Linux Mint (based on Ubuntu 24.04 / noble, HWE kernel stack) Symptom: When shutting down, all systemd services stop cleanly and the log reaches "Reached target poweroff.target", "Syncing filesystems and block devices", "Sending SIGTERM to remaining processes" - then the journal stops. The screen goes black, but the fans keep spinning and the power LED stays on. The system never actually powers off; it requires a hard power-button hold to turn off. Tested and confirmed: - Broken: 7.0.0-28-generic, 7.0.0-30-generic, 7.0.0-31-generic - Working: 6.17.0-40-generic, 6.17.0-35-generic (both shut down cleanly every time) No custom kernel parameters were needed on the working kernels (default "quiet splash"). Testing with acpi=force / reboot=acpi / acpi_osi=Linux on the broken kernel did not help and even caused reboot to hang as well. This looks like a regression in ACPI/power-management handling introduced somewhere between 6.17.0-40 and 7.0.0-28. Steps to reproduce: 1. Boot into kernel 7.0.0-31-generic (or 7.0.0-28/30) 2. Run "sudo poweroff" or shut down via the desktop menu 3. Observe: screen turns black, fans keep running, power LED stays on, system never actually powers off Expected result: System powers off completely. Actual result: System hangs indefinitely until a hard power-button shutdown is performed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167015/+subscriptions
[Bug 2167012] [NEW] System performs hard reset shortly after boot with kernel 7.0.0-31-generic
Public bug reported: Environment Hardware: XMG Focus 17 M25, NVIDIA RTX 5070 Ti (full 140-150W variant) Kernel (broken): linux-image-7.0.0-31-generic Kernel (working): linux-image-7.0.0-30-generic GPU driver: nvidia-driver-580-open, version 580.173.02, DKMS-built cleanly for both kernel versions Desktop environments installed: GNOME, KDE Plasma, XFCE Symptom Machine reboots abruptly with no warning while running kernel 7.0.0-31 journalctl -b -1 ends without any clean shutdown/reboot log entries Occurred multiple times in short succession (boots lasting ~2-3 minutes each) shortly after a kernel/driver update occurred on a freshly booted, idle system (ruled out thermal throttling via sensors / kernel thermal zone logs, which showed nothing abnormal) Under GNOME (Wayland) and KDE Plasma, the system crashed Under XFCE (X11, minimal), the system ran stably on the same kernel Downgraded/pinned to linux-image-7.0.0-30-generic (apt-mark hold on linux-image-generic-hwe-26.04, linux-generic-hwe-26.04, linux-headers- generic-hwe-26.04). System has been stable since. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Sep 10 21:06:00 2026 InstallationDate: Installed on 2026-08-28 (13 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: SchenkerTechnologiesGmbH XMG FOCUS 17 (M25) ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash intel_idle.max_cstate=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. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2026 dmi.bios.release: 7.9 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.09RTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNx dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: N/A dmi.ec.firmware.release: 9.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.09RTR4:bd03/19/2026:br7.9:efr9.4:svnSchenkerTechnologiesGmbH:pnXMGFOCUS17(M25):pvrNotApplicable:rvnNB01:rnV3xxSNx:rvrNotApplicable:cvnSchenkerTechnologiesGmbH:ct10:cvrN/A:skuXFO17M25:pfa: dmi.product.name: XMG FOCUS 17 (M25) dmi.product.sku: XFO17M25 dmi.product.version: Not Applicable dmi.sys.vendor: SchenkerTechnologiesGmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167012 Title: System performs hard reset shortly after boot with kernel 7.0.0-31-generic Status in linux package in Ubuntu: New Bug description: Environment Hardware: XMG Focus 17 M25, NVIDIA RTX 5070 Ti (full 140-150W variant) Kernel (broken): linux-image-7.0.0-31-generic Kernel (working): linux-image-7.0.0-30-generic GPU driver: nvidia-driver-580-open, version 580.173.02, DKMS-built cleanly for both kernel versions Desktop environments installed: GNOME, KDE Plasma, XFCE Symptom Machine reboots abruptly with no warning while running kernel 7.0.0-31 journalctl -b -1 ends without any clean shutdown/reboot log entries Occurred multiple times in short succession (boots lasting ~2-3 minutes each) shortly after a kernel/driver update occurred on a freshly booted, idle system (ruled out thermal throttling via sensors / kernel thermal zone logs, which showed nothing abnormal) Under GNOME (Wayland) and KDE Plasma, the system crashed Under XFCE (X11, minimal), the system ran stably on the same kernel Downgraded/pinned to linux-image-7.0.0-30-generic (apt-mark hold on linux-image-generic-hwe-26.04, linux-generic-hwe-26.04, linux-headers- generic-hwe-26.04). System has been stable since. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Sep 10 21:06:00 2026 InstallationDate: Installed on 2026-08-28 (13 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: SchenkerTechnologiesGmbH XMG FOCUS 17 (M25) ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash intel_idle.max_cstate=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. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2026 dmi.bios.release: 7.9 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.09RTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNx dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: N/A dmi.ec.firmware.release: 9.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.09RTR4:bd03/19/2026:br7.9:efr9.4:svnSchenkerTechnologiesGmbH:pnXMGFOCUS17(M25):pvrNotApplicable:rvnNB01:rnV3xxSNx:rvrNotApplicable:cvnSchenkerTechnologiesGmbH:ct10:cvrN/A:skuXFO17M25:pfa: dmi.product.name: XMG FOCUS 17 (M25) dmi.product.sku: XFO17M25 dmi.product.version: Not Applicable dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167012/+subscriptions
[Bug 2163121] Re: [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28
Ubuntu 26.04.1 LTS Linux kernel 7.0.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Aug 1 04:26:38 UTC 2026 x86_64 AMD Ryzen™ 5600G AMD Radeon™ RX 6600 Dual monitor Desktop System connected to the Graphic Card via HDMI cable Shutdown randomly does not completely power off the PC —Fans & LEDs still ON indefinitely— need to plug off the power cable. Current temporary workaround: • Use older kernel 6.17 version OR • Plug off all the HDMI cable before issuing poweroff command if I have to use 7.0.0-31 kernel -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163121 Title: [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-7.0 package in Ubuntu: Fix Committed Status in linux source package in Noble: Invalid Status in linux-hwe-7.0 source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux-hwe-7.0 source package in Resolute: Invalid Bug description: Issue Description: When shutting down the system with an external monitor connected via HDMI, the OS finishes the shutdown process normally, but the laptop hardware remains powered on (the power LED stays illuminated and the machine does not fully power off). If the HDMI cable is disconnected before the shutdown, the laptop powers off completely and correctly. Important note: Once the system enters this "stuck" state (black screen, power LED on), unplugging the HDMI cable does not recover the system or allow it to finish powering off. It remains completely frozen. The HDMI cable must be unplugged before initiating the shutdown sequence to avoid the hang. Additional troubleshooting: I have also tested this with two different HDMI cables to rule out a faulty cable, but the issue persists regardless of the cable used. Regression Details: This is a regression introduced in kernel 7.0.0-28. I have tested previous kernels on the exact same hardware and they work perfectly (the system powers off completely even with the HDMI connected). Fails in: Kernel 7.0.0-28-generic Works in: Kernel 7.0.0-14-generic, 6.x branch Steps to Reproduce: 1. Boot the laptop with kernel 7.0.0-28. 2, Connect an external monitor via the HDMI port. 3. Shut down the system from the GUI (or via sudo shutdown now). 4. Notice the OS halts, but the laptop's power LED remains on and the machine does not fully power down. 5. Unplugging the HDMI cable at this frozen stage does nothing; the machine remains stuck and must be forced off by holding the physical power button. System Information: OS: Linux Mint 22.3 Zena (Ubuntu 24.04 noble base) Hardware: LENOVO IdeaPad 5 15ALC05 CPU: AMD Ryzen 7 5700U with Radeon Graphics (Lucienne / Zen 2) GPU: AMD Lucienne (amdgpu driver) BIOS: H2CN33WW (08/30/2023) External Monitor: Xiaomi Monitor A22i (Model: A22FAB-RAGL) Hardware Details: Kernel: 7.0.0-28-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 CPU: Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 1 Graphics: Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: user 1698 F.... wireplumber /dev/snd/controlC0: user 1698 F.... wireplumber /dev/snd/seq: user 1696 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-07-22 (20 days ago) InstallationMedia: Linux Mint 22.3 "Zena" - Release amd64 20260108 MachineType: LENOVO 82LN Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 7.0.0-28.28~24.04.1-generic 7.0.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-28-generic N/A linux-backports-modules-7.0.0-28-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 Tags: zena Uname: Linux 7.0.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 08/30/2023 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: H2CN33WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ALC05 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrH2CN33WW:bd08/30/2023:br1.33:efr1.33:svnLENOVO:pn82LN:pvrIdeaPad515ALC05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad515ALC05:skuLENOVO_MT_82LN_BU_idea_FM_IdeaPad515ALC05:pfaIdeaPad515ALC05: dmi.product.family: IdeaPad 5 15ALC05 dmi.product.name: 82LN dmi.product.sku: LENOVO_MT_82LN_BU_idea_FM_IdeaPad 5 15ALC05 dmi.product.version: IdeaPad 5 15ALC05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163121/+subscriptions
[Bug 2167009] [NEW] Regression in 6.8.0-139: resume from hibernation hangs (GSC proxy bind timeout); 6.8.0-138 unaffected with identical userspace
Public bug reported: Hardware: CyberPowerPC / ASUS Z890 MAX GAMING WIFI7, BIOS 3002 (01/29/2026) CPU: Intel Core Ultra 9 285K (Arrow Lake) GPU: Intel Arrow Lake iGPU (i915) + NVIDIA RTX 4070 Ti SUPER (nvidia 595.84, DKMS) Kubuntu 24.04, X11/KDE Plasma Summary: Resume from hibernation reliably hangs on 6.8.0-139-generic. Booting 6.8.0-138-generic, with no other package changes, resumes from hibernation without any issues. This isolates the regression to the kernel package itself, not to userspace, initramfs, or firmware shipped alongside it. Details: The hibernation image is written and read back successfully. The restored kernel begins resuming devices and then never completes -- "PM: resume of devices complete" never prints. The machine is not frozen: it continues servicing timers indefinitely (observed for 5+ minutes without a hang or watchdog panic). Console output (captured with no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon): [ 52.940] PM: hibernation: Read 12721052 kbytes in 11.76 seconds [ 52.941] PM: Image successfully loaded [174.845] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin [174.865] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads [194.867] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout [194.873] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init [228.539] page_pool_release_retry() stalled pool shutdown: id 29, 7 inflight 60 sec (repeats at 120, 181, 241, 302, 362 sec ...) Note: mei_gsc_proxy binds correctly on resume from S3 (suspend-to-RAM) on this same machine; it only fails to bind after hibernation (S4). Also observed on the hibernate-entry path, one WARNING per CPU offlined (may be unrelated, noting for completeness): sysfs group 'package_00_die_00' not found for kobject 'intel_uncore_frequency' WARNING: at fs/sysfs/group.c:282 sysfs_remove_group+0x85/0x90 Call Trace: uncore_freq_remove_die_entry -> uncore_event_cpu_offline -> cpuhp_invoke_callback Steps to reproduce: 1. Boot 6.8.0-139-generic. 2. sudo systemctl hibernate (or via suspend-then-hibernate). 3. Power the machine back on. Expected: resumes normally. Actual: hangs indefinitely during device resume; only page_pool_release_retry warnings continue printing every ~60 seconds. Regression confirmed: Booted 6.8.0-138-generic with identical userspace/initramfs/firmware packages (only the running kernel differs). Hibernate/resume completed successfully with no issues. This confirms the regression is isolated to the 6.8.0-139 kernel package itself. Already ruled out: - nvidia DKMS module builds cleanly for 6.8.0-139; vermagic matches uname -r - Unloading all nvidia modules (nvidia_drm, nvidia_modeset, nvidia_uvm, nvidia) before hibernating does NOT fix the hang - CONFIG_DPM_WATCHDOG is not set in this kernel build, so no automatic panic/device name is produced on the hang; diagnosis required manual console capture via no_console_suspend Workaround in use: booting 6.8.0-138-generic until this is resolved. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: pm 3425 F.... wireplumber /dev/snd/controlC1: pm 3425 F.... wireplumber /dev/snd/controlC0: pm 3425 F.... wireplumber /dev/snd/seq: pm 3423 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 10 13:22:26 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (628 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-139-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=0 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-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2026 dmi.bios.release: 30.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 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.:bvr3002:bd01/29/2026:br30.2:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167009 Title: Regression in 6.8.0-139: resume from hibernation hangs (GSC proxy bind timeout); 6.8.0-138 unaffected with identical userspace Status in linux package in Ubuntu: New Bug description: Hardware: CyberPowerPC / ASUS Z890 MAX GAMING WIFI7, BIOS 3002 (01/29/2026) CPU: Intel Core Ultra 9 285K (Arrow Lake) GPU: Intel Arrow Lake iGPU (i915) + NVIDIA RTX 4070 Ti SUPER (nvidia 595.84, DKMS) Kubuntu 24.04, X11/KDE Plasma Summary: Resume from hibernation reliably hangs on 6.8.0-139-generic. Booting 6.8.0-138-generic, with no other package changes, resumes from hibernation without any issues. This isolates the regression to the kernel package itself, not to userspace, initramfs, or firmware shipped alongside it. Details: The hibernation image is written and read back successfully. The restored kernel begins resuming devices and then never completes -- "PM: resume of devices complete" never prints. The machine is not frozen: it continues servicing timers indefinitely (observed for 5+ minutes without a hang or watchdog panic). Console output (captured with no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon): [ 52.940] PM: hibernation: Read 12721052 kbytes in 11.76 seconds [ 52.941] PM: Image successfully loaded [174.845] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin [174.865] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads [194.867] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout [194.873] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init [228.539] page_pool_release_retry() stalled pool shutdown: id 29, 7 inflight 60 sec (repeats at 120, 181, 241, 302, 362 sec ...) Note: mei_gsc_proxy binds correctly on resume from S3 (suspend-to-RAM) on this same machine; it only fails to bind after hibernation (S4). Also observed on the hibernate-entry path, one WARNING per CPU offlined (may be unrelated, noting for completeness): sysfs group 'package_00_die_00' not found for kobject 'intel_uncore_frequency' WARNING: at fs/sysfs/group.c:282 sysfs_remove_group+0x85/0x90 Call Trace: uncore_freq_remove_die_entry -> uncore_event_cpu_offline -> cpuhp_invoke_callback Steps to reproduce: 1. Boot 6.8.0-139-generic. 2. sudo systemctl hibernate (or via suspend-then-hibernate). 3. Power the machine back on. Expected: resumes normally. Actual: hangs indefinitely during device resume; only page_pool_release_retry warnings continue printing every ~60 seconds. Regression confirmed: Booted 6.8.0-138-generic with identical userspace/initramfs/firmware packages (only the running kernel differs). Hibernate/resume completed successfully with no issues. This confirms the regression is isolated to the 6.8.0-139 kernel package itself. Already ruled out: - nvidia DKMS module builds cleanly for 6.8.0-139; vermagic matches uname -r - Unloading all nvidia modules (nvidia_drm, nvidia_modeset, nvidia_uvm, nvidia) before hibernating does NOT fix the hang - CONFIG_DPM_WATCHDOG is not set in this kernel build, so no automatic panic/device name is produced on the hang; diagnosis required manual console capture via no_console_suspend Workaround in use: booting 6.8.0-138-generic until this is resolved. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: pm 3425 F.... wireplumber /dev/snd/controlC1: pm 3425 F.... wireplumber /dev/snd/controlC0: pm 3425 F.... wireplumber /dev/snd/seq: pm 3423 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 10 13:22:26 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (628 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-139-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro no_console_suspend ignore_loglevel pm_debug_messages keep_bootcon cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" nvidia_drm.fbdev=0 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-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2026 dmi.bios.release: 30.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 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.:bvr3002:bd01/29/2026:br30.2:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167009/+subscriptions
среда
[Bug 2166710] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2166710/+attachment/5999083/+files/AudioDevicesInUse.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166710 Title: choppy audio 2 channel music files Status in linux package in Ubuntu: Incomplete Bug description: Music files played with any player comes out choppy, hesitates stops. Videos or streaming (youtube netfilx etc) work fine. If I boot to earlier version - 22.1 no problem. Zorin is bad too! The GPU is a 9070xt 16gb via hdmi. [code] System: Kernel: 7.0.0-31-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> Mobo: ASUSTeK model: ROG STRIX X870E-E GAMING WIFI v: Rev 1.xx serial: <superuser required> part-nu: SKU uuid: <superuser required> UEFI: American Megatrends v: 2402 date: 07/13/2026 Battery: Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 serial: <filter> charge: 55% (should be ignored) rechargeable: yes status: discharging Device-2: hidpp_battery_1 model: Logitech K350 serial: <filter> charge: 50% (should be ignored) rechargeable: yes status: N/A CPU: Info: 16-core model: AMD Ryzen 9 9950X bits: 64 type: MT MCP MCM smt: enabled arch: N/A rev: 0 cache: L1: 1.2 MiB L2: 16 MiB L3: 64 MiB Speed (MHz): avg: 1425 high: 5734 min/max: 624/5756 boost: enabled cores: 1: 2867 2: 624 3: 624 4: 5734 5: 5709 6: 624 7: 624 8: 624 9: 624 10: 3629 11: 624 12: 624 13: 624 14: 624 15: 624 16: 624 17: 624 18: 624 19: 624 20: 5731 21: 5730 22: 624 23: 624 24: 624 25: 624 26: 624 27: 624 28: 624 29: 624 30: 624 31: 624 32: 624 bogomips: 274697 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD vendor: ASRock driver: amdgpu v: kernel pcie: speed: 32 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:7550 class-ID: 0300 Device-2: AMD vendor: ASUSTeK driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: none empty: DP-4, DP-5, HDMI-A-2, Writeback-2 bus-ID: 7c:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 46.0 C Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 9-2:3 chip-ID: 046d:082d class-ID: 0102 serial: <filter> Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1280x720 s-dpi: 96 s-size: 339x191mm (13.35x7.52") s-diag: 389mm (15.32") Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: marantz-AVR serial: <filter> res: 1280x720 hz: 60 dpi: 17 size: 1872x1053mm (73.7x41.46") diag: 1630mm (64.2") modes: max: 3840x2160 min: 720x400 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.8-0ubuntu0.24.04.2 glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 9070 XT (radeonsi gfx1201 LLVM 20.1.2 DRM 3.64 7.0.0-31-generic) device-ID: 1002:7550 API: Vulkan v: 1.3.275 layers: 3 surfaces: xcb,xlib device: 0 type: discrete-gpu driver: N/A device-ID: 1002:7550 device: 1 type: integrated-gpu driver: N/A device-ID: 1002:13c0 device: 2 type: cpu driver: N/A device-ID: 10005:0000 Audio: Device-1: AMD driver: snd_hda_intel v: kernel pcie: speed: 32 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab40 class-ID: 0403 Device-2: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 7c:00.1 chip-ID: 1002:1640 class-ID: 0403 Device-3: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-6:6 chip-ID: 0b05:1b9b class-ID: 0300 Device-4: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 9-2:3 chip-ID: 046d:082d class-ID: 0102 serial: <filter> API: ALSA v: k7.0.0-31-generic status: kernel-api Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin Network: Device-1: MEDIATEK vendor: Foxconn driver: N/A pcie: speed: 8 GT/s lanes: 1 port: N/A bus-ID: 0c:00.0 chip-ID: 14c3:7927 class-ID: 0280 Device-2: Realtek vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 8 GT/s lanes: 1 port: d000 bus-ID: 0d:00.0 chip-ID: 10ec:8126 class-ID: 0200 IF: enp13s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Bluetooth: Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-5.1:7 chip-ID: 0b05:17cb class-ID: fe01 serial: <filter> Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6 sub-v: 220e hci-v: 6 rev: 15bb class-ID: 7c0104 Drives: Local Storage: total: 18.66 TiB used: 5.55 TiB (29.8%) ID-1: /dev/nvme0n1 vendor: A-Data model: SX8200PNP size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: R0906I temp: 39.9 C scheme: GPT ID-2: /dev/nvme1n1 vendor: Kingston model: SNV3S1000G size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: ETFKIN.5 temp: 46.9 C scheme: GPT ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 990 EVO Plus 2TB size: 1.82 TiB speed: 126 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QKXG7 temp: 51.9 C scheme: GPT ID-4: /dev/nvme3n1 vendor: Western Digital model: WDS100T3X0C-00SJG0 size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 111110WD temp: 55.9 C scheme: GPT ID-5: /dev/sda vendor: Seagate model: ST8000DM004-2CX188 size: 7.28 TiB type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 tech: HDD rpm: 5425 serial: <filter> fw-rev: 0214 scheme: GPT ID-6: /dev/sdb vendor: Seagate model: ST8000DM004-2CX188 size: 7.28 TiB speed: 6.0 Gb/s tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT Partition: ID-1: / size: 915.32 GiB used: 17.13 GiB (1.9%) fs: ext4 dev: /dev/nvme3n1p2 ID-2: /boot/efi size: 199.2 MiB used: 41.9 MiB (21.0%) fs: vfat dev: /dev/nvme2n1p2 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -1 file: /swapfile USB: Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-2: 2-0:1 info: super-speed hub ports: 5 rev: 3.1 speed: 20 Gb/s lanes: 2 chip-ID: 1d6b:0003 class-ID: 0900 Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-4: 3-1:2 info: VIA Labs USB2.0 Hub ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1 chip-ID: 2109:2822 class-ID: 0900 Device-1: 3-1.1:5 info: Logitech Unifying Receiver type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 98mA chip-ID: 046d:c52b class-ID: 0300 Hub-5: 3-4:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1 power: 100mA chip-ID: 174c:2074 class-ID: 0900 Hub-6: 3-5:4 info: ASMedia ASMT2307 ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1 chip-ID: 174c:2174 class-ID: 0900 Device-1: 3-5.1:7 info: ASUSTek Broadcom BCM20702A0 Bluetooth type: Bluetooth driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 100mA chip-ID: 0b05:17cb class-ID: fe01 serial: <filter> Device-2: 3-6:6 info: ASUSTek USB Audio type: audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 8 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 100mA chip-ID: 0b05:1b9b class-ID: 0300 Device-3: 3-7:8 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 16mA chip-ID: 0b05:1aa6 class-ID: 0300 serial: <filter> Hub-7: 4-0:1 info: super-speed hub ports: 5 rev: 3.1 speed: 20 Gb/s lanes: 2 chip-ID: 1d6b:0003 class-ID: 0900 Hub-8: 4-1:2 info: VIA Labs USB3.1 Hub ports: 4 rev: 3.2 speed: 10 Gb/s lanes: 1 chip-ID: 2109:0822 class-ID: 0900 Hub-9: 4-4:3 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0 speed: 5 Gb/s lanes: 1 power: 8mA chip-ID: 174c:3074 class-ID: 0900 Hub-10: 4-5:4 info: ASMedia ASMT2307 ports: 4 rev: 3.2 speed: 10 Gb/s lanes: 1 chip-ID: 174c:3174 class-ID: 0900 Device-1: 4-5.3:5 info: ASMedia ASM1051E SATA 6Gb/s bridge ASM1053E ASM1153 3Gb/s ASM1153E bridge type: mass storage driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s lanes: 1 chip-ID: 174c:55aa class-ID: 0806 serial: <filter> Device-2: 4-5.4:6 info: JMicron / USA USB Mass Storage type: mass storage driver: uas interfaces: 1 rev: 3.0 speed: 5 Gb/s lanes: 1 power: 896mA chip-ID: 152d:0577 class-ID: 0806 serial: <filter> Hub-11: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-12: 6-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 20 Gb/s lanes: 2 chip-ID: 1d6b:0003 class-ID: 0900 Hub-13: 7-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-14: 8-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900 Hub-15: 9-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-16: 9-1:2 info: Terminus Hub ports: 4 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 100mA chip-ID: 1a40:0101 class-ID: 0900 Device-1: 9-1.1:4 info: Linux Foundation Android type: abstract (modem),CDC-data driver: cdc_acm interfaces: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 500mA chip-ID: 1d6b:0106 class-ID: 0a00 serial: <filter> Device-2: 9-1.2:5 info: QinHeng UsbMonitor type: abstract (modem),CDC-data driver: cdc_acm interfaces: 2 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 500mA chip-ID: 1a86:ca21 class-ID: 0a00 serial: <filter> Device-3: 9-2:3 info: Logitech HD Pro Webcam C920 type: video,audio driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 500mA chip-ID: 046d:082d class-ID: 0102 serial: <filter> Hub-17: 10-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900 Hub-18: 11-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Sensors: System Temperatures: cpu: 54.0 C mobo: 44.0 C Fan Speeds (rpm): cpu: 0 GPU: device: amdgpu temp: 45.0 C device: amdgpu temp: 46.0 C mem: 66.0 C fan: 8 watts: 8.00 Repos: Packages: pm: dpkg pkgs: 1994 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/danielrichter2007-grub-customizer-noble.list 1: deb [signed-by=/etc/apt/keyrings/danielrichter2007-grub-customizer-noble.gpg] https: //ppa.launchpadcontent.net/danielrichter2007/grub-customizer/ubuntu noble main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com zena main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu noble main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu noble-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu noble-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ noble-security main restricted universe multiverse Active apt repos in: /etc/apt/sources.list.d/google-chrome.sources 1: deb [arch=amd64] https: //dl.google.com/linux/chrome-stable/deb/ stable main Info: Memory: total: 32 GiB note: est. available: 30.51 GiB used: 2.97 GiB (9.7%) Processes: 558 Power: uptime: 13m states: freeze,mem suspend: deep wakeups: 0 hibernate: disabled Init: systemd v: 255 target: graphical (5) default: graphical Compilers: gcc: 13.3.0 Client: Unknown python3.12 client inxi: 3.3.34 [/code] --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-09-07 (2 days ago) InstallationMedia: Linux Mint 22.2 "Zara" - Release amd64 20250828 IwConfig: lo no wireless extensions. enp13s0 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=3b7346f3-dda3-4267-9f76-779cee3c97d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-31-generic N/A linux-backports-modules-7.0.0-31-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: zena Uname: Linux 7.0.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 07/13/2026 dmi.bios.release: 24.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870E-E GAMING 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.:bvr2402:bd07/13/2026:br24.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870E-EGAMINGWIFI: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 --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-09-07 (2 days ago) InstallationMedia: Linux Mint 22.2 "Zara" - Release amd64 20250828 IwConfig: lo no wireless extensions. enp13s0 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=3b7346f3-dda3-4267-9f76-779cee3c97d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-31-generic N/A linux-backports-modules-7.0.0-31-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: zena Uname: Linux 7.0.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 07/13/2026 dmi.bios.release: 24.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870E-E GAMING 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.:bvr2402:bd07/13/2026:br24.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870E-EGAMINGWIFI: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 --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-09-07 (2 days ago) InstallationMedia: Linux Mint 22.2 "Zara" - Release amd64 20250828 IwConfig: lo no wireless extensions. enp13s0 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=3b7346f3-dda3-4267-9f76-779cee3c97d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-31-generic N/A linux-backports-modules-7.0.0-31-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: zena Uname: Linux 7.0.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 07/13/2026 dmi.bios.release: 24.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870E-E GAMING 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.:bvr2402:bd07/13/2026:br24.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870E-EGAMINGWIFI: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/2166710/+subscriptions
[Bug 2166130] Re: Bluetooth Issue
Jason, we have some more recent builds of the kernel available for debugging purposes. The documentation on how to install them is here: https://wiki.ubuntu.com/Kernel/MainlineBuilds Could you follow those instructions to install the mainline 7.3 kernel and see if the problem persists? You can download it here: https://kernel.ubuntu.com/mainline/v7.3-rc1/ Thanks. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166130 Title: Bluetooth Issue Status in linux package in Ubuntu: Triaged Bug description: btintel_pcie: Lunar Lake Bluetooth controller enters error state after firmware load (regression 7.0.0-28 → 7.0.0-29) Summary Intel Bluetooth (PCI ID 8086:A876) on Lenovo Yoga 9 14ILL10 (Lunar Lake) fails to initialize on kernels 7.0.0-29-generic and 7.0.0-30 generic. The btintel_pcie driver successfully loads both firmware stages (IML and PCI transport), but the controller enters an error state during the post-firmware reset. The “alive interrupt” times out and Intel Soft Reset fails with -ETIME (-62). Bluetooth worked correctly on kernel 7.0.0-28-generic with the same firmware files. The regression was introduced in 7.0.0-29. Steps to Reproduce Boot Lenovo Yoga 9 14ILL10 (model 83LC) with kernel 7.0.0-29-generic or 7.0.0-30-generic Bluetooth controller fails to initialize — bluetoothctl show reports “No default controller available” Expected Behavior Bluetooth controller initializes successfully (as it did on kernel 7.0.0-28-generic). Actual Behavior hciconfig shows hci0 with BD Address 00:00:00:00:00:00, state DOWN, 5 TX errors. bluetoothctlcontroller available.” Driver unbind/rebind reproduces the same failure — not a transient boot issue. show reports “No default System Information Distro: Ubuntu 26.04 (Resolute) Working kernel: 7.0.0-28-generic (confirmed working Aug 2–10, 2026) Broken kernels: 7.0.0-29-generic (7.0.0-29.29) and 7.0.0-30-generic (7.0.0-30.30) Machine: Lenovo Yoga 9 2-in-1 14ILL10, model 83LC SoC: Intel Lunar Lake BIOS: Q9CN22WW (01/09/2025) BT device: PCI 8086:A876, subsystem 8086:000E Driver: btintel_pcie (in-tree, /lib/modules/7.0.0-30-generic/kernel/drivers/bluetooth/btintel_pcie.ko.zst) Firmware: intel/ibt-0190-0291-iml.sfi + intel/ibt-0190-0291-pci.sfi (Firmware Version 107-8.26) linux-firmware: 20260319.git217ca6e4.1ubuntu Kernel Log (dmesg, annotated) Stage 1 — IML firmware: SUCCESS Bluetooth: hci0: Device revision is 0 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is disabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995 Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi Bluetooth: hci0: Boot Address: 0x30098800 Bluetooth: hci0: Firmware Version: 107-8.26 Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 60577 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 2195 usecs Bluetooth: hci0: Waiting for device transition to d0 Bluetooth: hci0: Device moved to D0 in 0 usecs Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b Stage 2 — PCI transport firmware: FAILURE Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfiBluetooth: hci0: Boot Address: 0x10000800 Bluetooth: hci0: Firmware Version: 107-8.26 Bluetooth: hci0: Received gp1 mailbox interrupt ← repeated ~36 times Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 579658 usecs ← much slower than IML stage Bluetooth: hci0: Received gp1 mailbox interrupt Bluetooth: hci0: Controller in error state ← FAILURE POINT Bluetooth: hci0: Timeout (3000 ms) on alive interrupt, alive context: intel_reset1 Bluetooth: hci0: Failed to send frame (-62) Bluetooth: hci0: sending frame failed (-62) Bluetooth: hci0: Failed to send Intel Reset command Bluetooth: hci0: Intel Soft Reset failed (-62) Retry attempt: SAME FAILURE Bluetooth: hci0: Firmware download retry count: 1 [...IML firmware loads again successfully...] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfi Bluetooth: hci0: Firmware loaded in 1033894 usecs Bluetooth: hci0: Controller in error state Bluetooth: hci0: Timeout (3000 ms) on alive interrupt, alive context: intel_reset1 Bluetooth: hci0: Intel Soft Reset failed (-62) Bluetooth: hci0: Received hw exception interrupt Bluetooth: hci0: Unsupported cnvi 0x00000000 ← hardware ID unreadable Bluetooth: hci0: Controller in error state Bluetooth: hci0: Failed to read MSFT supported features (-62) Comparison — working boot on 7.0.0-28 (May 29, 2026) Bluetooth: hci0: Device booted in 35237 usecs Bluetooth: hci0: Device moved to D0 in 51 usecs Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0190-0291-pci.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware timestamp 2025.25 buildtype 1 build 95112 Bluetooth: hci0: Firmware SHA1: 0x73cbad49 Bluetooth: hci0: Fseq status: Success (0x00) Bluetooth: hci0: Fseq executed: 00.00.04.202 Bluetooth: hci0: Fseq BT Top: 00.00.04.197 Additional Context rfkill reports Bluetooth as not blocked (soft or hard) The same failure reproduces after manual driver unbind/rebind (not a race condition at boot) A systemd sleep hook (/usr/lib/systemd/system-sleep/bluetooth-wakeup-fix) unbinds/rebinds this device around s2idle to prevent spurious wakeups — this is unrelated to the failure (the failure occurs on fresh boot before any sleep cycle) Kernel 7.0.0-29-generic tested and confirmed broken — same failure as 7.0.0-30 Regression bisected to the 7.0.0-28 → 7.0.0-29 kernel transition ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jkredfoot 6048 F.... pipewire jkredfoot 6063 F.... wireplumber /dev/snd/seq: jkredfoot 6048 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 22:36:48 2026 InstallationDate: Installed on 2026-02-16 (198 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: LENOVO 83LC ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=ff800d1a-2b21-4bc4-a94c-5194f1b6a033 ro quiet splash snd_sof.sof_debug=0x1 snd_soc_sof_sdw.dyndbg=+p 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-05-14 (110 days ago) dmi.bios.date: 01/09/2025 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: Q9CN22WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 2-in-1 14ILL10 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrQ9CN22WW:bd01/09/2025:br1.22:efr1.22:svnLENOVO:pn83LC:pvrYoga92-in-114ILL10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct31:cvrYoga92-in-114ILL10:skuLENOVO_MT_83LC_BU_idea_FM_Yoga92-in-114ILL10:pfaYoga92-in-114ILL10: dmi.product.family: Yoga 9 2-in-1 14ILL10 dmi.product.name: 83LC dmi.product.sku: LENOVO_MT_83LC_BU_idea_FM_Yoga 9 2-in-1 14ILL10 dmi.product.version: Yoga 9 2-in-1 14ILL10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166130/+subscriptions
[Bug 2165844] Re: linux 7.0.0-30: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end() on ntfs3 buffered write
Indeed, the fix commit does seem promising. It helps the kernel team to have confirmation via a test that the problem is actually fixed rather than speculating. So if Artem is able to confirm for us that the bug goes away, that should help speed up the process of getting the fix into the kernel :-) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165844 Title: linux 7.0.0-30: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end() on ntfs3 buffered write Status in linux package in Ubuntu: Confirmed Bug description: [Summary] Any buffered write() to an ntfs3-mounted volume can hit a BUG_ON in the generic iomap write path and panic the kernel. An unprivileged process (rsync, uid 1000) took the whole machine down; the system froze instantly, then kdump rebooted into the capture kernel. [Impact] This is reachable from unprivileged userspace with a plain write(2) syscall. Whatever the state of the NTFS volume, the correct outcome is -EIO returned to the caller, not a kernel panic. Reproducing it needs nothing but a writable NTFS mount, which udisks/GNOME Files creates by default when a user clicks a Windows partition. [Environment] Ubuntu 26.04, linux-image-7.0.0-30-generic 7.0.0-30.30, x86_64 ASUS ROG STRIX B550-XE GAMING WIFI, BIOS 3607 NTFS volume: 1.8 TB Windows system partition, mounted read-write by udisks (driver ntfs3, POSIX ACLs enabled) [What happened] Writing to the NTFS mount, the kernel hit the assertion and died: kernel BUG at fs/iomap/buffered-io.c:1061! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 2 UID: 1000 PID: 18561 Comm: rsync Kdump: loaded Tainted: G O Hardware name: ASUS System Product Name/ROG STRIX B550-XE GAMING WIFI RIP: 0010:iomap_write_end+0x1e0/0x1f0 Call Trace: iomap_write_iter+0x171/0x340 iomap_file_buffered_write+0xa6/0x110 ntfs_file_write_iter+0x267/0x310 [ntfs3] vfs_write+0x25b/0x490 ksys_write+0x71/0xf0 __x64_sys_write+0x19/0x30 do_syscall_64+0x105/0x5a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The faulting syscall was a 137-byte write(2) to fd 1 (ORIG_RAX 0x1, RDX 0x89) — an ordinary small buffered write, not anything exotic. The G/O taint is the out-of-tree NVIDIA module (595.84). It is unrelated to this code path; ntfs3, iomap and the write path are all in-tree. [Preceding symptom] About 14 minutes before the panic, ntfs3 logged a large burst of metadata repairs on the same volume: ntfs3(nvme0n1p2): ino=..., Correct links count -> N ntfs3: 15286 callbacks suppressed So the volume was not perfectly clean. That may well be what steers the write path into the bad state — but an inconsistent filesystem must not be able to panic the kernel, so it looks like a missing error path rather than a disk problem. [Reproducer] Not deterministic here, but the shape is simple: 1. Mount an NTFS volume read-write with ntfs3 (udisksctl mount is enough). 2. Run sustained buffered I/O against it (rsync of a large tree). The other reports linked below describe the same trace from ordinary file writes, including games writing save data. [Already reported elsewhere] Same trace, same line, on 7.0.x kernels since roughly April 2026: - https://github.com/CachyOS/linux-cachyos/issues/841 - https://discuss.cachyos.org/t/kernel-bug-in-iomap-write-end-triggered-by-ntfs3-buffered-write-linux-7-0-1-cachyos/28546 - https://bbs.archlinux.org/viewtopic.php?pid=2296728 - https://forum.manjaro.org/t/total-system-hangs-and-fs-iomap-kernel-panic-on-7-0-10-stable-on-6-18-lts/188283 I could not find an upstream fix. Upstream appears to be replacing ntfs3 with the new ntfsplus driver in 7.1 rather than fixing this one. [Suggestion for Ubuntu] Since 26.04 ships 7.0 and a user can trigger a kernel panic by copying files onto a Windows partition from the file manager, it may be worth either backporting a fix or having udisks default NTFS mounts to read-only until 7.1 lands via HWE. [Attached] Full kernel ring buffer from the kdump vmcore (VmCoreDmesg), plus the usual apport-collected hardware and package data. Sanitisation applied before upload: firewall log lines were dropped, and MAC addresses, the wireless BSSID/SSID and LAN IPv4 addresses were replaced with placeholders in VmCoreDmesg, CurrentDmesg and WifiSyslog. Nothing else was altered; the panic trace is untouched. An incomplete vmcore (2.3 GB, truncated because the machine was power-cycled during the dump) is available if it would help. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 11:45:03 2026 InstallationDate: Installed on 2026-07-12 (49 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS System Product Name PackageArchitecture: amd64 ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=5778b2dd-b496-4525-b52f-223e5be557bc ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux Title: linux 7.0.0-30: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end() on ntfs3 buffered write UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 03/18/2024 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3607 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-XE GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3607:bd03/18/2024:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-XEGAMINGWIFI:rvrRevX.0x: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/2165844/+subscriptions