[Bug 2166648] Re: After upgrade from 6.8.0-137 to 6.8.0-139 bluetooth does not work and suspend is unreliable

** 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/2166648 Title: After upgrade from 6.8.0-137 to 6.8.0-139 bluetooth does not work and suspend is unreliable Status in linux package in Ubuntu: Confirmed Bug description: Following the kernel update from 6.8.0-137 to 6.8.0-139, my bluetooth mouse does not work and suspend occasionally fails to restore a graphical session. I've resorted to using the USB mouse dongle to work around the lack of bluetooth - it's visible in lsusb. This fragment from journalctl might be related the bluetooth issue: ```text Sep 07 07:36:34 PiMutant kernel: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 Sep 07 07:36:34 PiMutant kernel: BUG: kernel NULL pointer dereference, address: 0000000000000219 Sep 07 07:36:34 PiMutant kernel: #PF: supervisor read access in kernel mode Sep 07 07:36:34 PiMutant kernel: #PF: error_code(0x0000) - not-present page Sep 07 07:36:34 PiMutant kernel: PGD 0 P4D 0 Sep 07 07:36:34 PiMutant kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Sep 07 07:36:34 PiMutant kernel: CPU: 6 PID: 174 Comm: kworker/u35:0 Not tainted 6.8.0-139-generic #139-Ubuntu Sep 07 07:36:34 PiMutant kernel: Hardware name: ASUSTeK COMPUTER INC. ROG Strix G513IH_G513IH/G513IH, BIOS G5> Sep 07 07:36:34 PiMutant kernel: Workqueue: hci0 hci_power_on [bluetooth] Sep 07 07:36:34 PiMutant kernel: RIP: 0010:__pm_runtime_resume+0x1b/0x80 Sep 07 07:36:34 PiMutant kernel: Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e> Sep 07 07:36:34 PiMutant kernel: RSP: 0018:ffffd3bc40733b30 EFLAGS: 00010246 Sep 07 07:36:34 PiMutant kernel: RAX: ffff8c7b032494d0 RBX: 0000000000000050 RCX: 0000000000000000 Sep 07 07:36:34 PiMutant kernel: RDX: 0000000000000015 RSI: 0000000000000000 RDI: 0000000000000050 Sep 07 07:36:34 PiMutant kernel: RBP: ffffd3bc40733b50 R08: 0183400090000000 R09: 000000ffffffff00 Sep 07 07:36:34 PiMutant kernel: R10: ffffffff00018340 R11: 0000000200000000 R12: 0000000000000004 Sep 07 07:36:34 PiMutant kernel: R13: 0000000000000035 R14: 000000000000003a R15: ffffd3bc40733be8 Sep 07 07:36:34 PiMutant kernel: FS: 0000000000000000(0000) GS:ffff8c7be7500000(0000) knlGS:0000000000000000 Sep 07 07:36:34 PiMutant kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 07 07:36:34 PiMutant kernel: CR2: 0000000000000219 CR3: 0000000114c38000 CR4: 0000000000350ef0 Sep 07 07:36:34 PiMutant kernel: Call Trace: Sep 07 07:36:34 PiMutant kernel: <TASK> Sep 07 07:36:34 PiMutant kernel: usb_autopm_get_interface+0x1d/0x60 Sep 07 07:36:34 PiMutant kernel: btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] Sep 07 07:36:34 PiMutant kernel: ? __pfx_btmtk_usb_hci_wmt_sync+0x10/0x10 [btmtk] Sep 07 07:36:34 PiMutant kernel: btmtk_setup_firmware_79xx+0x1ca/0x360 [btmtk] Sep 07 07:36:34 PiMutant kernel: btusb_mtk_setup+0x453/0x610 [btusb] Sep 07 07:36:34 PiMutant kernel: hci_dev_setup_sync+0x6f/0x430 [bluetooth] Sep 07 07:36:34 PiMutant kernel: ? __pm_runtime_idle+0x4c/0xd0 Sep 07 07:36:34 PiMutant kernel: hci_dev_init_sync+0x3e/0x1c0 [bluetooth] Sep 07 07:36:34 PiMutant kernel: hci_dev_open_sync+0xb1/0x350 [bluetooth] Sep 07 07:36:34 PiMutant kernel: ? srso_return_thunk+0x5/0x5f Sep 07 07:36:34 PiMutant kernel: hci_dev_do_open+0x28/0x70 [bluetooth] Sep 07 07:36:34 PiMutant kernel: hci_power_on+0x50/0x210 [bluetooth] Sep 07 07:36:34 PiMutant kernel: ? srso_return_thunk+0x5/0x5f Sep 07 07:36:34 PiMutant kernel: ? __try_to_del_timer_sync+0x5f/0xa0 Sep 07 07:36:34 PiMutant kernel: process_one_work+0x184/0x3a0 Sep 07 07:36:34 PiMutant kernel: worker_thread+0x18b/0x330 Sep 07 07:36:34 PiMutant kernel: ? __pfx_worker_thread+0x10/0x10 Sep 07 07:36:34 PiMutant kernel: kthread+0xf2/0x120 Sep 07 07:36:34 PiMutant kernel: ? __pfx_kthread+0x10/0x10 Sep 07 07:36:34 PiMutant kernel: ret_from_fork+0x47/0x70 Sep 07 07:36:34 PiMutant kernel: ? __pfx_kthread+0x10/0x10 Sep 07 07:36:34 PiMutant kernel: ret_from_fork_asm+0x1b/0x30 Sep 07 07:36:34 PiMutant kernel: </TASK> Sep 07 07:36:34 PiMutant kernel: Modules linked in: snd_hda_intel btusb snd_intel_dspcfg snd_compress mt7921e> Sep 07 07:36:34 PiMutant kernel: raid6_pq libcrc32c nvme crct10dif_pclmul crc32_pclmul hid_multitouch polyva> Sep 07 07:36:34 PiMutant kernel: CR2: 000000000000021 Sep 07 07:36:34 PiMutant kernel: RIP: 0010:__pm_runtime_resume+0x1b/0x80 Sep 07 07:36:34 PiMutant kernel: Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e> Sep 07 07:36:34 PiMutant kernel: RSP: 0018:ffffd3bc40733b30 EFLAGS: 00010246 Sep 07 07:36:34 PiMutant kernel: RAX: ffff8c7b032494d0 RBX: 0000000000000050 RCX: 0000000000000000 Sep 07 07:36:34 PiMutant kernel: RDX: 0000000000000015 RSI: 0000000000000000 RDI: 0000000000000050 Sep 07 07:36:34 PiMutant kernel: RBP: ffffd3bc40733b50 R08: 0183400090000000 R09: 000000ffffffff00 Sep 07 07:36:34 PiMutant kernel: R10: ffffffff00018340 R11: 0000000200000000 R12: 0000000000000004 Sep 07 07:36:34 PiMutant kernel: R13: 0000000000000035 R14: 000000000000003a R15: ffffd3bc40733be8 Sep 07 07:36:34 PiMutant kernel: FS: 0000000000000000(0000) GS:ffff8c7be7500000(0000) knlGS:0000000000000000 Sep 07 07:36:34 PiMutant kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 07 07:36:34 PiMutant kernel: CR2: 0000000000000219 CR3: 0000000114c38000 CR4: 0000000000350ef0 Sep 07 07:36:34 PiMutant kernel: note: kworker/u35:0[174] exited with irqs disabled ``` 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: lizsquir 1693 F.... wireplumber  /dev/snd/controlC1: lizsquir 1693 F.... wireplumber  /dev/snd/controlC0: lizsquir 1693 F.... wireplumber  /dev/snd/seq: lizsquir 1691 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Sep 7 08:35:02 2026 InstallationDate: Installed on 2022-02-19 (1661 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513IH_G513IH ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.8.0-139-generic root=UUID=89499276-dfdf-480a-852c-cbefef738a2d ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:  linux-restricted-modules-6.8.0-139-generic N/A  linux-backports-modules-6.8.0-139-generic N/A  linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-08-30 (738 days ago) dmi.bios.date: 01/27/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513IH.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513IH 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: 0.52 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513IH.301:bd01/27/2021:br5.16:efr0.52:svnASUSTeKCOMPUTERINC.:pnROGStrixG513IH_G513IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513IH_G513IH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166648/+subscriptions

[Bug 2166715] [NEW] Clocksource watchdog intermittently demotes TSC to HPET on Ryzen 7 5700G with constant_tsc + nonstop_tsc

Public bug reported: On an ASUS ROG STRIX G10DK (AMD Ryzen 7 5700G), the kernel's clocksource watchdog marks the TSC unstable at boot and falls back to HPET — but only on *some* boots. The same kernel, unchanged configuration, boots to `tsc` other times. It behaves like a race against the machine still settling: the skew is measured about 2.1 s into boot. ``` [ 1.477709] clocksource: Switched to clocksource tsc [ 2.109340] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 2.109345] clocksource: 'hpet' wd_nsec: 499479123 wd_now: 1b9c972 wd_last: 14ca962 [ 2.109348] clocksource: 'tsc' cs_nsec: 495996007 cs_now: 19355aab4a cs_last: 18c439320a [ 2.109351] clocksource: Clocksource 'tsc' skewed -3483116 ns (-3 ms) over watchdog 'hpet' interval of 499479123 ns (499 ms) [ 2.109358] tsc: Marking TSC unstable due to clocksource watchdog [ 2.109365] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 2.109494] clocksource: Switched to clocksource hpet ``` The CPU advertises `constant_tsc`, `nonstop_tsc` and `rdtscp`, i.e. an invariant TSC. **Observed across kernels — this is not a regression in any one version:** | date | kernel | resulting clocksource | |---|---|---| | 2026-07-22/23 | 7.0.0-28, 6.17.0-40, 6.8.0-136 | tsc ×8, hpet ×4 | | 2026-07-30 | 6.8.0-136 | hpet | | 2026-08-06 | 6.8.0-137 | hpet | | 2026-08-18 | 6.8.0-138 | hpet | | 2026-08-26 | 6.8.0-138 | tsc | | 2026-09-06 | 6.8.0-139 | hpet | | 2026-09-07 | 6.8.0-139 | tsc | | 2026-09-07 | 7.0.0-31 | hpet | **Impact:** This is not cosmetic. With HPET, `clock_gettime` stops being served from the vDSO and becomes a syscall with an MMIO hardware read. Measured on this machine, 200,000 iterations: - `hpet`: **1522 ns** per call - `tsc`: **103 ns** per call Any application that queries time frequently pays ~15× more. In my case Thunderbird 155 became completely unusable — its UI thread issues ~21,000 `clock_gettime`/s and saturated a core, with menus refusing to open. The same Thunderbird on the same profile runs at ~10% CPU once the clocksource is `tsc`. Because the demotion is intermittent, the resulting symptom looks random and gets misattributed to whatever application happens to notice it first. **Workaround:** `tsc=reliable` on the kernel command line. After that the machine boots to `tsc` every time and the symptom is gone. **Suggestion:** The kernel's own message points at the BIOS, and that may well be correct — but this board's last BIOS is from 2022-12-14 and the vendor has published nothing since, so there is no firmware fix available. Given the CPU declares an invariant TSC, it may be worth either running the watchdog later in boot, or being less eager to demote on CPUs that advertise `constant_tsc` + `nonstop_tsc`. **System:** Ubuntu 24.04.4 · ASUS ROG STRIX G10DK, BIOS 310 (2022-12-14) · AMD Ryzen 7 5700G ** 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/2166715 Title: Clocksource watchdog intermittently demotes TSC to HPET on Ryzen 7 5700G with constant_tsc + nonstop_tsc Status in linux package in Ubuntu: New Bug description: On an ASUS ROG STRIX G10DK (AMD Ryzen 7 5700G), the kernel's clocksource watchdog marks the TSC unstable at boot and falls back to HPET — but only on *some* boots. The same kernel, unchanged configuration, boots to `tsc` other times. It behaves like a race against the machine still settling: the skew is measured about 2.1 s into boot. ``` [ 1.477709] clocksource: Switched to clocksource tsc [ 2.109340] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 2.109345] clocksource: 'hpet' wd_nsec: 499479123 wd_now: 1b9c972 wd_last: 14ca962 [ 2.109348] clocksource: 'tsc' cs_nsec: 495996007 cs_now: 19355aab4a cs_last: 18c439320a [ 2.109351] clocksource: Clocksource 'tsc' skewed -3483116 ns (-3 ms) over watchdog 'hpet' interval of 499479123 ns (499 ms) [ 2.109358] tsc: Marking TSC unstable due to clocksource watchdog [ 2.109365] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 2.109494] clocksource: Switched to clocksource hpet ``` The CPU advertises `constant_tsc`, `nonstop_tsc` and `rdtscp`, i.e. an invariant TSC. **Observed across kernels — this is not a regression in any one version:** | date | kernel | resulting clocksource | |---|---|---| | 2026-07-22/23 | 7.0.0-28, 6.17.0-40, 6.8.0-136 | tsc ×8, hpet ×4 | | 2026-07-30 | 6.8.0-136 | hpet | | 2026-08-06 | 6.8.0-137 | hpet | | 2026-08-18 | 6.8.0-138 | hpet | | 2026-08-26 | 6.8.0-138 | tsc | | 2026-09-06 | 6.8.0-139 | hpet | | 2026-09-07 | 6.8.0-139 | tsc | | 2026-09-07 | 7.0.0-31 | hpet | **Impact:** This is not cosmetic. With HPET, `clock_gettime` stops being served from the vDSO and becomes a syscall with an MMIO hardware read. Measured on this machine, 200,000 iterations: - `hpet`: **1522 ns** per call - `tsc`: **103 ns** per call Any application that queries time frequently pays ~15× more. In my case Thunderbird 155 became completely unusable — its UI thread issues ~21,000 `clock_gettime`/s and saturated a core, with menus refusing to open. The same Thunderbird on the same profile runs at ~10% CPU once the clocksource is `tsc`. Because the demotion is intermittent, the resulting symptom looks random and gets misattributed to whatever application happens to notice it first. **Workaround:** `tsc=reliable` on the kernel command line. After that the machine boots to `tsc` every time and the symptom is gone. **Suggestion:** The kernel's own message points at the BIOS, and that may well be correct — but this board's last BIOS is from 2022-12-14 and the vendor has published nothing since, so there is no firmware fix available. Given the CPU declares an invariant TSC, it may be worth either running the watchdog later in boot, or being less eager to demote on CPUs that advertise `constant_tsc` + `nonstop_tsc`. **System:** Ubuntu 24.04.4 · ASUS ROG STRIX G10DK, BIOS 310 (2022-12-14) · AMD Ryzen 7 5700G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166715/+subscriptions

[Bug 2166700] Re: Bluetooth won't start after upgrading Ubuntu kernel to 139

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166700 Title: Bluetooth won't start after upgrading Ubuntu kernel to 139 Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu kernel to 6.8.0-139-generic and after reboot i am unable to start my Bluetooth on my Asus F15-FX506HC laptop. Nothing i try works, only reverting to 138 fixes the issue. Please look into that I am attaching journalctl output presiyan@F15-FX506HC:~$ journalctl -b -k --no-pager | grep -iE 'Bluetooth|btmtk|btusb|hci0|Oops|NULL pointer|BUG:' | tee ~/bt-139-kernel.log Sep 07 18:15:37 F15-FX506HC kernel: Bluetooth: Core ver 2.22 Sep 07 18:15:37 F15-FX506HC kernel: NET: Registered PF_BLUETOOTH protocol family Sep 07 18:15:37 F15-FX506HC kernel: Bluetooth: HCI device and connection manager initialized Sep 07 18:15:37 F15-FX506HC kernel: Bluetooth: HCI socket layer initialized Sep 07 18:15:37 F15-FX506HC kernel: Bluetooth: L2CAP socket layer initialized Sep 07 18:15:37 F15-FX506HC kernel: Bluetooth: SCO socket layer initialized Sep 07 18:15:38 F15-FX506HC kernel: usbcore: registered new interface driver btusb Sep 07 18:15:38 F15-FX506HC kernel: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 Sep 07 18:15:38 F15-FX506HC kernel: BUG: kernel NULL pointer dereference, address: 0000000000000219 Sep 07 18:15:38 F15-FX506HC kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Sep 07 18:15:38 F15-FX506HC kernel: Workqueue: hci0 hci_power_on [bluetooth] Sep 07 18:15:38 F15-FX506HC kernel: btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] Sep 07 18:15:38 F15-FX506HC kernel: ? __pfx_btmtk_usb_hci_wmt_sync+0x10/0x10 [btmtk] Sep 07 18:15:38 F15-FX506HC kernel: btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] Sep 07 18:15:38 F15-FX506HC kernel: btusb_mtk_setup+0x453/0x610 [btusb] Sep 07 18:15:38 F15-FX506HC kernel: hci_dev_setup_sync+0x6c/0x430 [bluetooth] Sep 07 18:15:38 F15-FX506HC kernel: hci_dev_init_sync+0x3e/0x1c0 [bluetooth] Sep 07 18:15:38 F15-FX506HC kernel: hci_dev_open_sync+0xb1/0x350 [bluetooth] Sep 07 18:15:38 F15-FX506HC kernel: hci_dev_do_open+0x28/0x70 [bluetooth] Sep 07 18:15:38 F15-FX506HC kernel: hci_power_on+0x50/0x210 [bluetooth] Sep 07 18:15:38 F15-FX506HC kernel: Modules linked in: snd_usb_audio(+) snd_pcm_dmaengine mt76_connac_lib btusb irqbypass btrtl snd_hda_intel mt76 crct10dif_pclmul btintel snd_intel_dspcfg polyval_clmulni snd_usbmidi_lib btbcm snd_intel_sdw_acpi polyval_generic btmtk snd_ump ghash_clmulni_intel snd_hda_codec snd_seq_midi nouveau(+) mac80211 sha256_ssse3 snd_seq_midi_event cmdlinepart bluetooth snd_hda_core uvcvideo spi_nor sha1_ssse3 snd_rawmidi videobuf2_vmalloc aesni_intel uvc videobuf2_memops videobuf2_v4l2 snd_hwdep asus_nb_wmi mfd_aaeon crypto_simd ee1004 mtd mei_hdcp mei_pxp intel_rapl_msr cryptd ecdh_generic videodev snd_seq asus_wmi mxm_wmi ecc rapl cfg80211 snd_pcm ledtrig_audio videobuf2_common i2c_i801 platform_profile drm_gpuvm spi_intel_pci snd_seq_device intel_cstate wmi_bmof i915(+) mc spi_intel libarc4 i2c_smbus snd_timer drm_exec mei_me snd gpu_sched mei processor_thermal_device_pci_legacy soundcore drm_ttm_helper processor_thermal_device drm_buddy processor_thermal_wt_hint ttm processor_thermal_rfim processor_thermal_rapl Sep 07 18:15:38 F15-FX506HC kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Sep 07 18:15:38 F15-FX506HC kernel: Bluetooth: BNEP filters: protocol multicast Sep 07 18:15:38 F15-FX506HC kernel: Bluetooth: BNEP socket layer initialized 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 ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: presiyan 3076 F.... wireplumber /dev/snd/controlC1: presiyan 3076 F.... wireplumber /dev/snd/controlC0: presiyan 3076 F.... wireplumber /dev/snd/seq: presiyan 3072 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 18:16:43 2026 InstallationDate: Installed on 2023-12-27 (985 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506HC_FX506HC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=a5e9d595-c55d-467f-9724-ea5097813566 ro quiet splash pcie_aspm=off rfkill.default_state=1 asus_wmi.fnlock_default=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2025 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FX506HC.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506HC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HC.316:bd06/17/2025:br5.19:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HC_FX506HC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506HC_FX506HC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166700/+subscriptions

Re: [Bug 2166325] Re: Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 causes NVMe completion stalls

Thanks for confirming this. I can also confirm that the equivalent interrupt-ordering workaround works on Ubuntu 26.04.1 with 7.0.0-31-generic on my MSI Vector with Intel VMD 8086:ad0b (Arrow Lake-HX). I am currently running 7.0.0-31-generic with the patched VMD module via DKMS. The recurring nvme: I/O ... timeout, completion polled events are gone and NVMe performance is normal. My original workaround was developed for 8086:ad0b / ARL004 and performs the same essential operation: a PCI configuration-space read from the MSI-initiating NVMe device before dispatching the child interrupt. So we now have successful results on both 8086:7d0b and 8086:ad0b under Ubuntu kernel 7.0.0-31-generic. С уважением Владимир Недошивин Tel: +79656931076 > > Вторник, 8 сентября 2026, 00:00 +04:00 от Stas Safari <2166325@bugs.launchpad.net > >: > Confirming the same issue on an Arrow Lake laptop with VMD 8086:7d0b > (Ubuntu 26.04.1, kernel 7.0.0-31-generic): frequent "nvme: I/O ... > timeout, completion polled" events causing 30 s – 2 min application > stalls. APST off, C-state limits, kernel/BIOS/firmware updates did not > help. > > Applying Rickey Bartlett's "PCI: vmd: Flush initiator posted writes before > demuxing interrupts on Meteor Lake" (pci.git controller/vmd) to Ubuntu's > vmd.c via DKMS fixed it completely: 0 events, I/O pressure from ~40% to > ~0%. Please consideran SRU cherry-pick for 7.0.x. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2166325 > > Title: > Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 > causes NVMe completion stalls > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hardware > ======== > > Laptop: MSI Vector 17 HX AI > Platform: Intel Arrow Lake > Intel VMD: 8086:ad0b > VMD PCI address: 0000:00:0e.0 > Subsystem: 1462:149c > > Internal NVMe SSD: > Phison 1TB ESR01TBYCCA4-EDJ-2MS > Controller: Phison PS5029-E29T PCIe 4.0 NVMe > PCI ID: 1987:5029 (rev 01) > Firmware: ETFM50.0 > > Ubuntu: 26.04 > Current/final tested kernel: 7.0.0-30-generic > Secure Boot: enabled > > > Problem 1: Intel VMD Bus Offset 3 > ================================ > > With the stock Ubuntu VMD driver the internal NVMe SSD is not exposed. > > The kernel reports: > > vmd 0000:00:0e.0: Unknown Bus Offset Setting (3) > > and no internal /dev/nvme* device is available. > > Linux 6.14 was also tested on this machine and did not solve the VMD > problem. > > The system firmware does not expose a usable BIOS option to disable Intel > VMD/RST. > > Intel's public VMD second-rootbus patch series was integrated into the > Ubuntu VMD source: > > [PATCH v3 0/8] VMD add second rootbus support > > https://www.spinics.net/lists/linux-pci/msg163096.html > > After integrating the second-rootbus support, Linux successfully > enumerates > the internal NVMe controller and SSD. > > > Problem 2: NVMe completion stalls > ================================= > > After the SSD became accessible through the modified VMD driver, a second > problem became visible. > > Kernel messages repeatedly contained: > > nvme nvme0: I/O tag ... timeout, completion polled > > The stalls occurred at approximately 30-second intervals. > > A diagnostic sequential read before the workaround: > > sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 > status=progress > > Result: > > 1 GiB in approximately 121.339 seconds > approximately 8.8 MB/s > > CPU and memory were not saturated. > > Disabling ASPM was tested and did not solve the problem. > > > ARL004 investigation > ==================== > > The official Intel RST/VMD Windows driver distributed by MSI for this > machine was examined by static analysis for comparison. > > The relevant Windows driver path performs a PCI configuration-space read > after MSI handling when the completion state requires ordering. > > This behavior is consistent with the Intel Arrow Lake ARL004 erratum, > where > an MSI from a VMD-owned device may pass a preceding memory write. > > An experimental Linux workaround was implemented for the tested > 8086:ad0b VMD/NVMe path. It performs a dummy PCI configuration-space read > before the subsequent interrupt handling path. > > > Result > ====== > > With the experimental ARL004 workaround: > > sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 > status=progress > > completed in: > > 1 GiB in 0.88206 seconds > approximately 1.2 GB/s > > A subsequent 10 GiB sequential diagnostic read also completed > normally. > > After booting with the final tested module: > > sudo journalctl -k -b | grep -E 'timeout|completion polled' > > produced no matching messages. > > The approximately 136x difference above is only a diagnostic comparison on > > this specific machine and is not intended as a general SSD benchmark. > > > Reproduction / reference implementation > ======================================= > > The complete investigation, tested source, separate patches, combined > patch, > known-working module, SHA256 checksums, installation/bootstrap procedure > and > recovery procedure are published here: > > https://github.com/gvozd188/vmd-arl004 > > Exact reference commit: > > https://github.com/gvozd188/vmd-arl004/commit/5438c83 > > Relevant files: > > 0001-vmd-second-rootbus-intel.patch > Integration of Intel's second-rootbus support. > > 0002-vmd-ad0b-arl004-workaround.patch > Experimental ARL004 workaround. > > vmd-arl004.patch > Combined patch. > > vmd-ubuntu-7.0.0-30.c > Ubuntu VMD source used as the patch base. > > vmd.c > Final tested source. > > vmd.ko > Known-working reference module for 7.0.0-30-generic. > > > Known-working source SHA256: > > 0a27aa1379e8b7fc22f509b8d06ed3676a211d7bb3226a3f9b3dadfc208be7a3 > > Known-working module SHA256: > > b2c9eacb720d45fcaab15ff09ad3fdc2e97b8a6dd215c80fa282090ff8d2b2cd > > > Installation history > ==================== > > Because the stock VMD driver could not expose the internal SSD, an > existing > Ubuntu HDD from another laptop was connected to the MSI Vector through a > SATA-to-USB adapter. > > The MSI Vector was booted directly from that HDD. That Ubuntu environment > was running kernel 7.0.0-30-generic. > > The modified VMD driver was used there to expose the internal NVMe > SSD. > > Ubuntu was then manually deployed onto the dedicated Ubuntu partition of > the > internal SSD without modifying the existing Windows and data partitions. > > The manually deployed SSD installation initially contained kernel > 7.0.0-14-generic. This kernel was not intentionally selected as a VMD > workaround; it was simply the kernel present in the manually deployed > system > at that stage. > > A compatible custom VMD module was installed for 7.0.0-14-generic and > added > to its initramfs, allowing the first independent boot from the internal > SSD. > > Only after that successful SSD boot was DKMS configured. > > The SSD installation was subsequently updated to 7.0.0-30-generic, where > the > final VMD/ARL004 development and testing was performed. > > > Expected result > =============== > > The stock Ubuntu kernel should: > > 1. correctly enumerate the second-rootbus / Bus Offset 3 topology on Intel > > VMD 8086:ad0b; > 2. expose the internal NVMe SSD; > 3. handle NVMe completion ordering without repeated approximately > 30-second > completion timeouts. > > > Actual result > ============= > > With the stock VMD driver, the internal SSD is not exposed because Bus > Offset Setting 3 is rejected. > > After adding second-rootbus support alone, the SSD becomes visible but > repeated NVMe completion stalls occur on this hardware. > > The experimental ARL004 ordering workaround eliminates the observed stalls > > on the tested system. > > > Notes > ===== > > The ARL004 workaround is experimental and platform-specific. I am > reporting > the observed hardware behavior and the tested workaround rather than > claiming that this implementation is the appropriate final upstream fix. > > The Windows driver binary is not redistributed in the GitHub repository. > Only identification information, hashes and static-analysis notes are > provided. > > 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 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC1: gvozd188 2323 F.... pipewire > gvozd188 2360 F.... wireplumber > /dev/snd/controlC0: gvozd188 2360 F.... wireplumber > /dev/snd/seq: gvozd188 2323 F.... pipewire > CasperMD5CheckResult: unknown > CurrentDesktop: ubuntu:GNOME > Date: Thu Sep 3 13:08:10 2026 > MachineType: Micro-Star International Co., Ltd. Vector 17 HX AI A2XWIG > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic > root=UUID=fef65fb9-b1c4-4bbe-9c02-92a4a7280fee ro quiet splash iommu=pt > crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > WifiSyslog: > > dmi.bios.date: 04/20/2026 > dmi.bios.release: 1.18 > dmi.bios.vendor: American Megatrends International, LLC. > dmi.bios.version: E17S3IMS.112 > dmi.board.asset.tag: Default string > dmi.board.name: MS-17S3 > dmi.board.vendor: Micro-Star International Co., Ltd. > dmi.board.version: REV:1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Micro-Star International Co., Ltd. > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17S3IMS.112:bd04/20/2026:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnVector17HXAIA2XWIG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17S3.1:pfaVector: > > dmi.product.family: Vector > dmi.product.name: Vector 17 HX AI A2XWIG > dmi.product.sku: 17S3.1 > dmi.product.version: REV:1.0 > dmi.sys.vendor: Micro-Star International Co., Ltd. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166325/+subscriptions > > -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166325 Title: Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 causes NVMe completion stalls Status in linux package in Ubuntu: Confirmed Bug description: Hardware ======== Laptop: MSI Vector 17 HX AI Platform: Intel Arrow Lake Intel VMD: 8086:ad0b VMD PCI address: 0000:00:0e.0 Subsystem: 1462:149c Internal NVMe SSD: Phison 1TB ESR01TBYCCA4-EDJ-2MS Controller: Phison PS5029-E29T PCIe 4.0 NVMe PCI ID: 1987:5029 (rev 01) Firmware: ETFM50.0 Ubuntu: 26.04 Current/final tested kernel: 7.0.0-30-generic Secure Boot: enabled Problem 1: Intel VMD Bus Offset 3 ================================ With the stock Ubuntu VMD driver the internal NVMe SSD is not exposed. The kernel reports: vmd 0000:00:0e.0: Unknown Bus Offset Setting (3) and no internal /dev/nvme* device is available. Linux 6.14 was also tested on this machine and did not solve the VMD problem. The system firmware does not expose a usable BIOS option to disable Intel VMD/RST. Intel's public VMD second-rootbus patch series was integrated into the Ubuntu VMD source: [PATCH v3 0/8] VMD add second rootbus support https://www.spinics.net/lists/linux-pci/msg163096.html After integrating the second-rootbus support, Linux successfully enumerates the internal NVMe controller and SSD. Problem 2: NVMe completion stalls ================================= After the SSD became accessible through the modified VMD driver, a second problem became visible. Kernel messages repeatedly contained: nvme nvme0: I/O tag ... timeout, completion polled The stalls occurred at approximately 30-second intervals. A diagnostic sequential read before the workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress Result: 1 GiB in approximately 121.339 seconds approximately 8.8 MB/s CPU and memory were not saturated. Disabling ASPM was tested and did not solve the problem. ARL004 investigation ==================== The official Intel RST/VMD Windows driver distributed by MSI for this machine was examined by static analysis for comparison. The relevant Windows driver path performs a PCI configuration-space read after MSI handling when the completion state requires ordering. This behavior is consistent with the Intel Arrow Lake ARL004 erratum, where an MSI from a VMD-owned device may pass a preceding memory write. An experimental Linux workaround was implemented for the tested 8086:ad0b VMD/NVMe path. It performs a dummy PCI configuration-space read before the subsequent interrupt handling path. Result ====== With the experimental ARL004 workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress completed in: 1 GiB in 0.88206 seconds approximately 1.2 GB/s A subsequent 10 GiB sequential diagnostic read also completed normally. After booting with the final tested module: sudo journalctl -k -b | grep -E 'timeout|completion polled' produced no matching messages. The approximately 136x difference above is only a diagnostic comparison on this specific machine and is not intended as a general SSD benchmark. Reproduction / reference implementation ======================================= The complete investigation, tested source, separate patches, combined patch, known-working module, SHA256 checksums, installation/bootstrap procedure and recovery procedure are published here: https://github.com/gvozd188/vmd-arl004 Exact reference commit: https://github.com/gvozd188/vmd-arl004/commit/5438c83 Relevant files: 0001-vmd-second-rootbus-intel.patch Integration of Intel's second-rootbus support. 0002-vmd-ad0b-arl004-workaround.patch Experimental ARL004 workaround. vmd-arl004.patch Combined patch. vmd-ubuntu-7.0.0-30.c Ubuntu VMD source used as the patch base. vmd.c Final tested source. vmd.ko Known-working reference module for 7.0.0-30-generic. Known-working source SHA256: 0a27aa1379e8b7fc22f509b8d06ed3676a211d7bb3226a3f9b3dadfc208be7a3 Known-working module SHA256: b2c9eacb720d45fcaab15ff09ad3fdc2e97b8a6dd215c80fa282090ff8d2b2cd Installation history ==================== Because the stock VMD driver could not expose the internal SSD, an existing Ubuntu HDD from another laptop was connected to the MSI Vector through a SATA-to-USB adapter. The MSI Vector was booted directly from that HDD. That Ubuntu environment was running kernel 7.0.0-30-generic. The modified VMD driver was used there to expose the internal NVMe SSD. Ubuntu was then manually deployed onto the dedicated Ubuntu partition of the internal SSD without modifying the existing Windows and data partitions. The manually deployed SSD installation initially contained kernel 7.0.0-14-generic. This kernel was not intentionally selected as a VMD workaround; it was simply the kernel present in the manually deployed system at that stage. A compatible custom VMD module was installed for 7.0.0-14-generic and added to its initramfs, allowing the first independent boot from the internal SSD. Only after that successful SSD boot was DKMS configured. The SSD installation was subsequently updated to 7.0.0-30-generic, where the final VMD/ARL004 development and testing was performed. Expected result =============== The stock Ubuntu kernel should: 1. correctly enumerate the second-rootbus / Bus Offset 3 topology on Intel VMD 8086:ad0b; 2. expose the internal NVMe SSD; 3. handle NVMe completion ordering without repeated approximately 30-second completion timeouts. Actual result ============= With the stock VMD driver, the internal SSD is not exposed because Bus Offset Setting 3 is rejected. After adding second-rootbus support alone, the SSD becomes visible but repeated NVMe completion stalls occur on this hardware. The experimental ARL004 ordering workaround eliminates the observed stalls on the tested system. Notes ===== The ARL004 workaround is experimental and platform-specific. I am reporting the observed hardware behavior and the tested workaround rather than claiming that this implementation is the appropriate final upstream fix. The Windows driver binary is not redistributed in the GitHub repository. Only identification information, hashes and static-analysis notes are provided. 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gvozd188 2323 F.... pipewire gvozd188 2360 F.... wireplumber /dev/snd/controlC0: gvozd188 2360 F.... wireplumber /dev/snd/seq: gvozd188 2323 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 13:08:10 2026 MachineType: Micro-Star International Co., Ltd. Vector 17 HX AI A2XWIG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=fef65fb9-b1c4-4bbe-9c02-92a4a7280fee ro quiet splash iommu=pt crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 04/20/2026 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17S3IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-17S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17S3IMS.112:bd04/20/2026:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnVector17HXAIA2XWIG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17S3.1:pfaVector: dmi.product.family: Vector dmi.product.name: Vector 17 HX AI A2XWIG dmi.product.sku: 17S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166325/+subscriptions

[Bug 2166325] Re: Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 causes NVMe completion stalls

Confirming the same issue on an Arrow Lake laptop with VMD 8086:7d0b (Ubuntu 26.04.1, kernel 7.0.0-31-generic): frequent "nvme: I/O ... timeout, completion polled" events causing 30 s – 2 min application stalls. APST off, C-state limits, kernel/BIOS/firmware updates did not help. Applying Rickey Bartlett's "PCI: vmd: Flush initiator posted writes before demuxing interrupts on Meteor Lake" (pci.git controller/vmd) to Ubuntu's vmd.c via DKMS fixed it completely: 0 events, I/O pressure from ~40% to ~0%. Please consideran SRU cherry-pick for 7.0.x. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166325 Title: Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 causes NVMe completion stalls Status in linux package in Ubuntu: Confirmed Bug description: Hardware ======== Laptop: MSI Vector 17 HX AI Platform: Intel Arrow Lake Intel VMD: 8086:ad0b VMD PCI address: 0000:00:0e.0 Subsystem: 1462:149c Internal NVMe SSD: Phison 1TB ESR01TBYCCA4-EDJ-2MS Controller: Phison PS5029-E29T PCIe 4.0 NVMe PCI ID: 1987:5029 (rev 01) Firmware: ETFM50.0 Ubuntu: 26.04 Current/final tested kernel: 7.0.0-30-generic Secure Boot: enabled Problem 1: Intel VMD Bus Offset 3 ================================ With the stock Ubuntu VMD driver the internal NVMe SSD is not exposed. The kernel reports: vmd 0000:00:0e.0: Unknown Bus Offset Setting (3) and no internal /dev/nvme* device is available. Linux 6.14 was also tested on this machine and did not solve the VMD problem. The system firmware does not expose a usable BIOS option to disable Intel VMD/RST. Intel's public VMD second-rootbus patch series was integrated into the Ubuntu VMD source: [PATCH v3 0/8] VMD add second rootbus support https://www.spinics.net/lists/linux-pci/msg163096.html After integrating the second-rootbus support, Linux successfully enumerates the internal NVMe controller and SSD. Problem 2: NVMe completion stalls ================================= After the SSD became accessible through the modified VMD driver, a second problem became visible. Kernel messages repeatedly contained: nvme nvme0: I/O tag ... timeout, completion polled The stalls occurred at approximately 30-second intervals. A diagnostic sequential read before the workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress Result: 1 GiB in approximately 121.339 seconds approximately 8.8 MB/s CPU and memory were not saturated. Disabling ASPM was tested and did not solve the problem. ARL004 investigation ==================== The official Intel RST/VMD Windows driver distributed by MSI for this machine was examined by static analysis for comparison. The relevant Windows driver path performs a PCI configuration-space read after MSI handling when the completion state requires ordering. This behavior is consistent with the Intel Arrow Lake ARL004 erratum, where an MSI from a VMD-owned device may pass a preceding memory write. An experimental Linux workaround was implemented for the tested 8086:ad0b VMD/NVMe path. It performs a dummy PCI configuration-space read before the subsequent interrupt handling path. Result ====== With the experimental ARL004 workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress completed in: 1 GiB in 0.88206 seconds approximately 1.2 GB/s A subsequent 10 GiB sequential diagnostic read also completed normally. After booting with the final tested module: sudo journalctl -k -b | grep -E 'timeout|completion polled' produced no matching messages. The approximately 136x difference above is only a diagnostic comparison on this specific machine and is not intended as a general SSD benchmark. Reproduction / reference implementation ======================================= The complete investigation, tested source, separate patches, combined patch, known-working module, SHA256 checksums, installation/bootstrap procedure and recovery procedure are published here: https://github.com/gvozd188/vmd-arl004 Exact reference commit: https://github.com/gvozd188/vmd-arl004/commit/5438c83 Relevant files: 0001-vmd-second-rootbus-intel.patch Integration of Intel's second-rootbus support. 0002-vmd-ad0b-arl004-workaround.patch Experimental ARL004 workaround. vmd-arl004.patch Combined patch. vmd-ubuntu-7.0.0-30.c Ubuntu VMD source used as the patch base. vmd.c Final tested source. vmd.ko Known-working reference module for 7.0.0-30-generic. Known-working source SHA256: 0a27aa1379e8b7fc22f509b8d06ed3676a211d7bb3226a3f9b3dadfc208be7a3 Known-working module SHA256: b2c9eacb720d45fcaab15ff09ad3fdc2e97b8a6dd215c80fa282090ff8d2b2cd Installation history ==================== Because the stock VMD driver could not expose the internal SSD, an existing Ubuntu HDD from another laptop was connected to the MSI Vector through a SATA-to-USB adapter. The MSI Vector was booted directly from that HDD. That Ubuntu environment was running kernel 7.0.0-30-generic. The modified VMD driver was used there to expose the internal NVMe SSD. Ubuntu was then manually deployed onto the dedicated Ubuntu partition of the internal SSD without modifying the existing Windows and data partitions. The manually deployed SSD installation initially contained kernel 7.0.0-14-generic. This kernel was not intentionally selected as a VMD workaround; it was simply the kernel present in the manually deployed system at that stage. A compatible custom VMD module was installed for 7.0.0-14-generic and added to its initramfs, allowing the first independent boot from the internal SSD. Only after that successful SSD boot was DKMS configured. The SSD installation was subsequently updated to 7.0.0-30-generic, where the final VMD/ARL004 development and testing was performed. Expected result =============== The stock Ubuntu kernel should: 1. correctly enumerate the second-rootbus / Bus Offset 3 topology on Intel VMD 8086:ad0b; 2. expose the internal NVMe SSD; 3. handle NVMe completion ordering without repeated approximately 30-second completion timeouts. Actual result ============= With the stock VMD driver, the internal SSD is not exposed because Bus Offset Setting 3 is rejected. After adding second-rootbus support alone, the SSD becomes visible but repeated NVMe completion stalls occur on this hardware. The experimental ARL004 ordering workaround eliminates the observed stalls on the tested system. Notes ===== The ARL004 workaround is experimental and platform-specific. I am reporting the observed hardware behavior and the tested workaround rather than claiming that this implementation is the appropriate final upstream fix. The Windows driver binary is not redistributed in the GitHub repository. Only identification information, hashes and static-analysis notes are provided. 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gvozd188 2323 F.... pipewire gvozd188 2360 F.... wireplumber /dev/snd/controlC0: gvozd188 2360 F.... wireplumber /dev/snd/seq: gvozd188 2323 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 13:08:10 2026 MachineType: Micro-Star International Co., Ltd. Vector 17 HX AI A2XWIG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=fef65fb9-b1c4-4bbe-9c02-92a4a7280fee ro quiet splash iommu=pt crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 04/20/2026 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17S3IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-17S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17S3IMS.112:bd04/20/2026:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnVector17HXAIA2XWIG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17S3.1:pfaVector: dmi.product.family: Vector dmi.product.name: Vector 17 HX AI A2XWIG dmi.product.sku: 17S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166325/+subscriptions

[Bug 2166325] Re: Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 causes NVMe completion stalls

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166325 Title: Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004 causes NVMe completion stalls Status in linux package in Ubuntu: Confirmed Bug description: Hardware ======== Laptop: MSI Vector 17 HX AI Platform: Intel Arrow Lake Intel VMD: 8086:ad0b VMD PCI address: 0000:00:0e.0 Subsystem: 1462:149c Internal NVMe SSD: Phison 1TB ESR01TBYCCA4-EDJ-2MS Controller: Phison PS5029-E29T PCIe 4.0 NVMe PCI ID: 1987:5029 (rev 01) Firmware: ETFM50.0 Ubuntu: 26.04 Current/final tested kernel: 7.0.0-30-generic Secure Boot: enabled Problem 1: Intel VMD Bus Offset 3 ================================ With the stock Ubuntu VMD driver the internal NVMe SSD is not exposed. The kernel reports: vmd 0000:00:0e.0: Unknown Bus Offset Setting (3) and no internal /dev/nvme* device is available. Linux 6.14 was also tested on this machine and did not solve the VMD problem. The system firmware does not expose a usable BIOS option to disable Intel VMD/RST. Intel's public VMD second-rootbus patch series was integrated into the Ubuntu VMD source: [PATCH v3 0/8] VMD add second rootbus support https://www.spinics.net/lists/linux-pci/msg163096.html After integrating the second-rootbus support, Linux successfully enumerates the internal NVMe controller and SSD. Problem 2: NVMe completion stalls ================================= After the SSD became accessible through the modified VMD driver, a second problem became visible. Kernel messages repeatedly contained: nvme nvme0: I/O tag ... timeout, completion polled The stalls occurred at approximately 30-second intervals. A diagnostic sequential read before the workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress Result: 1 GiB in approximately 121.339 seconds approximately 8.8 MB/s CPU and memory were not saturated. Disabling ASPM was tested and did not solve the problem. ARL004 investigation ==================== The official Intel RST/VMD Windows driver distributed by MSI for this machine was examined by static analysis for comparison. The relevant Windows driver path performs a PCI configuration-space read after MSI handling when the completion state requires ordering. This behavior is consistent with the Intel Arrow Lake ARL004 erratum, where an MSI from a VMD-owned device may pass a preceding memory write. An experimental Linux workaround was implemented for the tested 8086:ad0b VMD/NVMe path. It performs a dummy PCI configuration-space read before the subsequent interrupt handling path. Result ====== With the experimental ARL004 workaround: sudo dd if=/dev/nvme0n1 of=/dev/null bs=16M count=64 status=progress completed in: 1 GiB in 0.88206 seconds approximately 1.2 GB/s A subsequent 10 GiB sequential diagnostic read also completed normally. After booting with the final tested module: sudo journalctl -k -b | grep -E 'timeout|completion polled' produced no matching messages. The approximately 136x difference above is only a diagnostic comparison on this specific machine and is not intended as a general SSD benchmark. Reproduction / reference implementation ======================================= The complete investigation, tested source, separate patches, combined patch, known-working module, SHA256 checksums, installation/bootstrap procedure and recovery procedure are published here: https://github.com/gvozd188/vmd-arl004 Exact reference commit: https://github.com/gvozd188/vmd-arl004/commit/5438c83 Relevant files: 0001-vmd-second-rootbus-intel.patch Integration of Intel's second-rootbus support. 0002-vmd-ad0b-arl004-workaround.patch Experimental ARL004 workaround. vmd-arl004.patch Combined patch. vmd-ubuntu-7.0.0-30.c Ubuntu VMD source used as the patch base. vmd.c Final tested source. vmd.ko Known-working reference module for 7.0.0-30-generic. Known-working source SHA256: 0a27aa1379e8b7fc22f509b8d06ed3676a211d7bb3226a3f9b3dadfc208be7a3 Known-working module SHA256: b2c9eacb720d45fcaab15ff09ad3fdc2e97b8a6dd215c80fa282090ff8d2b2cd Installation history ==================== Because the stock VMD driver could not expose the internal SSD, an existing Ubuntu HDD from another laptop was connected to the MSI Vector through a SATA-to-USB adapter. The MSI Vector was booted directly from that HDD. That Ubuntu environment was running kernel 7.0.0-30-generic. The modified VMD driver was used there to expose the internal NVMe SSD. Ubuntu was then manually deployed onto the dedicated Ubuntu partition of the internal SSD without modifying the existing Windows and data partitions. The manually deployed SSD installation initially contained kernel 7.0.0-14-generic. This kernel was not intentionally selected as a VMD workaround; it was simply the kernel present in the manually deployed system at that stage. A compatible custom VMD module was installed for 7.0.0-14-generic and added to its initramfs, allowing the first independent boot from the internal SSD. Only after that successful SSD boot was DKMS configured. The SSD installation was subsequently updated to 7.0.0-30-generic, where the final VMD/ARL004 development and testing was performed. Expected result =============== The stock Ubuntu kernel should: 1. correctly enumerate the second-rootbus / Bus Offset 3 topology on Intel VMD 8086:ad0b; 2. expose the internal NVMe SSD; 3. handle NVMe completion ordering without repeated approximately 30-second completion timeouts. Actual result ============= With the stock VMD driver, the internal SSD is not exposed because Bus Offset Setting 3 is rejected. After adding second-rootbus support alone, the SSD becomes visible but repeated NVMe completion stalls occur on this hardware. The experimental ARL004 ordering workaround eliminates the observed stalls on the tested system. Notes ===== The ARL004 workaround is experimental and platform-specific. I am reporting the observed hardware behavior and the tested workaround rather than claiming that this implementation is the appropriate final upstream fix. The Windows driver binary is not redistributed in the GitHub repository. Only identification information, hashes and static-analysis notes are provided. 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gvozd188 2323 F.... pipewire gvozd188 2360 F.... wireplumber /dev/snd/controlC0: gvozd188 2360 F.... wireplumber /dev/snd/seq: gvozd188 2323 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 13:08:10 2026 MachineType: Micro-Star International Co., Ltd. Vector 17 HX AI A2XWIG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=fef65fb9-b1c4-4bbe-9c02-92a4a7280fee ro quiet splash iommu=pt crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 04/20/2026 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17S3IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-17S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17S3IMS.112:bd04/20/2026:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnVector17HXAIA2XWIG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17S3.1:pfaVector: dmi.product.family: Vector dmi.product.name: Vector 17 HX AI A2XWIG dmi.product.sku: 17S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166325/+subscriptions

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

All autopkgtests for the newly accepted linux-restricted-modules (5.15.0-198.208) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (amd64, armhf, i386) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 2150605] Re: `i915 Arrow Lake-S: PHY A / C10 DPLL state mismatch on resume from long s2idle dwell — slow wake (5-10s) with retry storm`

Two things not yet in this bug: the no-suspend path is also clean on 7.1.x, and there is a recorded reason why some journals here die and others survive. Everything else I had prepared is already covered by #16, #19 and #20. Why the journal dies -- the console lock, not just the modeset lock ------------------------------------------------------------------- #20 remarks that its journal survived, in contrast to the cut-off-mid-line reports in #18 and in my #9. On this machine the reason is on record. On 7.0.0-22, in a boot carrying 56 lines of the PHY A / DPLL signature, the hung-task detector caught two tasks, one of them journald itself: INFO: task systemd-journal:617 blocked for more than 122 seconds. task:systemd-journal state:D __mutex_lock_slowpath -> mutex_lock -> tty_open -> chrdev_open -> do_dentry_open -> vfs_open INFO: task 9:84842 blocked for more than 122 seconds. __down -> down -> console_device -> tty_lookup_driver -> tty_open So alongside the modeset lock in #20's trace, the console semaphore is held as well, and journald blocks on it as soon as it touches a tty. Nothing reaches the journal after that, which is exactly the "cut off mid-line" pattern. It is loss of evidence rather than proof of a dead machine: in that instance a clean shutdown still completed afterwards (systemd-shutdown, filesystems unmounted), so the system was alive behind a dead display. Reading my own four July freezes with that in mind: three end mid-cascade with 60-130 s to the next boot, one goes silent for seven hours after the cascade and then stops. Only a long press on the power button recovered them, and I never tested network reachability, so I cannot say whether those were #20's unbounded wait or something worse. If it recurs I will check from another host before power-cycling; anyone else hitting this, please do the same, because the local console is the one thing that is provably unreliable here. The no-suspend path on a fixed kernel ------------------------------------- Comment #2 describes the failure with no suspend at all -- panel powered down through inactivity, system still running -- and #20 documents that path with a trace, reaching the pipe disable through DPMS. Every clean result posted so far, #19 included, measures s2idle dwell, and #20's good kernel is 6.17, from before the regression. So the no-suspend path has not yet been shown clean on a kernel that carries the fix. ThinkPad P1 Gen 8, Arrow Lake-P [8086:7d51], BIOS N4EET24W 1.10, Ubuntu 26.04, internal eDP-1 (pipe A / DDI A / PHY A), undocked, on AC. Stock mainline 7.1.9-070109-generic, no local patches. Same machine as comment #9. 24./25.08. 11 h 31 m no nvidia (taint 0) 25.08. 1 h 52 m nvidia 595.84 loaded Both: machine left running, panel powered down through inactivity, zero "PM: suspend entry" in the journal for the whole window. Zero hits across each boot for PHY A, DDI BUF, DP idle patterns, pll hw state mismatch, flip_done, commit wait, and zero i915 *ERROR*. One detail that may extend the userspace conclusion in #20: my sessions are KDE on Wayland, so the X DPMS extension is not in the picture, and the pipe disable was still reached on 7.0.0-27. The path does not look closable from userspace there either. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150605 Title: `i915 Arrow Lake-S: PHY A / C10 DPLL state mismatch on resume from long s2idle dwell — slow wake (5-10s) with retry storm` Status in linux package in Ubuntu: Confirmed Bug description: This is what an investigation using claude code yielded regarding a wake-up from sleep issue: On HP ZBook Fury G1i 16 (Arrow Lake-S, integrated display engine identifying as meteorlake D0, PCI 8086:7d67), every resume from s2idle after a multi-hour dwell produces a stack of i915 *ERROR* messages from the C10 PHY / DPLL state-restore path. The driver retries and eventually recovers, so the display *does* come back, but the retry loop takes ~5-10 seconds — long enough that users report "the display didn't wake up." Short cycles (seconds-to-minutes of dwell) wake instantly with no errors. The error stack is byte-for-byte identical across two reproductions and across `i915.enable_psr=0`, `i915.enable_dc=0`, and `i915.enable_fbc=0`. Those flags do not reach the code path that's racing. Earlier, before `i915.enable_psr=0` was applied, the same regime caused hard hangs (`Atomic update failure on pipe A`) requiring power-cycle. PSR-disable converted the failure mode from "hang" to "slow recover" but did not eliminate it. `xe.force_probe=7d67` was also tested as a workaround. xe binds cleanly on this device but suffers a different bug: `Tile0: GT0: Engine reset engine_class=rcs guc_id=48 state=0x289` repeating across each suspend cycle (`drm_WARN_ON_ONCE(ret == -110)`), eventually wedging the display. Not viable as a workaround on this kernel. NVIDIA dGPU is fully exonerated: `nvidia-suspend.service` and `nvidia-resume.service` `Finished` cleanly across every cycle. ## System * Distro: Ubuntu 26.04 LTS (resolute) * Kernel: 7.0.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 13 11:09:53 UTC 2026 x86_64 * Package: linux-image-7.0.0-14-generic 7.0.0-14.14 * Firmware pkg: linux-firmware 20260319.git217ca6e4.1ubuntu * HW: HP ZBook Fury G1i 16 inch Mobile Workstation PC, BIOS X96 Ver. 01.01.19 (2025-11-22) (latest per fwupdmgr) * iGPU: Intel Corporation Arrow Lake-S [Intel Graphics] [8086:7d67] (rev 06), driver: i915 * dGPU: NVIDIA Corporation GB205GLM [RTX PRO 3000 Blackwell Generation Laptop GPU] [10de:2f38] (rev a1), driver: nvidia 580.142 (open kernel modules) * Loaded i915 firmware: mtl_dmc.bin (v2.23), mtl_guc_70.bin v70.53.0, mtl_huc_gsc.bin v8.5.4 * Sleep mode: s2idle only (`ACPI: PM: (supports S0 S4 S5)` — firmware does not expose S3) * Kernel cmdline (current):   `quiet splash i915.enable_psr=0 i915.enable_dc=0 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=20 i915.enable_fbc=0` * Session: KDE Plasma on Wayland (sddm) ## Reproduction 1. Boot, log in, do normal work (browser, IDE, terminals). 2. Close laptop lid (or `systemctl suspend`) for ≥2 hours. 3. Open lid / press a key. Expected: panel relights within ~500 ms, no kernel ERRORs. Actual: panel relights after ~5-10 s, journal contains the error stack below. ## Journal trace (boot 2026-04-29 05:48, dwell 05:51:11 → 07:59:21 = 2 h 8 min) ``` PM: suspend entry (s2idle) PM: Some devices failed to suspend, or early wake event detected PM: suspend exit PM: suspend entry (s2idle) [2 h 8 min later] PM: suspend exit i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle. i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate                        (expected 1220171, found 92553) i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state i915 0000:00:02.0: [drm] *ERROR* expected: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no,                                    use_c10: yes, tbt_mode: no i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 810000, fracen: yes, i915 0000:00:02.0: [drm] *ERROR* quot: 61440, rem: 0, den: 1, i915 0000:00:02.0: [drm] *ERROR* multiplier: 210, tx_clk_div: 0. i915 0000:00:02.0: [drm] *ERROR* found: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no, i915 0000:00:02.0: [drm] *ERROR* multiplier: 16, tx_clk_div: 0. ``` The expected vs found C10 PLL clock (810 MHz HBR3 vs 61 MHz fallback) is the key signal: the panel's eDP link comes back at the wrong rate, the driver retries and eventually re-locks at the correct rate. This is in `drivers/gpu/drm/i915/display/intel_cx0_phy.c` / DPLL state restore — below the layers reachable by `enable_psr` / `enable_dc` / `enable_fbc`. ## What I have already tried | change | wake outcome on long dwell | |---|---| | (default) | hard hang, `Atomic update failure on pipe A`, requires power-cycle | | `i915.enable_psr=0` (only) | clean wake on short cycles, untested at long dwell | | `i915.enable_psr=0 i915.enable_dc=0` | slow recover (~5-10 s) at 6 h 41 min dwell, full error stack | | `... i915.enable_fbc=0` (added) | same: slow recover, identical error stack at 2 h 8 min dwell | | `i915.force_probe=!7d67 xe.force_probe=7d67` | xe binds cleanly, but `GT0: Engine reset` storm during cycles, eventual wedge | linux-firmware is at the latest candidate for 26.04 (20260319.git217ca6e4.1ubuntu). linux-image-oem-26.04 does not exist yet. ## Why this matters This is a clean reproduction of a likely-upstream Arrow Lake-S regression in the cx0/c10pll DPLL state-restore path during s2idle resume. The error signature is highly diagnostic and consistent across runs. Fix has not landed in 7.0.0-14.14; would benefit from being picked into the 26.04 kernel from upstream once available. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Wed Apr 29 08:18:09 2026 InstallationDate: Installed on 2026-03-27 (33 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260325) MachineType: HP HP ZBook Fury G1i 16 inch Mobile Workstation PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=2b2b39cc-2151-49f5-9205-74e3f9f1f999 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=20 i915.enable_fbc=0 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: 11/22/2025 dmi.bios.release: 1.19 dmi.bios.vendor: HP dmi.bios.version: X96 Ver. 01.01.19 dmi.board.name: 8DE2 dmi.board.vendor: HP dmi.board.version: KBC Version 55.35.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 85.53 dmi.modalias: dmi:bvnHP:bvrX96Ver.01.01.19:bd11/22/2025:br1.19:efr85.53:svnHP:pnHPZBookFuryG1i16inchMobileWorkstationPC:pvrSBKPFV3:rvnHP:rn8DE2:rvrKBCVersion55.35.00:cvnHP:ct10:cvr:skuB14E7AV:pfa103C_5336ANHPZBook: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Fury G1i 16 inch Mobile Workstation PC dmi.product.sku: B14E7AV dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150605/+subscriptions

[Bug 2166710] [NEW] choppy audio 2 channel music files

Public bug reported: 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] ** 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/2166710 Title: choppy audio 2 channel music files Status in linux package in Ubuntu: New 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] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166710/+subscriptions