Public bug reported: DESCRIPTION: == Summary == Repeated kernel panics on AMD Ryzen 7 4800U (Renoir/Zen2) triggered by the SRSO (Speculative Return Stack Overflow) mitigation interacting with the scheduler tick path. The system crashes every 1-11 days with no user-space trigger. Crashes occur in both linux-image-7.0.0-22-generic and linux-image-7.0.0-27-generic. Workaround: processor.max_cstate=1 (preventing deep C-states avoids the crash path). == Hardware == - System: AZW (Beelink) SER Mini PC - CPU: AMD Ryzen 7 4800U with Radeon Graphics (Zen2 / Renoir) - Microcode: 0x0860010d (updated from 0x08600106 at boot) - GPU: AMD Renoir [Radeon Vega Series] (integrated, amdgpu driver) - RAM: 16GB DDR4 - BIOS: SER_V1.14_P3C6M43_B_Link (03/24/2022) — latest available for this model - NVMe storage == Software == - Ubuntu 26.04 LTS (fresh install on 2026-05-26) - Kernel: 7.0.0-22-generic and 7.0.0-27-generic (both affected) - amd64-microcode: 3.20251202.1ubuntu2 - linux-firmware: 20260319.git217ca6e4.1ubuntu - Boot params: quiet splash crashkernel=... - Active mitigation: srso_return_thunk (confirmed via dmesg) - NOPTI active == Crash #1 — 2026-07-10 (kernel 7.0.0-27) == Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 0 Comm: swapper/0 RIP: 0010:srso_safe_ret+0x0/0x20 Call Trace: <IRQ> sched_tick+0x48/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x9a/0xd0 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1b/0x20 RIP: 0010:cpuidle_enter_state+0xca/0x700 cpuidle_enter+0x30/0x50 cpuidle_idle_call+0x16b/0x1f0 do_idle+0x94/0xf0 </TASK> == Crash #2 — 2026-07-12 (kernel 7.0.0-27) == BUG: unable to handle page fault for address: ffffffff99053b04 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD bc447067 P4D bc447067 PUD bc448063 PMD 0 Oops: Oops: 0002 [#1] SMP NOPTI CPU: 0 UID: 1000 PID: 2680076 Comm: curl RIP: 0010:kick_ilb+0x6e/0x180 Call Trace: <TASK> kick_ilb+0x52/0x180 nohz_balancer_kick+0x92/0x2d0 sched_balance_trigger+0x4c/0x90 sched_tick+0xf9/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x44/0xd0 asm_sysvec_apic_timer_interrupt+0x1b/0x20 </TASK> == Additional context == - amdgpu driver logs "dm_irq_work_func [amdgpu] hogged CPU for >13333us" 35+ times per boot, suggesting IRQ pressure on the scheduler tick path. - Both crashes occur on CPU 0 during timer interrupt → sched_tick. - Crash #1 is an invalid opcode in the SRSO safe_ret thunk itself. - Crash #2 is a page fault in kick_ilb writing to an unmapped kernel address (PMD 0), suggesting corrupted per-cpu data or text patching issue in the SRSO path. - The system was stable for 14 days once (when amdgpu initialized without errors). - Full kdump vmcores are available in /var/crash/ for all crashes. == Crash frequency == 6+ crashes since 2026-05-29, intervals ranging from 1.5 to 11 days. No specific user-space trigger identified — crashes happen during idle or light workloads (cron jobs, curl). == Workaround == Adding processor.max_cstate=1 to kernel boot parameters prevents the CPU from entering deep C-states where the crash occurs. This confirms the interaction between cpuidle exit path, SRSO return thunks, and sched_tick. == Possible root cause == The SRSO mitigation (srso_return_thunk / srso_safe_ret) appears to have a bug in the text patching or in the interaction with the scheduler's nohz/idle balancer on AMD Zen2 processors when exiting deep C-states. The amdgpu driver hogging the CPU in interrupt context likely increases the probability of hitting the race condition. == Kdump files == /var/crash/202607101059/ — Crash #1 (srso_safe_ret) /var/crash/202607120124/ — Crash #2 (kick_ilb) Both contain full vmcore dumps and dmesg extracts. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gdm-greeter 2490 F.... wireplumber /dev/snd/controlC0: gdm-greeter 2490 F.... wireplumber /dev/snd/seq: gdm-greeter 2474 F.... pipewire CasperMD5CheckResult: unknown Date: Sun Jul 12 12:34:59 2026 InstallationDate: Installed on 2026-05-26 (47 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp2s0Link: Not connected. MachineType: AZW SER ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=3cc618bf-7287-4c56-86b6-9ddbfe59a14a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.14_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.14_P3C6M43_B_Link:bd03/24/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4:pfaSER: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160457 Title: Kernel panic in srso_safe_ret / kick_ilb during sched_tick on AMD Ryzen 7 4800U (Zen2) Status in linux package in Ubuntu: New Bug description: DESCRIPTION: == Summary == Repeated kernel panics on AMD Ryzen 7 4800U (Renoir/Zen2) triggered by the SRSO (Speculative Return Stack Overflow) mitigation interacting with the scheduler tick path. The system crashes every 1-11 days with no user-space trigger. Crashes occur in both linux-image-7.0.0-22-generic and linux-image-7.0.0-27-generic. Workaround: processor.max_cstate=1 (preventing deep C-states avoids the crash path). == Hardware == - System: AZW (Beelink) SER Mini PC - CPU: AMD Ryzen 7 4800U with Radeon Graphics (Zen2 / Renoir) - Microcode: 0x0860010d (updated from 0x08600106 at boot) - GPU: AMD Renoir [Radeon Vega Series] (integrated, amdgpu driver) - RAM: 16GB DDR4 - BIOS: SER_V1.14_P3C6M43_B_Link (03/24/2022) — latest available for this model - NVMe storage == Software == - Ubuntu 26.04 LTS (fresh install on 2026-05-26) - Kernel: 7.0.0-22-generic and 7.0.0-27-generic (both affected) - amd64-microcode: 3.20251202.1ubuntu2 - linux-firmware: 20260319.git217ca6e4.1ubuntu - Boot params: quiet splash crashkernel=... - Active mitigation: srso_return_thunk (confirmed via dmesg) - NOPTI active == Crash #1 — 2026-07-10 (kernel 7.0.0-27) == Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 0 Comm: swapper/0 RIP: 0010:srso_safe_ret+0x0/0x20 Call Trace: <IRQ> sched_tick+0x48/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x9a/0xd0 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1b/0x20 RIP: 0010:cpuidle_enter_state+0xca/0x700 cpuidle_enter+0x30/0x50 cpuidle_idle_call+0x16b/0x1f0 do_idle+0x94/0xf0 </TASK> == Crash #2 — 2026-07-12 (kernel 7.0.0-27) == BUG: unable to handle page fault for address: ffffffff99053b04 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD bc447067 P4D bc447067 PUD bc448063 PMD 0 Oops: Oops: 0002 [#1] SMP NOPTI CPU: 0 UID: 1000 PID: 2680076 Comm: curl RIP: 0010:kick_ilb+0x6e/0x180 Call Trace: <TASK> kick_ilb+0x52/0x180 nohz_balancer_kick+0x92/0x2d0 sched_balance_trigger+0x4c/0x90 sched_tick+0xf9/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x44/0xd0 asm_sysvec_apic_timer_interrupt+0x1b/0x20 </TASK> == Additional context == - amdgpu driver logs "dm_irq_work_func [amdgpu] hogged CPU for >13333us" 35+ times per boot, suggesting IRQ pressure on the scheduler tick path. - Both crashes occur on CPU 0 during timer interrupt → sched_tick. - Crash #1 is an invalid opcode in the SRSO safe_ret thunk itself. - Crash #2 is a page fault in kick_ilb writing to an unmapped kernel address (PMD 0), suggesting corrupted per-cpu data or text patching issue in the SRSO path. - The system was stable for 14 days once (when amdgpu initialized without errors). - Full kdump vmcores are available in /var/crash/ for all crashes. == Crash frequency == 6+ crashes since 2026-05-29, intervals ranging from 1.5 to 11 days. No specific user-space trigger identified — crashes happen during idle or light workloads (cron jobs, curl). == Workaround == Adding processor.max_cstate=1 to kernel boot parameters prevents the CPU from entering deep C-states where the crash occurs. This confirms the interaction between cpuidle exit path, SRSO return thunks, and sched_tick. == Possible root cause == The SRSO mitigation (srso_return_thunk / srso_safe_ret) appears to have a bug in the text patching or in the interaction with the scheduler's nohz/idle balancer on AMD Zen2 processors when exiting deep C-states. The amdgpu driver hogging the CPU in interrupt context likely increases the probability of hitting the race condition. == Kdump files == /var/crash/202607101059/ — Crash #1 (srso_safe_ret) /var/crash/202607120124/ — Crash #2 (kick_ilb) Both contain full vmcore dumps and dmesg extracts. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gdm-greeter 2490 F.... wireplumber /dev/snd/controlC0: gdm-greeter 2490 F.... wireplumber /dev/snd/seq: gdm-greeter 2474 F.... pipewire CasperMD5CheckResult: unknown Date: Sun Jul 12 12:34:59 2026 InstallationDate: Installed on 2026-05-26 (47 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp2s0Link: Not connected. MachineType: AZW SER ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=3cc618bf-7287-4c56-86b6-9ddbfe59a14a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.14_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.14_P3C6M43_B_Link:bd03/24/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4:pfaSER: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160457/+subscriptions
воскресенье
[Bug 2160453] [NEW] i915: DPLL/PHY hang on Meteor Lake (Dell Pro Max 16 Plus) with TB5 dock after suspend/resume - flip_done timeout, system freeze
Public bug reported: ## Summary Dell Pro Max 16 Plus laptop running Ubuntu 26.04 with Intel Meteor Lake iGPU (`i915`) and NVIDIA RTX PRO 5000 (hybrid graphics) repeatedly freezes with black screen(s). The system remains running (compute continues, fans spin) but the desktop becomes completely unresponsive. Recovery requires dock power-cycle, suspend/resume, SSH reboot, or hard reset. The kernel logs show repeated `i915` display driver failures in the DPLL/PHY/pipe A path, especially during suspend/resume and display power-state transitions. A Dell Thunderbolt 5 dock with a 5120x2160 external monitor exacerbates the issue. Kernel parameter `i915.enable_psr=0` was applied but did not resolve suspend/resume failures. --- ## Hardware | Component | Details | |---|---| | Laptop | Dell Pro Max 16 Plus MB16250/0K8XPY | | BIOS | 2.6.1 (03/16/2026) | | CPU/GPU (integrated) | Intel Meteor Lake, PCI `8086:7d67`, driver `i915` | | GPU (discrete) | NVIDIA RTX PRO 5000 Blackwell, driver `nvidia 595.71.05` | | RAM | 128 GB | | Internal display | eDP-1 (built-in OLED panel) | | External monitor | Dell U4025QW 40" ultrawide, 5120x2160 | | Dock | Dell Thunderbolt 5 Dock (SD25TB5 / K2 DOCK) | | Dock link | TB5, 120 Gb/s, left-side Thunderbolt port | | Monitor connection | DisplayPort (dock DP port; previously USB-C, same bug) | --- ## Software | Component | Version | |---|---| | OS | Ubuntu 26.04 LTS (resolute) | | Kernel | 7.0.0-27-generic (#27-Ubuntu SMP PREEMPT_DYNAMIC) | | Mesa | 26.0.3-1ubuntu1 | | libdrm | 2.4.131-1 | | linux-firmware-intel-graphics | 20260319.git217ca6e4-0ubuntu2.1 | | Desktop | GNOME Shell 50.1, Wayland | | Kernel cmdline | `i915.enable_psr=0` (PSR disabled, bug persists) | --- ## Symptoms 1. One or both screens go black 2. Keyboard/mouse input stops responding 3. System is NOT fully dead — background processes (e.g. vLLM compute) may continue 4. No clean shutdown — logs stop abruptly until hard reset or recovery action 5. Disconnecting monitor/dock during freeze does not help (compositor blocked in kernel ioctl) 6. Toggling dock power off/on DOES recover the display link --- ## Triggers (confirmed across multiple incidents) | Trigger | Confirmed | |---|---| | Suspend / resume (lid close, idle suspend) | Yes — most reliable trigger | | Overnight idle (display power management) | Yes | | Stopping GPU workload (vLLM exit) | Yes — likely GPU power-state change | | External monitor via dock at 5120x2160 | Contributes — DP link retraining failures | | Monitor hotplug / dock reconnect | Yes | --- ## Kernel error signature (repeated in every incident) ``` i915 0000:00:02.0: [drm] *ERROR* flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] commit wait timed out i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state 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* PHY A failed to change powerdown state i915 0000:00:02.0: [drm] Port A PLL not unlocked i915 0000:00:02.0: [drm] port_clock mismatch: expected 540000, found 61440 i915 0000:00:02.0: [drm] pixel_rate mismatch: expected 317250, found 36096 ``` During suspend/resume, errors occur in: - `intel_display_driver_resume` → `i915_drm_resume` - `intel_dp_retrain_link` → `intel_encoder_link_check_work_fn` Also seen: ``` pcieport 0000:00:01.0: PCIe Bus Error: ACSViol (Thunderbolt controller) NVRM: RmHandleDNotifierEvent: Failed to handle ACPI D-Notifier event, status=0x11 ``` No `NMI watchdog`, `soft lockup`, or `hung_task` messages — kernel appears alive, display commit path is deadlocked. --- ## Incident timeline ### Incident 1 — 2026-07-10 ~20:23 - Hard reset required - Last log: `flip_done timed out` at 20:23:43 - Reboot at 20:26:48 ### Incident 2 — 2026-07-11 ~10:14 - Overnight computation, spontaneous freeze (no user interaction) - Both screens black, unresponsive - Hard reset, reboot at 10:31:55 ### Incident 3 — 2026-07-11 ~17:51 - After login, exiting vLLM - Recovered via dock power-cycle (no hard reset) ### Incident 4 — 2026-07-12 ~10:44 - Suspend/resume (lid close) - Same i915 errors during `i915_drm_resume` - Recovered without hard reset (~1 minute) --- ## What was tried | Mitigation | Result | |---|---| | `i915.enable_psr=0` kernel parameter | Active in cmdline; bug persists on suspend/resume | | Monitor USB-C → DisplayPort on dock | Display path changed (DP-7 → DP-10); suspend/resume still fails | | Dock on TB5 port (left side, 120 Gb/s) | Correct port confirmed; bug persists | | Dock power-cycle | Recovers display (workaround, not fix) | --- ## Display topology ``` Laptop (Intel i915, card1) ├── eDP-1: internal panel (always connected) └── DP-10: external Dell U4025QW via TB5 dock DisplayPort NVIDIA (card2): all outputs disconnected (compute only, vLLM) ``` External display is driven by **Intel i915**, not NVIDIA, even with vLLM using the discrete GPU. --- ## Steps to reproduce 1. Dell Pro Max 16 Plus with BIOS 2.6.1 2. Connect Dell TB5 dock to left-side Thunderbolt 5 port 3. Connect Dell U4025QW (or similar 5K display) via DisplayPort on dock 4. Boot Ubuntu 26.04 with kernel 7.0.0-27-generic 5. Use dual-monitor setup (internal + external) 6. Suspend the system (close lid or `systemctl suspend`) 7. Resume **Expected:** Normal desktop **Actual:** Black screen(s), input frozen; kernel logs show i915 DPLL/flip_done errors Alternative trigger: leave system idle overnight with external monitor connected. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "logs" https://bugs.launchpad.net/bugs/2160453/+attachment/5981380/+files/dell.zip -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160453 Title: i915: DPLL/PHY hang on Meteor Lake (Dell Pro Max 16 Plus) with TB5 dock after suspend/resume - flip_done timeout, system freeze Status in linux package in Ubuntu: New Bug description: ## Summary Dell Pro Max 16 Plus laptop running Ubuntu 26.04 with Intel Meteor Lake iGPU (`i915`) and NVIDIA RTX PRO 5000 (hybrid graphics) repeatedly freezes with black screen(s). The system remains running (compute continues, fans spin) but the desktop becomes completely unresponsive. Recovery requires dock power-cycle, suspend/resume, SSH reboot, or hard reset. The kernel logs show repeated `i915` display driver failures in the DPLL/PHY/pipe A path, especially during suspend/resume and display power-state transitions. A Dell Thunderbolt 5 dock with a 5120x2160 external monitor exacerbates the issue. Kernel parameter `i915.enable_psr=0` was applied but did not resolve suspend/resume failures. --- ## Hardware | Component | Details | |---|---| | Laptop | Dell Pro Max 16 Plus MB16250/0K8XPY | | BIOS | 2.6.1 (03/16/2026) | | CPU/GPU (integrated) | Intel Meteor Lake, PCI `8086:7d67`, driver `i915` | | GPU (discrete) | NVIDIA RTX PRO 5000 Blackwell, driver `nvidia 595.71.05` | | RAM | 128 GB | | Internal display | eDP-1 (built-in OLED panel) | | External monitor | Dell U4025QW 40" ultrawide, 5120x2160 | | Dock | Dell Thunderbolt 5 Dock (SD25TB5 / K2 DOCK) | | Dock link | TB5, 120 Gb/s, left-side Thunderbolt port | | Monitor connection | DisplayPort (dock DP port; previously USB-C, same bug) | --- ## Software | Component | Version | |---|---| | OS | Ubuntu 26.04 LTS (resolute) | | Kernel | 7.0.0-27-generic (#27-Ubuntu SMP PREEMPT_DYNAMIC) | | Mesa | 26.0.3-1ubuntu1 | | libdrm | 2.4.131-1 | | linux-firmware-intel-graphics | 20260319.git217ca6e4-0ubuntu2.1 | | Desktop | GNOME Shell 50.1, Wayland | | Kernel cmdline | `i915.enable_psr=0` (PSR disabled, bug persists) | --- ## Symptoms 1. One or both screens go black 2. Keyboard/mouse input stops responding 3. System is NOT fully dead — background processes (e.g. vLLM compute) may continue 4. No clean shutdown — logs stop abruptly until hard reset or recovery action 5. Disconnecting monitor/dock during freeze does not help (compositor blocked in kernel ioctl) 6. Toggling dock power off/on DOES recover the display link --- ## Triggers (confirmed across multiple incidents) | Trigger | Confirmed | |---|---| | Suspend / resume (lid close, idle suspend) | Yes — most reliable trigger | | Overnight idle (display power management) | Yes | | Stopping GPU workload (vLLM exit) | Yes — likely GPU power-state change | | External monitor via dock at 5120x2160 | Contributes — DP link retraining failures | | Monitor hotplug / dock reconnect | Yes | --- ## Kernel error signature (repeated in every incident) ``` i915 0000:00:02.0: [drm] *ERROR* flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] commit wait timed out i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state 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* PHY A failed to change powerdown state i915 0000:00:02.0: [drm] Port A PLL not unlocked i915 0000:00:02.0: [drm] port_clock mismatch: expected 540000, found 61440 i915 0000:00:02.0: [drm] pixel_rate mismatch: expected 317250, found 36096 ``` During suspend/resume, errors occur in: - `intel_display_driver_resume` → `i915_drm_resume` - `intel_dp_retrain_link` → `intel_encoder_link_check_work_fn` Also seen: ``` pcieport 0000:00:01.0: PCIe Bus Error: ACSViol (Thunderbolt controller) NVRM: RmHandleDNotifierEvent: Failed to handle ACPI D-Notifier event, status=0x11 ``` No `NMI watchdog`, `soft lockup`, or `hung_task` messages — kernel appears alive, display commit path is deadlocked. --- ## Incident timeline ### Incident 1 — 2026-07-10 ~20:23 - Hard reset required - Last log: `flip_done timed out` at 20:23:43 - Reboot at 20:26:48 ### Incident 2 — 2026-07-11 ~10:14 - Overnight computation, spontaneous freeze (no user interaction) - Both screens black, unresponsive - Hard reset, reboot at 10:31:55 ### Incident 3 — 2026-07-11 ~17:51 - After login, exiting vLLM - Recovered via dock power-cycle (no hard reset) ### Incident 4 — 2026-07-12 ~10:44 - Suspend/resume (lid close) - Same i915 errors during `i915_drm_resume` - Recovered without hard reset (~1 minute) --- ## What was tried | Mitigation | Result | |---|---| | `i915.enable_psr=0` kernel parameter | Active in cmdline; bug persists on suspend/resume | | Monitor USB-C → DisplayPort on dock | Display path changed (DP-7 → DP-10); suspend/resume still fails | | Dock on TB5 port (left side, 120 Gb/s) | Correct port confirmed; bug persists | | Dock power-cycle | Recovers display (workaround, not fix) | --- ## Display topology ``` Laptop (Intel i915, card1) ├── eDP-1: internal panel (always connected) └── DP-10: external Dell U4025QW via TB5 dock DisplayPort NVIDIA (card2): all outputs disconnected (compute only, vLLM) ``` External display is driven by **Intel i915**, not NVIDIA, even with vLLM using the discrete GPU. --- ## Steps to reproduce 1. Dell Pro Max 16 Plus with BIOS 2.6.1 2. Connect Dell TB5 dock to left-side Thunderbolt 5 port 3. Connect Dell U4025QW (or similar 5K display) via DisplayPort on dock 4. Boot Ubuntu 26.04 with kernel 7.0.0-27-generic 5. Use dual-monitor setup (internal + external) 6. Suspend the system (close lid or `systemctl suspend`) 7. Resume **Expected:** Normal desktop **Actual:** Black screen(s), input frozen; kernel logs show i915 DPLL/flip_done errors Alternative trigger: leave system idle overnight with external monitor connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160453/+subscriptions
[Bug 2160452] [NEW] Touchpad broke after updating linux kernel to 7.0.0-27-generic
Public bug reported: Hi, After updating the linux kernel from 7.0.0-22-generic to 7.0.0-27-generic the touchpad completely stopped working. I tried restarting the drivers (i2c_hid_api driver), and rebooting my computer, without success. I booted back in ubuntu using the 7.0.0-22-generic kernel and it worked again. OS version: Ubuntu 26.04 LTS, firmware version E16V1IMS.112 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: heart 3714 F.... wireplumber /dev/snd/controlC1: heart 3714 F.... wireplumber /dev/snd/seq: heart 3698 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:40:46 2026 InstallationDate: Installed on 2026-05-05 (68 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. GS66 Stealth 10SF ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-kitty ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rootflags=subvol=@ quiet splash intel_iommu=on 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) dmi.bios.date: 11/19/2020 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16V1IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-16V1 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:bvnAmericanMegatrendsInc.:bvrE16V1IMS.112:bd11/19/2020:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnGS66Stealth10SF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16V1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16V1.1:pfaGS: dmi.product.family: GS dmi.product.name: GS66 Stealth 10SF dmi.product.sku: 16V1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160452 Title: Touchpad broke after updating linux kernel to 7.0.0-27-generic Status in linux package in Ubuntu: New Bug description: Hi, After updating the linux kernel from 7.0.0-22-generic to 7.0.0-27-generic the touchpad completely stopped working. I tried restarting the drivers (i2c_hid_api driver), and rebooting my computer, without success. I booted back in ubuntu using the 7.0.0-22-generic kernel and it worked again. OS version: Ubuntu 26.04 LTS, firmware version E16V1IMS.112 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: heart 3714 F.... wireplumber /dev/snd/controlC1: heart 3714 F.... wireplumber /dev/snd/seq: heart 3698 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:40:46 2026 InstallationDate: Installed on 2026-05-05 (68 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. GS66 Stealth 10SF ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-kitty ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rootflags=subvol=@ quiet splash intel_iommu=on 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) dmi.bios.date: 11/19/2020 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16V1IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-16V1 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:bvnAmericanMegatrendsInc.:bvrE16V1IMS.112:bd11/19/2020:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnGS66Stealth10SF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16V1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16V1.1:pfaGS: dmi.product.family: GS dmi.product.name: GS66 Stealth 10SF dmi.product.sku: 16V1.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/2160452/+subscriptions
[Bug 2150776] Re: Ubuntu 26.04 GNOME Wayland: random short display/presentation freezes on AMD RX 7900 XT while apps continue running
Same symptom on different hardware — RX 9060 XT (RDNA4) Adding a data point from a different GPU generation, since this doesn't appear to be RX 7900 XT/RDNA3-specific. Hardware: AMD RX 9060 XT / Navi 44 (RDNA4), PCI ID [1002:7590] Kernel: 7.1.2-070102-generic (mainline build, #202606271039 SMP PREEMPT_DYNAMIC, Sat Jun 27 2026) Symptom: Identical "dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us N times" workqueue warnings, recurring across boots. Example from one boot (kernel monotonic timestamps, wall-clock range Jul 11 19:21:52 - Jul 12 00:37:29 — note the count climbs across the boot rather than resetting): [ 370.797119] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [ 455.037142] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [ 4037.810198] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND [ 5131.830194] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND [19307.125552] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 19 times, consider switching to WQ_UNBOUND Ruled out via systematic testing (12+ hours real usage under all three conditions simultaneously): 1. VRR/FreeSync — confirmed disabled at both the Xorg driver level (VariableRefresh: disabled) and the KWin compositor level (vrrPolicy: Never on both outputs). Warning still fired. 2. DPM/mclk power-state switching — GPU pinned to power_dpm_force_performance_level=high for the entire session (static top pstate, no automatic transitions). Warning still fired. 3. Refresh rate/modeset switching — both monitors static at 3440x1440@60Hz for the whole boot, no modeset or hotplug events in kernel or Xorg logs. Warning still fired. Since all three of the obvious triggers were independently ruled out, this points toward the underlying mechanism rather than any of the usual suspects (adaptive sync, power states, or display timing changes). Looked into the driver code and found dm_handle_vmin_vmax_update is a workqueue handler introduced specifically to offload dc_stream_adjust_vmin_vmax() off the interrupt handler so it can wait on dc_lock instead of racing it (see the amd-gfx patch thread on "fix dmub access race condition"): https://www.mail-archive.com/amd-gfx@lists.freedesktop.org/msg126413.html So the warning itself looks like the race-condition fix's own offload mechanism hitting contention, rather than being triggered by any user-facing setting. Happy to provide full journalctl -k output or test a debug kernel build if that'd help narrow it down further. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150776 Title: Ubuntu 26.04 GNOME Wayland: random short display/presentation freezes on AMD RX 7900 XT while apps continue running Status in linux package in Ubuntu: Confirmed Bug description: After installing Ubuntu 26.04 LTS, the display randomly freezes for a short time, usually a few hundred milliseconds to around one second. This is most visible in games and video playback, but it can also happen outside games (e.g. watching a video or just using Ubuntu). During the freeze, the application/game continues running. For example, in Counter-Strike 2 or Albion Online, if I am moving when the freeze happens, after the screen updates again my character is farther ahead. This suggests the system/game/input are still running, but the display/presentation stops updating temporarily. Audio usually continues normally. Very rarely, during longer freezes, audio repeats/stutters briefly. This did not happen on the same hardware with Ubuntu 24.04.4, Ubuntu 25.04, or Ubuntu 25.10. It started only on Ubuntu 26.04. Hardware: - CPU: AMD Ryzen 7 7700X - GPU: AMD Radeon RX 7900 XT / Navi 31 - Motherboard: ASRock B650M Pro RS WiFi - RAM: 32 GB - Monitors: 2x Dell S2721HS, 1920x1080, 60/74.97 Hz Software: - Ubuntu 26.04 LTS - GNOME Shell 50.1 - Wayland session - Mutter/libmutter 50.1 - Kernel 7.0.0-15-generic - Mesa 26.0.3 - RADV/radeonsi - Xwayland 24.1.10 What I tried: - Disabled VRR: no change - Tested 60 Hz and 74.97 Hz: no useful change - Disabled second monitor: no change - Disabled all GNOME Shell extensions: no change - Created a clean new user account and tested there: still freezes - Disabled Ryzen iGPU so only RX 7900 XT remained visible: still freezes - Updated motherboard BIOS from 1.30 to 4.20: no change - Tried amdgpu.dcdebugmask=0x12, 0x20012, 0x20052: no change - Tried runtime power_dpm_force_performance_level=high: no change - Tried MUTTER_DEBUG_FORCE_KMS_MODE=simple, MUTTER_DEBUG_KMS_THREAD_TYPE=user, MUTTER_DEBUG_DISABLE_HW_CURSORS=1: no change - Tried disabling unredirect/direct scanout through GNOME Looking Glass: no change - Kernel logs do not show amdgpu ring timeout or GPU reset during freezes - dmesg did show repeated AMD display-manager workqueue warnings: "dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us" Expected: The display should continue presenting frames smoothly. Actual: The visible display freezes briefly, then jumps forward, while the application continues running underneath. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: libmutter-18-0 50.1-0ubuntu2 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 21:47:54 2026 InstallationDate: Installed on 2026-04-29 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150776/+subscriptions
[Bug 2160443] Re: Graphics driver fails in kernel 6.8.0-134
Please give output of: sudo apt dist-upgrade ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160443 Title: Graphics driver fails in kernel 6.8.0-134 Status in linux package in Ubuntu: Incomplete Bug description: On a MacBook Air 2013 running linux mint 22.3 xfce, kernel 6.8.0-124 works perfectly with the intel graphics card (intel hd graphics 5000). However, in kernel 6.8.0-134 the screen is immediately black after booting and any editing of the bootloader eg with nomodeset or i915.modeset=1 does not work. Booting into GRUB and selecting 6.8.0-124 works and I've now held the boot into kernel 6.8.0-124. When booting into 6.8.0-124 in recovery mode and running dpkg the following errors were reported: linux-headers-6.8.0-134-generic linux-headers-generic linux-generic linux-image-6.8.0-134-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160443/+subscriptions
[Bug 2160443] [NEW] Graphics driver fails in kernel 6.8.0-134
You have been subscribed to a public bug: On a MacBook Air 2013 running linux mint 22.3 xfce, kernel 6.8.0-124 works perfectly with the intel graphics card (intel hd graphics 5000). However, in kernel 6.8.0-134 the screen is immediately black after booting and any editing of the bootloader eg with nomodeset or i915.modeset=1 does not work. Booting into GRUB and selecting 6.8.0-124 works and I've now held the boot into kernel 6.8.0-124. When booting into 6.8.0-124 in recovery mode and running dpkg the following errors were reported: linux-headers-6.8.0-134-generic linux-headers-generic linux-generic linux-image-6.8.0-134-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- Graphics driver fails in kernel 6.8.0-134 https://bugs.launchpad.net/bugs/2160443 You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2160444] [NEW] Ubuntu 26.04 live USB hangs at boot with GeForce RTX 5060 unless nomodeset is used
Public bug reported: Ubuntu 26.04 Desktop live USB cannot reach the "Try or Install Ubuntu" environment on a system with an NVIDIA GeForce RTX 5060. Steps to reproduce: 1. Create a bootable USB from the Ubuntu 26.04 Desktop AMD64 ISO. 2. Boot the USB in UEFI mode. 3. Select "Try or Install Ubuntu". 4. The system displays the Ubuntu logo and then hangs or shows a black screen. Expected result: The live desktop and installer should start normally, or GRUB should provide an accessible "Safe graphics" option. Actual result: The live environment cannot start with the default kernel parameters. Editing the GRUB entry and adding "nomodeset" allows the live environment to boot. Additional information: - GPU: NVIDIA GB206 [GeForce RTX 5060], PCI ID 10de:2d05 - Ubuntu kernel: 7.0.0-14-generic - After installation, ubuntu-drivers recommends nvidia-driver-595-open. - Installing nvidia-driver-595-open allows the installed system to use the GPU. - The problem occurs before the installer can offer third-party NVIDIA drivers. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: shinonn 5114 F.... wireplumber /dev/snd/controlC2: shinonn 5114 F.... wireplumber /dev/snd/controlC1: shinonn 5114 F.... wireplumber /dev/snd/seq: shinonn 5096 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 16:51:28 2026 InstallationDate: Installed on 2026-07-12 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASRock B660M PG Riptide ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=4673e360-461c-47e8-a6e8-8a9de2fad1e9 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 13.01 dmi.board.name: B660M PG Riptide dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr13.01:bd09/26/2025:br5.27:svnASRock:pnB660MPGRiptide:pvrToBeFilledByO.E.M.:rvnASRock:rnB660MPGRiptide:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:pfaToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: B660M PG Riptide dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ASRock ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160444 Title: Ubuntu 26.04 live USB hangs at boot with GeForce RTX 5060 unless nomodeset is used Status in linux package in Ubuntu: New Bug description: Ubuntu 26.04 Desktop live USB cannot reach the "Try or Install Ubuntu" environment on a system with an NVIDIA GeForce RTX 5060. Steps to reproduce: 1. Create a bootable USB from the Ubuntu 26.04 Desktop AMD64 ISO. 2. Boot the USB in UEFI mode. 3. Select "Try or Install Ubuntu". 4. The system displays the Ubuntu logo and then hangs or shows a black screen. Expected result: The live desktop and installer should start normally, or GRUB should provide an accessible "Safe graphics" option. Actual result: The live environment cannot start with the default kernel parameters. Editing the GRUB entry and adding "nomodeset" allows the live environment to boot. Additional information: - GPU: NVIDIA GB206 [GeForce RTX 5060], PCI ID 10de:2d05 - Ubuntu kernel: 7.0.0-14-generic - After installation, ubuntu-drivers recommends nvidia-driver-595-open. - Installing nvidia-driver-595-open allows the installed system to use the GPU. - The problem occurs before the installer can offer third-party NVIDIA drivers. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: shinonn 5114 F.... wireplumber /dev/snd/controlC2: shinonn 5114 F.... wireplumber /dev/snd/controlC1: shinonn 5114 F.... wireplumber /dev/snd/seq: shinonn 5096 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 16:51:28 2026 InstallationDate: Installed on 2026-07-12 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASRock B660M PG Riptide ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=4673e360-461c-47e8-a6e8-8a9de2fad1e9 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 13.01 dmi.board.name: B660M PG Riptide dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr13.01:bd09/26/2025:br5.27:svnASRock:pnB660MPGRiptide:pvrToBeFilledByO.E.M.:rvnASRock:rnB660MPGRiptide:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:pfaToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: B660M PG Riptide dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160444/+subscriptions
[Bug 2160441] [NEW] USB-C PD negotiation fails to marginal-quality power sources on ASUS ProArt PX13 (HN7306WV) - ucsi_acpi GET_CURRENT_CAM failure, other laptops unaffected on same power source
Public bug reported: Release: Description: Ubuntu 26.04 LTS Release: 26.04 Package version: linux-image-generic: Installed: (none) Candidate: 7.0.0-27.27 Version table: 7.0.0-27.27 500 500 http://id.archive.ubuntu.com/ubuntu resolute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu resolute-security/main amd64 Packages 7.0.0-14.14 500 500 http://id.archive.ubuntu.com/ubuntu resolute/main amd64 Packages What I expected to happen: USB-C PD charging should negotiate full wattage on any compliant charger, matching the behavior of other laptops on the same power source. What happened instead: On a specific AC power source (tested at a cafe), USB-C charging on ASUS ProArt PX13 fails to negotiate above the USB-C default fallback rate (15W / 5V-3A), regardless of charger brand used (tested with both Kiip 100W and Anker 100W chargers — same result on both). For comparison, two other laptops (Lenovo Yoga, ASUS ROG Flow Z13) charge normally at full rate on the exact same power source, using their own respective chargers (Anker 100W and a 64W charger respectively). At a different location (same building, different floor), the same ProArt + Kiip 100W combination charges normally at full rate — suggesting the ProArt's PD negotiation is less tolerant of marginal power quality compared to the other devices tested, rather than a simple charger/cable compatibility issue. dmesg shows the following error at the time of the failed negotiation: ucsi_acpi USBC000:00: GET_CURRENT_CAM command failed Hardware: ASUS ProArt PX13 (HN7306WV) BIOS version: HN7306WV.316 (confirmed latest available from ASUS support site as of testing) Kernel: 7.0.0-27-generic dGPU: disabled (via prime-select intel) at time of testing ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:44:09 2026 InstallationDate: Installed on 2026-05-22 (51 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUSTeK COMPUTER INC. ProArt PX13 HN7306WV_HN7306WV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=092e632f-6509-4603-95f7-c4038dc8f1a3 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: HN7306WV.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: HN7306WV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.25 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHN7306WV.316:bd03/18/2025:br5.35:efr3.25:svnASUSTeKCOMPUTERINC.:pnProArtPX13HN7306WV_HN7306WV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnHN7306WV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:pfaProArtPX13: dmi.product.family: ProArt PX13 dmi.product.name: ProArt PX13 HN7306WV_HN7306WV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160441 Title: USB-C PD negotiation fails to marginal-quality power sources on ASUS ProArt PX13 (HN7306WV) - ucsi_acpi GET_CURRENT_CAM failure, other laptops unaffected on same power source Status in linux package in Ubuntu: New Bug description: Release: Description: Ubuntu 26.04 LTS Release: 26.04 Package version: linux-image-generic: Installed: (none) Candidate: 7.0.0-27.27 Version table: 7.0.0-27.27 500 500 http://id.archive.ubuntu.com/ubuntu resolute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu resolute-security/main amd64 Packages 7.0.0-14.14 500 500 http://id.archive.ubuntu.com/ubuntu resolute/main amd64 Packages What I expected to happen: USB-C PD charging should negotiate full wattage on any compliant charger, matching the behavior of other laptops on the same power source. What happened instead: On a specific AC power source (tested at a cafe), USB-C charging on ASUS ProArt PX13 fails to negotiate above the USB-C default fallback rate (15W / 5V-3A), regardless of charger brand used (tested with both Kiip 100W and Anker 100W chargers — same result on both). For comparison, two other laptops (Lenovo Yoga, ASUS ROG Flow Z13) charge normally at full rate on the exact same power source, using their own respective chargers (Anker 100W and a 64W charger respectively). At a different location (same building, different floor), the same ProArt + Kiip 100W combination charges normally at full rate — suggesting the ProArt's PD negotiation is less tolerant of marginal power quality compared to the other devices tested, rather than a simple charger/cable compatibility issue. dmesg shows the following error at the time of the failed negotiation: ucsi_acpi USBC000:00: GET_CURRENT_CAM command failed Hardware: ASUS ProArt PX13 (HN7306WV) BIOS version: HN7306WV.316 (confirmed latest available from ASUS support site as of testing) Kernel: 7.0.0-27-generic dGPU: disabled (via prime-select intel) at time of testing ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:44:09 2026 InstallationDate: Installed on 2026-05-22 (51 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUSTeK COMPUTER INC. ProArt PX13 HN7306WV_HN7306WV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=092e632f-6509-4603-95f7-c4038dc8f1a3 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: HN7306WV.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: HN7306WV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.25 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHN7306WV.316:bd03/18/2025:br5.35:efr3.25:svnASUSTeKCOMPUTERINC.:pnProArtPX13HN7306WV_HN7306WV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnHN7306WV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:pfaProArtPX13: dmi.product.family: ProArt PX13 dmi.product.name: ProArt PX13 HN7306WV_HN7306WV 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/2160441/+subscriptions
суббота
[Bug 1786013] Autopkgtest regression report (linux-meta-azure-nvidia/6.8.0-1042.45)
All autopkgtests for the newly accepted linux-meta-azure-nvidia (6.8.0-1042.45) for noble have finished running. The following regressions have been reported in tests triggered by the package: linux-azure-nvidia/6.8.0-1042.45 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-meta-azure-nvidia [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 2160416] [NEW] Unable to connect to 6 GHz networks with MT7921K
Public bug reported: I am unable to use 6ghz WiFi with this chipset in Kubuntu 26.04. Only just noticed it because I upgraded my mesh WiFi at home to ASUS BT8, and my other devices work fine. Running "iw list" shows all 6ghz disabled. I tried forcing Swedish region with "sudo iw reg set SE" but no change. I found a bug report here, not sure if this is the same or not https://bugzilla.kernel.org/show_bug.cgi?id=218731 Happy to provide any additional information needed to help solve this. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jul 11 12:43:37 2026 InstallationDate: Installed on 2023-01-16 (1272 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-27 (106 days ago) dmi.bios.date: 04/16/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.20 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.20:bd04/16/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160416 Title: Unable to connect to 6 GHz networks with MT7921K Status in linux package in Ubuntu: New Bug description: I am unable to use 6ghz WiFi with this chipset in Kubuntu 26.04. Only just noticed it because I upgraded my mesh WiFi at home to ASUS BT8, and my other devices work fine. Running "iw list" shows all 6ghz disabled. I tried forcing Swedish region with "sudo iw reg set SE" but no change. I found a bug report here, not sure if this is the same or not https://bugzilla.kernel.org/show_bug.cgi?id=218731 Happy to provide any additional information needed to help solve this. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jul 11 12:43:37 2026 InstallationDate: Installed on 2023-01-16 (1272 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230115) MachineType: ASRock B650E PG Riptide WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=5863f9c0-ef4f-497e-81f5-12268da1003b ro kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-27 (106 days ago) dmi.bios.date: 04/16/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.20 dmi.board.asset.tag: Default string dmi.board.name: B650E PG Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.20:bd04/16/2026:br5.41:svnASRock:pnB650EPGRiptideWiFi:pvrDefaultstring:rvnASRock:rnB650EPGRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650E PG Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160416/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-6.8/6.8.0-1059.62~22.04.1)
All autopkgtests for the newly accepted linux-meta-nvidia-6.8 (6.8.0-1059.62~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dm-writeboost/2.2.13-1ubuntu4 (amd64) dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64) glibc/2.35-0ubuntu3.13 (arm64) glibc/unknown (amd64) lime-forensics/1.9.1-3 (amd64, arm64) linux-nvidia-6.8/6.8.0-1059.62~22.04.1 (amd64, arm64) lxc/unknown (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-meta-nvidia-6.8 [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 2150776] Re: Ubuntu 26.04 GNOME Wayland: random short display/presentation freezes on AMD RX 7900 XT while apps continue running
Confirming the fix on my end as well since I originally reported this bug. I've been running 7.0.0-27-generic as my daily driver for at least the past two weeks (installed via the normal official update - sudo apt upgrade - once 7.0.0-27 reached the release pocket, so no -proposed needed anymore). In that time, doing the same things that used to reliably trigger the freezes - Counter-Strike 2 on one monitor with video (YouTube/Twitch) playing on the second monitor - I have not experienced a single display freeze, neither the short sub-second ones nor the long multi-minute ones. This matches the other reports above (#11-#14) that 7.0.0-26 / 7.0.0-27 resolves the issue. So from my side this looks fixed by the 7.0.0-26/-27 kernel. One caveat for anyone landing here: earlier in this bug I had concluded that the 6.19.10 mainline kernel was also a workaround, but I later hit the same freeze (including a total pipe wedge) on 6.19.10 too - it only reduced the frequency. 7.0.0-27 is the first kernel where I genuinely stopped seeing the freezes. Thanks to everyone who tested and to the maintainers. Happy for this to be marked fixed if that matches the maintainers' view. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150776 Title: Ubuntu 26.04 GNOME Wayland: random short display/presentation freezes on AMD RX 7900 XT while apps continue running Status in linux package in Ubuntu: Confirmed Bug description: After installing Ubuntu 26.04 LTS, the display randomly freezes for a short time, usually a few hundred milliseconds to around one second. This is most visible in games and video playback, but it can also happen outside games (e.g. watching a video or just using Ubuntu). During the freeze, the application/game continues running. For example, in Counter-Strike 2 or Albion Online, if I am moving when the freeze happens, after the screen updates again my character is farther ahead. This suggests the system/game/input are still running, but the display/presentation stops updating temporarily. Audio usually continues normally. Very rarely, during longer freezes, audio repeats/stutters briefly. This did not happen on the same hardware with Ubuntu 24.04.4, Ubuntu 25.04, or Ubuntu 25.10. It started only on Ubuntu 26.04. Hardware: - CPU: AMD Ryzen 7 7700X - GPU: AMD Radeon RX 7900 XT / Navi 31 - Motherboard: ASRock B650M Pro RS WiFi - RAM: 32 GB - Monitors: 2x Dell S2721HS, 1920x1080, 60/74.97 Hz Software: - Ubuntu 26.04 LTS - GNOME Shell 50.1 - Wayland session - Mutter/libmutter 50.1 - Kernel 7.0.0-15-generic - Mesa 26.0.3 - RADV/radeonsi - Xwayland 24.1.10 What I tried: - Disabled VRR: no change - Tested 60 Hz and 74.97 Hz: no useful change - Disabled second monitor: no change - Disabled all GNOME Shell extensions: no change - Created a clean new user account and tested there: still freezes - Disabled Ryzen iGPU so only RX 7900 XT remained visible: still freezes - Updated motherboard BIOS from 1.30 to 4.20: no change - Tried amdgpu.dcdebugmask=0x12, 0x20012, 0x20052: no change - Tried runtime power_dpm_force_performance_level=high: no change - Tried MUTTER_DEBUG_FORCE_KMS_MODE=simple, MUTTER_DEBUG_KMS_THREAD_TYPE=user, MUTTER_DEBUG_DISABLE_HW_CURSORS=1: no change - Tried disabling unredirect/direct scanout through GNOME Looking Glass: no change - Kernel logs do not show amdgpu ring timeout or GPU reset during freezes - dmesg did show repeated AMD display-manager workqueue warnings: "dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us" Expected: The display should continue presenting frames smoothly. Actual: The visible display freezes briefly, then jumps forward, while the application continues running underneath. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: libmutter-18-0 50.1-0ubuntu2 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 21:47:54 2026 InstallationDate: Installed on 2026-04-29 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150776/+subscriptions
[Bug 2158569] Re: 7.0.0 kernel spends ~63s in initramfs retrying a non-enumerable USB port while 6.19.10 doesn't (same hardware)
Thanks Jacob. I tested the latest mainline stable build, v7.1.3 (7.1.3-070103-generic), on the same hardware. Note: the mainline image initially panicked at boot with "VFS: Unable to mount root fs on unknown-block(0,0)" because no initramfs was generated on install. I generated one with: sudo update-initramfs -c -k 7.1.3-070103-generic sudo update-grub after which 7.1.3 boots normally. Result: I could NOT reproduce the boot stall on 7.1.3. I tried 15+ different cases and times, including the specific conditions that reliably reproduce it on 7.0.0-27 (rebooting from a second user session, and repeated reboots to try to trigger the latched state). On 7.1.3 the initramfs phase was consistently fast every time and the usb 1-8 enumeration retry cycle did not occur. For reference, on the same machine: 7.0.0-27-generic: initrd ~65s when the stall is present 7.1.3-070103-generic: initrd 2.119s, stall never observed (total boot 18.4s) So whatever the cause, it appears to be resolved somewhere between 7.0.0 and 7.1.3 upstream. The broken/phantom USB port and the (likely faulty) controller are physically unchanged, only the kernel differs. Happy to test a specific intermediate build or provide any further logs if that would help narrow down which change fixed it. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158569 Title: 7.0.0 kernel spends ~63s in initramfs retrying a non-enumerable USB port while 6.19.10 doesn't (same hardware) Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 26.04, the 7.0.0 kernel frequently adds ~63 seconds to boot because the kernel repeatedly tries and fails to enumerate a USB port during the initramfs phase, proceeding only after exhausting all retries. The 6.19.10 mainline kernel doesn't stall on the same hardware with the same broken port present. Reproduction / behavior: - Once the stall occurs, it then occurs on EVERY subsequent boot - the long ~60+ seconds loading screen happens every time - until I fully drain power (shut down, unplug the power cable, hold the power button ~30s, then plug back in and boot). A normal reboot or power-off does not clear it; only the full power drain does. - After a power drain, the next boot may be clean, but once the stall reappears even once, it again persists on every boot until the next power drain. - This is easy to hit on 7.0.0. On 6.19.10, on the same hardware, I do not see this behavior at all. - I have not isolated exactly what first triggers it on a given session; I am reporting the observed pattern: it latches on and persists across reboots until a full power drain resets it. Hardware: - CPU: AMD Ryzen 7 7700X - GPU: AMD Radeon RX 7900 XT / Navi 31 - Motherboard: ASRock B650M Pro RS WiFi, BIOS 4.20 - Root: NVMe (Lexar SSD NM710 2TB), ext4, no USB needed for root The failing port: - usb 1-8 on controller 0000:0d:00.0 (xhci_hcd). - It never enumerates: it cycles through "device descriptor read/64, error -110", "Device not responding to setup address", and "device not accepting address N, error -71", then "unable to enumerate USB device". - physical_location reports back / left / lower. It does not correspond to any usable socket I can find: my actual front ports enumerate as 1-6 and 1-5, and my working rear ports are on a different controller (0000:10:00.4). So 1-8 appears to be a phantom/dead endpoint on this controller. Boot time comparison (systemd-analyze), same machine, same disk, same broken port physically present: 6.19.10-061910-generic: initrd 2.160s (total 19.820s) 7.0.0-27-generic: initrd ~65-67s (total ~1min 38s) On 7.0.0, the kernel log shows the full retry cycle on usb 1-8 consuming the window from ~1.4s to ~65s, and dracut-initqueue finishes the instant the kernel gives up on the port: [ 1.408] usb 1-8: new high-speed USB device number 3 using xhci_hcd [ 6.880] usb 1-8: device descriptor read/64, error -110 [22.752] usb 1-8: device descriptor read/64, error -110 [28.897] usb 1-8: device descriptor read/64, error -110 [44.768] usb 1-8: device descriptor read/64, error -110 [44.877] usb usb1-port8: attempt power cycle [50.118] usb 1-8: Device not responding to setup address. [55.331] usb 1-8: device not accepting address 5, error -71 [60.510] usb 1-8: Device not responding to setup address. [65.723] usb 1-8: device not accepting address 6, error -71 [65.725] usb usb1-port8: unable to enumerate USB device [65.739] systemd[1]: Finished dracut-initqueue.service - dracut initqueue hook. During this whole window the boot splash stays at a low fallback resolution (simpledrm), because amdgpu does not load until after the initramfs completes. What differs between the kernels: - 6.19.10 reaches the root filesystem and proceeds in ~2s of initrd; it does not sit through a 60+ seconds USB retry cycle during boot, and the slow state does not keep recurring. - 7.0.0 blocks the initramfs for the full retry/timeout budget on this single failed port. Root is on NVMe and does not depend on USB at all, so nothing about reaching the root filesystem requires waiting on this port. Runtime note (not a boot fix): - Once booted, writing 1 to /sys/bus/usb/devices/usb1/1-0:1.0/usb1-port8/disable stops the port retrying, but only after userspace is up, so it does not help the initramfs stall. Per-port quirks (quirks=0x01) and dracut cmdline/pre-trigger hooks did not prevent the boot-time stall in my testing. Expected: the kernel should not block boot for ~63s on a single USB port that fails to enumerate, especially when root is on NVMe and does not depend on USB. 6.19.10 demonstrates the faster behavior on identical hardware. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 19:10:17 2026 InstallationDate: Installed on 2026-05-01 (58 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp7s0Link: Not connected. MachineType: ASRock B650M Pro RS WiFi ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=b624231d-8e1e-4b2a-887d-4d219254360d ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.20 dmi.board.asset.tag: Default string dmi.board.name: B650M Pro RS WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.20:bd04/16/2026:br5.41:svnASRock:pnB650MProRSWiFi:pvrDefaultstring:rvnASRock:rnB650MProRSWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B650M Pro RS WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158569/+subscriptions