[Bug 2156644] Re: GNOME Panel & Activities Overview workspace thumbnails flickering issue

Update: The original apport report was generated using ubuntu-bug while the system was actively exhibiting the flickering/corruption symptoms with the 3-display configuration attached. I performed additional testing and found a significant correlation with monitor configuration. With my original multi-monitor setup (2 ASUS monitors + 1 TCL TV), GNOME Shell produced repeated errors of the form: gbm_surface_lock_front_buffer failed Failed to query buffer age, got error 3003 These sessions also exhibited Activities Overview flickering, top-panel flickering, and occasional window-edge artifacts. The issue reproduced across multiple kernels, including mainline 7.0.12-070012-generic. On that kernel the symptoms appeared after roughly 10 minutes rather than several hours, suggesting the newer kernel affected time-to-failure but did not eliminate the issue. I have since tested using a single display only (Sony TV over HDMI) and have been unable to reproduce the problem. In the single-display configuration there is no visible flickering, no rendering corruption, and the GBM/buffer-age errors are absent. Error counts observed: 3-display configuration: journalctl -b | grep -c "gbm_surface_lock_front_buffer failed" => 4495 journalctl -b | grep -c "Failed to query buffer age" => 3967 Single-display configuration: journalctl -b | grep -c "gbm_surface_lock_front_buffer failed" => 0 journalctl -b | grep -c "Failed to query buffer age" => 0 Perhaps this appears to be a GNOME Shell/Mutter multi-monitor rendering issue, or an interaction involving multiple outputs, rather than a kernel-only or i915-only problem. This multi-monitor configuration was used for an extended period on Ubuntu 24.04 without exhibiting the Activities Overview flickering or related rendering corruption. The issue first appeared after upgrading to Ubuntu 26.04. While I cannot rule out other software changes that occurred as part of the upgrade, I did not observe this behavior on the same hardware prior to the upgrade. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: New Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions

[Bug 1876637] Re: [Lenovo V330-15IKB] Volume jumps to max automatically

[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1876637 Title: [Lenovo V330-15IKB] Volume jumps to max automatically Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Invalid Bug description: alsa-driver was selected automatically. I don't know if that's the problem. I'm newbie. I just want to understand when it will be triggered (if it's a feature) so I can avoid increasing the volume to the max accidentally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mert 1026 F.... pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 02:57:08 2020 InstallationDate: Installed on 2020-05-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: May 03 12:18:43 V330 dbus-daemon[841]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=1000 pid=1026 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [81AX, Intel Kabylake HDMI, Digital Out, HDMI] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN49WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN49WW:bd02/18/2020:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876637/+subscriptions

[Bug 2121693] Re: iwlwifi drivers make network unavailable after some time

I am seeing what appears to be a similar/related issue on Ubuntu 26.04 LTS with an Intel AX201 adapter. System: - Ubuntu 26.04 LTS (resolute) - Kernel: 7.0.0-22-generic - Laptop: ASUS TUF Gaming F15 FX507ZC_FX507ZC - BIOS: FX507ZC.315, dated 2022-06-17 - Wi-Fi: Intel Alder Lake-P PCH CNVi WiFi [8086:51f0] rev 01 - Subsystem: Intel AX201 160MHz [8086:0074] - Firmware loaded: 89.123cf747.0 so-a0-hr-b0-89.ucode - linux-firmware: 20260319.git217ca6e4.1ubuntu Impact: Wi-Fi disappears/becomes unusable after iwlwifi firmware crashes. After the failure, lspci still shows the device and the iwlwifi/iwlmvm/mac80211/cfg80211 modules are loaded, but no wireless interface exists: - `iw dev` shows no wireless interfaces - `nmcli device status` shows only ethernet and loopback - `rfkill list all` shows Bluetooth only, no Wi-Fi device Relevant dmesg excerpts: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. iwlwifi 0000:00:14.3: Loaded firmware version: 89.123cf747.0 so-a0-hr-b0-89.ucode iwlwifi 0000:00:14.3: 0x00000034 | NMI_INTERRUPT_WDG iwlwifi 0000:00:14.3: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL iwlwifi 0000:00:14.3: Failed to start RT ucode: -110 iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110 iwlwifi 0000:00:14.3: Device error - reprobe! Hardware became unavailable during restart. WARNING: net/mac80211/util.c:1877 at ieee80211_reconfig+0x11e/0x1620 [mac80211], CPU#4: kworker/4:1/206 Timeline from one boot: - 2026-06-13 22:26:32: firmware 89.123cf747.0 so-a0-hr-b0-89.ucode loaded - 2026-06-13 22:26:32: NMI_INTERRUPT_WDG / NMI_INTERRUPT_LMAC_FATAL - 2026-06-13 22:26:32: Failed to start RT ucode: -110 - 2026-06-13 22:26:34: Failed to run INIT ucode: -110 - 2026-06-13 22:30:52: Microcode SW error detected. Restarting 0x0. - 2026-06-13 22:38:16: repeated Microcode SW error, followed by Device error - reprobe! - 2026-06-13 22:39:40: Hardware became unavailable during restart / ieee80211_reconfig warning - 2026-06-13 22:41:23: another Microcode SW error followed by reprobe and failed RT/INIT ucode starts This looks related because the hardware is Intel AX201 / Alder Lake-P CNVi and the failure mode is iwlwifi losing the device/interface after firmware restart. I can provide full dmesg, journalctl -k, NetworkManager logs, lspci -vvnn, and package versions if useful. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2121693 Title: iwlwifi drivers make network unavailable after some time Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Triaged Status in linux source package in Plucky: Won't Fix Bug description: Using an ACER Laptop here unddddddder Ubuntu 25.04, behavior was the same under 24.10 and 24.04 : System Information         Manufacturer: Acer         Product Name: Aspire A515-57         Version: V1.30 WiFi card is : 0000:00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01)         Subsystem: Intel Corporation Dual Band Wi-Fi 6(802.11ax) AX201 160MHz 2x2 [Harrison Peak]         Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 9         Memory at 601f274000 (64-bit, non-prefetchable) [size=16K]         Capabilities: [c8] Power Management version 3         Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+         Capabilities: [40] Express Root Complex Integrated Endpoint, IntMsgNum 0         Capabilities: [80] MSI-X: Enable+ Count=16 Masked-         Capabilities: [100] Latency Tolerance Reporting         Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>         Kernel driver in use: iwlwifi         Kernel modules: iwlwifi When using WiFi connected to a 5GHz access point, within a random time though mins to hours depending on the traffic usage on the card, the iwlwifi driver can get unusable leading to impossibility to use WiFi on the PC, only way to solve the problem after crash is to shutdown totally the laptop and cold boot to recover a usable connection. Attached are the logs found under dmesg which show when the problem occurs. Found a way to avoid the problem to occurs but it leads to have an almost unusable WiFi as the transfer rate is limited to 15~16Mbits/sec ... by adding options iwlwifi 11n_disable=1 to /etc/modprobe.d/iwlwifi.conf there is no crash anymore but it renders the laptop very laggy on some situations... I have a double boot with Windows 11 on this laptop and can confirm that I have no problem even with heavy speed usage under Windows, never had annny crash related to WiFi under Windows, but sorry Windows is not a solution for me :) Others tests I've done : - tried with different Live USB : Fedora / Ubuntu / Mint : all failed so the problem could be related to a common issue with wilwifi drivers under Linux ? - tried to change some settings at the access point's side : Mercusys HALO H80X which is 3 nodes Wifi 6 AX3000 Mesh but didn't find any setting which permit to solve the problem. I do not have access to another Access Point to test if this could be the culprit ... - some more configurations under /etc/modprobe.d/iwlwifi.conf ( I will output them below in a separate attachment). Available and at your disposal to give some more informations and/or debug more if you need some more tests. Thanks a lot for reading ! :) ------------------------------------------------------- ProblemType: Bug DistroRelease: Ubuntu 25.04 Package: linux-image-generic 6.14.0-29.29 ProcVersionSignature: Ubuntu 6.14.0-29.29-generic 6.14.8 Uname: Linux 6.14.0-29-generic x86_64 ApportVersion: 2.32.0-0ubuntu5.3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC0: lolomin 2090 F.... pipewire                       lolomin 2093 F.... wireplumber  /dev/snd/seq: lolomin 2090 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon Date: Fri Aug 29 16:40:09 2025 InstallationDate: Installed on 2024-07-05 (420 days ago) InstallationMedia: Ubuntu-Cinnamon 24.04 LTS "Noble Numbat" - Release amd64 (20240425) MachineType: Acer Aspire A515-57 ProcEnviron:  LANG=fr_FR.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-29-generic root=UUID=3b1ab1f5-3c43-4750-a198-2f3128d73147 ro security=selinux quiet splash pcie_port_pm=off pcie_aspm.policy=performance vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-6.14.0-29-generic N/A  linux-backports-modules-6.14.0-29-generic N/A  linux-firmware 20250317.git1d4c88ee-0ubuntu1.5 SourcePackage: linux UpgradeStatus: Upgraded to plucky on 2025-04-29 (122 days ago) dmi.bios.date: 01/13/2025 dmi.bios.release: 1.30 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ganymede_ADU dmi.board.vendor: ADL dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.30 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.30:bd01/13/2025:br1.30:efr1.29:svnAcer:pnAspireA515-57:pvrV1.30:rvnADL:rnGanymede_ADU:rvrV1.30:cvnAcer:ct10:cvrV1.30:sku0000000000000000: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-57 dmi.product.sku: 0000000000000000 dmi.product.version: V1.30 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2121693/+subscriptions

[Bug 2150776] Re: Ubuntu 26.04 GNOME Wayland: random short display/presentation freezes on AMD RX 7900 XT while apps continue running

I am experiencing the exact same symptoms as already mentioned above; Intermittent screen freezes / pauses usually only for a few 100 milliseconds but during video playback (YouTube, VLC) up to a few seconds has been noticed. The difference for me is that I have nothing in the log files suggesting what may be the cause of the problem so according to my logs it never happened. The system: - AMD Ryzen 9700X - 32GB G.Skill DDR6000 - MSI X870E Tomahawk WiFi - Gen4 NVMe system drive - Both iGPU and RX 9060 XT tested - Kubuntu 26.04 fully updated I have noticed that when I play an old game in DOSBox these hiccups affect both picture and sound. Since everything (CPU, GPU & soundcard) in DOSBox is emulated via the CPU, I think that these hiccups could be related to CPU and not GPU. It may have something to do with core- parking, power states or alike. If I boot the above computer into my old system, which is Kubuntu 24.04, the issue does not exist so it has to be related to *buntu 26.04. -- 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 2154646] Re: i915 Arrow Lake: PHY A powerdown failure + DPLL hw state mismatch on s2idle resume — recovers most cycles, hard-freezes some (Dell Pro Max 16, kernel 7.0.0-22)

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/2154646 Title: i915 Arrow Lake: PHY A powerdown failure + DPLL hw state mismatch on s2idle resume — recovers most cycles, hard-freezes some (Dell Pro Max 16, kernel 7.0.0-22) Status in linux package in Ubuntu: Confirmed Bug description: # i915 Arrow Lake: PHY A powerdown failure + DPLL hw state mismatch on s2idle resume — recovers most cycles, hard-freezes some (Dell Pro Max 16, kernel 7.0.0-22) ## Summary Every s2idle suspend/resume cycle triggers an identical i915 failure on the internal display (eDP-1). The bug reproduces 100% of the time, independent of external monitors, dock state, or session activity. Most resume cycles now recover after 30–75 seconds of degraded display state via timeout-based fallback paths in i915. However, **some resume cycles produce a complete, silent system freeze**: the desktop remains visible but is entirely unresponsive (no keyboard, mouse, or remote SSH), the kernel log stops with no further entries, no soft lockup watchdog trace fires, and only a power button hold recovers the system. The proportion of cycles that result in a silent freeze vs. a noisy recovery is non-deterministic. On earlier kernels (6.17.0-1017-oem, 7.0.0-15-generic) the same bug presented as a soft lockup in `nvidia-modeset` blocked downstream of the stuck i915 display state, with a visible watchdog trace in dmesg. As of 7.0.0-22 the soft-lockup path no longer fires — but the underlying race is unchanged, and now manifests as a silent hang of the entire graphics pipeline when it does cause a freeze. ## Hardware - **Machine**: Dell Pro Max 16 Premium (MA16250), BIOS 1.9.0 (2026-03-31) — latest available from Dell - **iGPU**: Intel Arrow Lake-P / Arc Pro 130T (rev 03) at `0000:00:02.0` - **dGPU**: NVIDIA RTX PRO 2000 Blackwell (Open kernel modules, driver 595.71.05) — verified not involved in this trace - **Internal display**: eDP-1 (CONNECTOR:507), driven via PHY A / DPLL 0 / pipe A / PLANE:34 - **RAM**: 61 GiB ## Software - **OS**: Ubuntu 26.04 LTS - **Kernel**: `7.0.0-22-generic` (`linux-image-7.0.0-22-generic`) - **Session**: Wayland (GNOME) - **Suspend mode**: `s2idle` only — BIOS does not expose `deep`/S3 (`cat /sys/power/mem_sleep` returns `[s2idle]`) - **Kernel command line**: `quiet splash i915.enable_psr=0 nvidia-drm.modeset=1` ## Steps to reproduce 1. Boot the system normally (any user activity, GNOME Wayland session) 2. `systemctl suspend` 3. Wake via keyboard/lid within ~30 seconds 4. Observe dmesg ## Expected behavior Suspend/resume completes within a few seconds, no display errors, dmesg clean. ## Actual behavior Resume takes 30–75 seconds during which the internal display is in a glitched/unresponsive state. dmesg shows the identical sequence on every cycle: ``` 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* [CRTC:150:pipe A] flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch ------------[ cut here ]------------ WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state+0x2a6/0x6b0 [i915] RIP: 0010:verify_single_dpll_state+0x2b3/0x6b0 [i915] Call Trace: intel_dpll_state_verify+0x63/0x260 [i915] intel_modeset_verify_crtc+0x5a/0xb0 [i915] intel_atomic_commit_tail+0x8a3/0xc50 [i915] intel_atomic_commit+0x28e/0x2e0 [i915] drm_atomic_commit+0xad/0xf0 drm_atomic_helper_commit_duplicated_state+0xfe/0x120 __intel_display_driver_resume+0xb8/0x130 [i915] intel_display_driver_resume+0xc7/0x140 [i915] i915_drm_resume+0x147/0x1e0 [i915] i915_pm_resume+0x1b/0x30 [i915] pci_pm_resume+0x8c/0x140 dpm_run_callback+0x5f/0x180 device_resume+0x177/0x270 async_resume+0x21/0x40 ---[ end trace 0000000000000000 ]--- 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] *ERROR* flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:507:eDP-1] commit wait timed out i915 0000:00:02.0: [drm] *ERROR* flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [PLANE:34:plane 1A] commit wait timed out [further trace through intel_dp_retrain_link → intel_dp_link_check → intel_encoder_link_check_work_fn] i915 0000:00:02.0: [drm] PHY A failed to change powerdown state ``` ## Test matrix (all produced the identical trace) | # | Dock state | Outcome | |---|------------|---------| | 1 | Dell Thunderbolt dock attached throughout | recovered, 33s | | 2 | Dock attached throughout (different cycle, same boot) | recovered, 74s | | 3 | Dock attached at suspend, disconnected before wake | recovered, 74s | | 4 | No dock attached at any time | recovered, 32s | Conclusion: dock state is irrelevant to the recovery cases. Bug is internal to i915 handling of eDP-1 / PHY A during s2idle resume. ## Silent freeze case (2026-05-30, kernel 7.0.0-22-generic, docked) A separate boot exhibited four consecutive recoverable resume cycles followed by a fifth cycle that hard-froze. Timeline from `journalctl -k -b -3`: ``` 10:31:54 suspend 1: visible PHY A errors → recovered 10:43:44 suspend 2: visible PHY A errors → recovered 11:05:47 suspend 3: visible PHY A errors → recovered 11:17:08 suspend 4: visible PHY A errors → recovered 11:30:54 suspend 5: PM: suspend exit @ 11:30:55 (no PHY A errors logged) 11:30:56 evdi reconnects, displays reinitialize 11:31:02 WiFi reassociates, DisplayLink reconnects 11:31:05 usb 3-9: reset full-speed USB device number 7 using xhci_hcd 11:31:53 cgroup: Unknown subsys name 'memory' ← LAST KERNEL LOG ENTRY ??? HARD FREEZE — no further entries, no watchdog trace ``` Operational symptoms during the freeze: - Desktop on internal display remained visible — last frame held, not black - Keyboard, mouse, and trackpad completely unresponsive - Lid state at freeze: undetermined (user docked, internal display in use) - Recovery required holding the power button (no other path; SSH/SysRq not tried but kernel logging had stopped, suggesting they would not have worked) - Boot session ended at uptime ~5500s (boot at 10:00, freeze at 11:31) This freeze was preceded by a resume that *appeared* clean in dmesg — no PHY A errors logged before the hang. The previous four resume cycles in the same boot all triggered the standard PHY A / DPLL trace but recovered. This suggests the same underlying race can either (a) trigger visible recovery, or (b) lock the entire display pipeline silently — the difference is not yet understood from available logs. The kernel `watchdog: BUG: soft lockup` mechanism does **not** fire for this failure mode. Earlier kernels (6.17.0-1017-oem, 7.0.0-15-generic) produced a visible soft lockup trace in `nvidia- modeset` after ~22 seconds in cases where i915 hung — that downstream effect appears to have been mitigated in 7.0.0-22, but the upstream i915 deadlock that caused those lockups still exists and now hangs silently when it triggers. ## Workarounds attempted (no effect on the bug) - NVIDIA driver upgrade `595.58.03` → `595.71.05` - Kernel upgrade `6.17.0-1017-oem` → `7.0.0-15-generic` → `7.0.0-22-generic` - BIOS upgrade `1.8.1` → `1.9.0` - Dell dock firmware updates (MST VMM9 9.03→9.04, PD 1.34→1.37, WD25TB5 1.0.9→1.0.10, USB4v2 controller, dock package) - Kernel command line already has `i915.enable_psr=0` ## Behavior across kernel versions - **6.17.0-1017-oem / 7.0.0-15-generic**: Bug fired on most s2idle resumes and caused hard system freezes. Soft lockup watchdog visibly triggered in `nvidia-modeset` thread blocked downstream of the stuck i915 state. System unrecoverable without power button reset. Frequency: multiple per week under normal use. - **7.0.0-22-generic**: Bug still fires on every s2idle resume (visible PHY A / DPLL trace in dmesg). i915 timeout-based recovery paths handle most cycles, leaving the system in a degraded display state for 30–75 seconds before continuing. However, occasional cycles result in a complete silent system freeze (see "Silent freeze case" section above) — desktop visible but unresponsive, no kernel trace, no watchdog firing. Hard freeze frequency: at least one per week of normal use with the current workaround in place to avoid most suspends. Without the workaround (allowing GNOME idle suspend), prior measurements suggest higher frequency. The 7.0.0-22 change has eliminated the *visible* soft lockup symptom, but has not fixed the underlying race in PHY A / DPLL state validation during s2idle resume. ## Workaround currently in use Avoid s2idle suspend entirely: ``` # /etc/systemd/logind.conf.d/no-suspend.conf [Login] HandleLidSwitch=lock HandleLidSwitchDocked=ignore HandleLidSwitchExternalPower=lock ``` ``` gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' ``` System runs indefinitely with display blanked when idle. No bug triggered. 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 CasperMD5CheckMismatches: ./casper/initrd ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat May 30 20:33:57 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04c-20251113-97 InstallationDate: Installed on 2026-03-04 (87 days ago) InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20251111) MachineType: Dell Inc. Dell Pro Max 16 Premium MA16250 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=tmux-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash i915.enable_psr=0 nvidia-drm.modeset=1 ipv6.disable=1 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/31/2026 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 061K67 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd03/31/2026:br1.9:efr1.8:svnDellInc.:pnDellProMax16PremiumMA16250:pvr:rvnDellInc.:rn061K67:rvrA02:cvnDellInc.:ct10:cvr:sku0D33:pfaDellProMaxLaptops: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 16 Premium MA16250 dmi.product.sku: 0D33 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154646/+subscriptions

[Bug 2156440] Re: My PC froze inexplicably on Ubuntu Unity 26.04

Hello, since I'm having many bugs on Ubuntu Unity 26.04 I will link to issue tracker threads of ubuntu unity gitlab page where I opened other issue threads... I tried to using Ubuntu Unity with nomodeset and this bug is gone: https://gitlab.com/ubuntu-unity/issue- tracker/-/work_items?show=eyJpaWQiOiIxODIiLCJmdWxsX3BhdGgiOiJ1YnVudHUtdW5pdHkvaXNzdWUtdHJhY2tlciIsImlkIjoxODk5MDQyNDF9 Maybe this bug is related with this one I described here so it's better to take a look of this possibility. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156440 Title: My PC froze inexplicably on Ubuntu Unity 26.04 Status in linux package in Ubuntu: New Bug description: My PC froze inexplicably while I was using it and the loading (stuck) mouse pointer was the only thing that moved. I was ending to watching the WWDC from VLC. It happened some night ago around 00:15, I would provide different details of this issue I could send if only know what it needs, so please let me know what I can do. When the freezing happened I tried to press some combinations of keys (like ctrl + alt + f3, etc.), opened and re-opened the laptop to try the suspension but nothing happened so I pressed the power button. I checked my last journalctl sessions (journalctl --list-boots) and I found the session I described in log.txt (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+attachment/5976875/+files/log.txt) and log2.txt (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+attachment/5977268/+files/log2.txt) I tried to send these messages to ChatGPT and it makes me a summary of what it "thinks" it's the problem: During normal desktop use (Unity session), the system completely froze without any possibility of recovery, including switching to a TTY (Ctrl+Alt+F3). The logs clearly indicate a crash in the graphics subsystem related to the AMD Radeon HD 7310 using the radeon driver. In the minutes leading up to the freeze, there are repeated DRM errors related to video decoding (UVD) and command stream handling, in particular “invalid command stream” and “reloc crossing 256MB boundary”. Shortly after, the kernel reports a GPU lockup (ring 0 stalled), followed by attempts to perform a GPU soft reset, which only partially succeed. At the same time, user-space applications such as the Brave browser lose their GPU context and restart their graphics pipelines, indicating a forced driver reset or loss of GPU context. Overall, the issue does not appear to be a general system crash, but rather a hang in the radeon driver on relatively old hardware, likely triggered by hardware video acceleration. The GPU reset occurs but is not sufficient to restore the graphical session, which remains completely frozen. As a possible hint, this seems consistent with instability of the radeon driver’s UVD path on legacy GPUs, where video decoding or 3D acceleration can trigger a full ring buffer lockup leading to a complete desktop freeze. I tried to speak with a maintainer of Ubuntu Unity and it says me: "it looks like radeon driver has some bugs or even the GPU can sometimes have hardware bugs (which is normal, it doesn't mean that the hardware is faulty)." My Specs: OS: Ubuntu 26.04 LTS (Resolute Raccoon) x86_64 Host: 36852BG (Lenovo B575e) Kernel: Linux 7.0.0-22-generic Uptime: 36 mins Packages: 2824 (dpkg), 29 (flatpak), 7 (snap) Shell: bash 5.3.9 Display (LGD033B): 1366x768 @ 1.05x in 16", 60 Hz DE: Unity 7.7.1 WM: Compiz (X11) Theme: Ambiance [GTK2/3/4] Icons: Humanity-Dark [GTK2/3/4] Font: Ubuntu Sans (11pt) [GTK2/3/4] Cursor: DMZ-White (24px) Terminal: GNOME Terminal 3.58.0 Terminal Font: Ubuntu Sans Mono (11pt) CPU: AMD E1-1500 with Radeon(tm) HD Graphics (2) @ 1.48 GHz GPU: AMD Radeon HD 7310 Memory: 3.58 GiB / 7.14 GiB (50%) Swap: 0 B / 512.00 MiB (0%) Disk (/): 323.23 GiB / 431.79 GiB (75%) - ext4 Local IP (wlp2s0): 192.168.1.19/24 Battery (L09M6Y02): 100% [AC Connected] Locale: it_IT.UTF-8 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 NonfreeKernelModules: wl ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: dinosauro-trex 1829 F.... pulseaudio  /dev/snd/controlC0: dinosauro-trex 1829 F.... pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Jun 11 10:27:15 2026 InstallationDate: Installed on 2026-04-27 (45 days ago) InstallationMedia: Ubuntu-Unity 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp2s0Link:  Error: command ['iw', 'dev', 'wlp2s0', 'link'] failed with exit code 255: command failed: Operation not permitted (-1)  Connected to <hidden-mac> (on wlp2s0)   SSID: <hidden>   freq: 2412.0 MachineType: LENOVO 36852BG ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=124d282b-aef1-4b32-bea3-611a698e355f ro quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2012 dmi.bios.release: 1.6 dmi.bios.vendor: LENOVO dmi.bios.version: HPET68WW(1.06) dmi.board.asset.tag: Not Available dmi.board.name: 36852BG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHPET68WW(1.06):bd12/26/2012:br1.6:svnLENOVO:pn36852BG:pvrLenovoB575e:rvnLENOVO:rn36852BG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3685:pfaLenovoB575e: dmi.product.family: Lenovo B575e dmi.product.name: 36852BG dmi.product.sku: LENOVO_MT_3685 dmi.product.version: Lenovo B575e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+subscriptions

[Bug 2156440] Re: My PC froze inexplicably on Ubuntu Unity 26.04

** Attachment added: "log2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+attachment/5977268/+files/log2.txt ** Description changed: My PC froze inexplicably while I was using it and the loading (stuck) mouse pointer was the only thing that moved. I was ending to watching the WWDC from VLC. It happened some night ago around 00:15, I would provide different details of this issue I could send if only know what it needs, so please let me know what I can do. When the freezing happened I tried to press some combinations of keys (like ctrl + alt + f3, etc.), opened and re-opened the laptop to try the suspension but nothing happened so I pressed the power button. I checked my last journalctl sessions (journalctl --list-boots) and I found the session I described in log.txt (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+attachment/5976875/+files/log.txt) + and log2.txt + (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+attachment/5977268/+files/log2.txt) I tried to send these messages to ChatGPT and it makes me a summary of what it "thinks" it's the problem: During normal desktop use (Unity session), the system completely froze without any possibility of recovery, including switching to a TTY (Ctrl+Alt+F3). The logs clearly indicate a crash in the graphics subsystem related to the AMD Radeon HD 7310 using the radeon driver. In the minutes leading up to the freeze, there are repeated DRM errors related to video decoding (UVD) and command stream handling, in particular “invalid command stream” and “reloc crossing 256MB boundary”. Shortly after, the kernel reports a GPU lockup (ring 0 stalled), followed by attempts to perform a GPU soft reset, which only partially succeed. At the same time, user-space applications such as the Brave browser lose their GPU context and restart their graphics pipelines, indicating a forced driver reset or loss of GPU context. Overall, the issue does not appear to be a general system crash, but rather a hang in the radeon driver on relatively old hardware, likely triggered by hardware video acceleration. The GPU reset occurs but is not sufficient to restore the graphical session, which remains completely frozen. As a possible hint, this seems consistent with instability of the radeon driver’s UVD path on legacy GPUs, where video decoding or 3D acceleration can trigger a full ring buffer lockup leading to a complete desktop freeze. I tried to speak with a maintainer of Ubuntu Unity and it says me: "it looks like radeon driver has some bugs or even the GPU can sometimes have hardware bugs (which is normal, it doesn't mean that the hardware is faulty)." My Specs: OS: Ubuntu 26.04 LTS (Resolute Raccoon) x86_64 Host: 36852BG (Lenovo B575e) Kernel: Linux 7.0.0-22-generic Uptime: 36 mins Packages: 2824 (dpkg), 29 (flatpak), 7 (snap) Shell: bash 5.3.9 Display (LGD033B): 1366x768 @ 1.05x in 16", 60 Hz DE: Unity 7.7.1 WM: Compiz (X11) Theme: Ambiance [GTK2/3/4] Icons: Humanity-Dark [GTK2/3/4] Font: Ubuntu Sans (11pt) [GTK2/3/4] Cursor: DMZ-White (24px) Terminal: GNOME Terminal 3.58.0 Terminal Font: Ubuntu Sans Mono (11pt) CPU: AMD E1-1500 with Radeon(tm) HD Graphics (2) @ 1.48 GHz GPU: AMD Radeon HD 7310 Memory: 3.58 GiB / 7.14 GiB (50%) Swap: 0 B / 512.00 MiB (0%) Disk (/): 323.23 GiB / 431.79 GiB (75%) - ext4 Local IP (wlp2s0): 192.168.1.19/24 Battery (L09M6Y02): 100% [AC Connected] Locale: it_IT.UTF-8 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 NonfreeKernelModules: wl ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: dinosauro-trex 1829 F.... pulseaudio  /dev/snd/controlC0: dinosauro-trex 1829 F.... pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Jun 11 10:27:15 2026 InstallationDate: Installed on 2026-04-27 (45 days ago) InstallationMedia: Ubuntu-Unity 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp2s0Link:  Error: command ['iw', 'dev', 'wlp2s0', 'link'] failed with exit code 255: command failed: Operation not permitted (-1)  Connected to <hidden-mac> (on wlp2s0)   SSID: <hidden>   freq: 2412.0 MachineType: LENOVO 36852BG ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=124d282b-aef1-4b32-bea3-611a698e355f ro quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2012 dmi.bios.release: 1.6 dmi.bios.vendor: LENOVO dmi.bios.version: HPET68WW(1.06) dmi.board.asset.tag: Not Available dmi.board.name: 36852BG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHPET68WW(1.06):bd12/26/2012:br1.6:svnLENOVO:pn36852BG:pvrLenovoB575e:rvnLENOVO:rn36852BG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3685:pfaLenovoB575e: dmi.product.family: Lenovo B575e dmi.product.name: 36852BG dmi.product.sku: LENOVO_MT_3685 dmi.product.version: Lenovo B575e dmi.sys.vendor: LENOVO -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156440 Title: My PC froze inexplicably on Ubuntu Unity 26.04 Status in linux package in Ubuntu: New Bug description: My PC froze inexplicably while I was using it and the loading (stuck) mouse pointer was the only thing that moved. I was ending to watching the WWDC from VLC. It happened some night ago around 00:15, I would provide different details of this issue I could send if only know what it needs, so please let me know what I can do. When the freezing happened I tried to press some combinations of keys (like ctrl + alt + f3, etc.), opened and re-opened the laptop to try the suspension but nothing happened so I pressed the power button. I checked my last journalctl sessions (journalctl --list-boots) and I found the session I described in log.txt (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+attachment/5976875/+files/log.txt) and log2.txt (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+attachment/5977268/+files/log2.txt) I tried to send these messages to ChatGPT and it makes me a summary of what it "thinks" it's the problem: During normal desktop use (Unity session), the system completely froze without any possibility of recovery, including switching to a TTY (Ctrl+Alt+F3). The logs clearly indicate a crash in the graphics subsystem related to the AMD Radeon HD 7310 using the radeon driver. In the minutes leading up to the freeze, there are repeated DRM errors related to video decoding (UVD) and command stream handling, in particular “invalid command stream” and “reloc crossing 256MB boundary”. Shortly after, the kernel reports a GPU lockup (ring 0 stalled), followed by attempts to perform a GPU soft reset, which only partially succeed. At the same time, user-space applications such as the Brave browser lose their GPU context and restart their graphics pipelines, indicating a forced driver reset or loss of GPU context. Overall, the issue does not appear to be a general system crash, but rather a hang in the radeon driver on relatively old hardware, likely triggered by hardware video acceleration. The GPU reset occurs but is not sufficient to restore the graphical session, which remains completely frozen. As a possible hint, this seems consistent with instability of the radeon driver’s UVD path on legacy GPUs, where video decoding or 3D acceleration can trigger a full ring buffer lockup leading to a complete desktop freeze. I tried to speak with a maintainer of Ubuntu Unity and it says me: "it looks like radeon driver has some bugs or even the GPU can sometimes have hardware bugs (which is normal, it doesn't mean that the hardware is faulty)." My Specs: OS: Ubuntu 26.04 LTS (Resolute Raccoon) x86_64 Host: 36852BG (Lenovo B575e) Kernel: Linux 7.0.0-22-generic Uptime: 36 mins Packages: 2824 (dpkg), 29 (flatpak), 7 (snap) Shell: bash 5.3.9 Display (LGD033B): 1366x768 @ 1.05x in 16", 60 Hz DE: Unity 7.7.1 WM: Compiz (X11) Theme: Ambiance [GTK2/3/4] Icons: Humanity-Dark [GTK2/3/4] Font: Ubuntu Sans (11pt) [GTK2/3/4] Cursor: DMZ-White (24px) Terminal: GNOME Terminal 3.58.0 Terminal Font: Ubuntu Sans Mono (11pt) CPU: AMD E1-1500 with Radeon(tm) HD Graphics (2) @ 1.48 GHz GPU: AMD Radeon HD 7310 Memory: 3.58 GiB / 7.14 GiB (50%) Swap: 0 B / 512.00 MiB (0%) Disk (/): 323.23 GiB / 431.79 GiB (75%) - ext4 Local IP (wlp2s0): 192.168.1.19/24 Battery (L09M6Y02): 100% [AC Connected] Locale: it_IT.UTF-8 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 NonfreeKernelModules: wl ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: dinosauro-trex 1829 F.... pulseaudio  /dev/snd/controlC0: dinosauro-trex 1829 F.... pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Jun 11 10:27:15 2026 InstallationDate: Installed on 2026-04-27 (45 days ago) InstallationMedia: Ubuntu-Unity 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp2s0Link:  Error: command ['iw', 'dev', 'wlp2s0', 'link'] failed with exit code 255: command failed: Operation not permitted (-1)  Connected to <hidden-mac> (on wlp2s0)   SSID: <hidden>   freq: 2412.0 MachineType: LENOVO 36852BG ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=124d282b-aef1-4b32-bea3-611a698e355f ro quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2012 dmi.bios.release: 1.6 dmi.bios.vendor: LENOVO dmi.bios.version: HPET68WW(1.06) dmi.board.asset.tag: Not Available dmi.board.name: 36852BG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHPET68WW(1.06):bd12/26/2012:br1.6:svnLENOVO:pn36852BG:pvrLenovoB575e:rvnLENOVO:rn36852BG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3685:pfaLenovoB575e: dmi.product.family: Lenovo B575e dmi.product.name: 36852BG dmi.product.sku: LENOVO_MT_3685 dmi.product.version: Lenovo B575e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156440/+subscriptions

[Bug 2156644] [NEW] GNOME Panel & Activities Overview workspace thumbnails flickering issue

Public bug reported: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec ** 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/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: New Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions

[Bug 2156629] [NEW] Jammy update: v5.15.207 upstream stable release

Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.207 upstream stable release Ported from the following upstream stable releases: v5.15.204, v5.15.205, v5.15.206, v5.15.207 from git://git.kernel.org/ Buffer overflow in drivers/xen/sys-hypervisor.c xen/privcmd: fix double free via VMA splitting Linux 5.15.204 Linux 5.15.205 Linux 5.15.206 x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache Linux 5.15.207 UBUNTU: Upstream stable to v5.15.204, v5.15.205, v5.15.206, v5.15.207 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Noah Wager (nwager) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Noah Wager (nwager) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.207 upstream stable release + + Ported from the following upstream stable releases: + v5.15.204, v5.15.205, v5.15.206, v5.15.207 + from git://git.kernel.org/ - + Buffer overflow in drivers/xen/sys-hypervisor.c + xen/privcmd: fix double free via VMA splitting + Linux 5.15.204 + Linux 5.15.205 + Linux 5.15.206 + x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache Linux 5.15.207 - x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache - x86/CPU/AMD: Add X86_FEATURE_ZEN1 - x86/CPU/AMD: Rename init_amd_zn() to init_amd_zen_common() - x86/CPU/AMD: Call the spectral chicken in the Zen2 init function - x86/CPU/AMD: Add ZenX generations flags - ptrace: slightly saner 'get_dumpable()' logic + UBUNTU: Upstream stable to v5.15.204, v5.15.205, v5.15.206, v5.15.207 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156629 Title: Jammy update: v5.15.207 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.207 upstream stable release Ported from the following upstream stable releases: v5.15.204, v5.15.205, v5.15.206, v5.15.207 from git://git.kernel.org/ Buffer overflow in drivers/xen/sys-hypervisor.c xen/privcmd: fix double free via VMA splitting Linux 5.15.204 Linux 5.15.205 Linux 5.15.206 x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache Linux 5.15.207 UBUNTU: Upstream stable to v5.15.204, v5.15.205, v5.15.206, v5.15.207 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156629/+subscriptions

[Bug 1767324] Re: Extreme regression in battery autonomy with kernel 4.15

[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1767324 Title: Extreme regression in battery autonomy with kernel 4.15 Status in linux package in Ubuntu: Expired Bug description: Since upgrading to kernel 4.15, my laptop (HP Elitebook 850 G3) lasts less than one hour on a fully charged battery. On Ubuntu 17.10 with kernel 4.13, the autonomy was typically in excess of 5 hours. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-lowlatency 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jzimm 3538 F.... pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:10:02 2018 InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-lowlatency N/A linux-backports-modules-4.15.0-20-lowlatency N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767324/+subscriptions

[Bug 2156553] Re: Kernel Panic when download Gemini text

** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156553 Title: Kernel Panic when download Gemini text Status in linux package in Ubuntu: New Bug description: Gemini (Pro) provided some code, which I tried to download using the "down" button. System showed downloaded files dialog box, but soon cursor froze, and I got a screen saying "Kernel Panic" "Please Reboot" "Fatal Exception in Interrupt". No stack trace. Repeatable. Browser is Firefox 151.0.4; acceleration is disabled. journal did not show an clear signs of a crash. Ubuntu 7.0.0-22.22-generic 7.0.0 1 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: george 4498 F.... wireplumber /dev/snd/seq: george 4477 F.... pipewire CasperMD5CheckResult: unknown Date: Thu Jun 11 21:06:23 2026 InstallationDate: Installed on 2026-04-01 (71 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=771d63ca-1644-4fb4-aa72-a91bc92b8c80 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-04 (8 days ago) dmi.bios.date: 02/13/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0Y9N5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd02/13/2020:br1.14:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA00:cvnDellInc.:ct9:cvr:sku06E4:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156553/+subscriptions

[Bug 2156553] [NEW] Kernel Panic when download Gemini text

You have been subscribed to a public bug: Gemini (Pro) provided some code, which I tried to download using the "down" button. System showed downloaded files dialog box, but soon cursor froze, and I got a screen saying "Kernel Panic" "Please Reboot" "Fatal Exception in Interrupt". No stack trace. Repeatable. Browser is Firefox 151.0.4; acceleration is disabled. journal did not show an clear signs of a crash. Ubuntu 7.0.0-22.22-generic 7.0.0 1 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: george 4498 F.... wireplumber /dev/snd/seq: george 4477 F.... pipewire CasperMD5CheckResult: unknown Date: Thu Jun 11 21:06:23 2026 InstallationDate: Installed on 2026-04-01 (71 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=771d63ca-1644-4fb4-aa72-a91bc92b8c80 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-04 (8 days ago) dmi.bios.date: 02/13/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0Y9N5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd02/13/2020:br1.14:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA00:cvnDellInc.:ct9:cvr:sku06E4:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- Kernel Panic when download Gemini text https://bugs.launchpad.net/bugs/2156553 You received this bug notification because you are subscribed to linux in Ubuntu.

[Bug 2156312] Re: Internal display black screen on Intel Lunar Lake with eDP panel

** Changed in: linux (Ubuntu Resolute) Status: New => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156312 Title: Internal display black screen on Intel Lunar Lake with eDP panel Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Internal display goes black after login on Intel Lunar Lake systems with an eDP panel. The external monitor works. The internal display shows as disabled in display settings and cannot be enabled. Hits 100% on affected hardware (3 units, 15/15 attempts). The bug is caused by LOBF (Link Off Between Frames) being enabled on platforms that use the legacy VRR timing generator. Those platforms do not meet the bspec requirement for LOBF (Always-on VRR TG with fixed refresh rate mode). Enabling LOBF incorrectly causes the display to go dark. [Fix] Replace the raw vmin/vmax/flipline comparison with the proper bspec checks: - intel_vrr_always_use_vrr_tg() to gate LOBF on platforms with Always-on VRR TG - intel_vrr_is_fixed_rr() to confirm fixed refresh rate mode Backported from upstream commit 8a517b1e6d8b, merged in v7.1-rc1. [Test Plan] Boot on affected Intel Lunar Lake hardware with an eDP panel. Without patch: internal display is black after login; shows as disabled in display settings. With patch: internal display works normally after login. [Where problems could occur] Could affect intel_alpm.c LOBF configuration logic in the i915 driver. If intel_vrr_always_use_vrr_tg() or intel_vrr_is_fixed_rr() return wrong results on a platform, LOBF would be incorrectly blocked, and Panel Replay power savings would be lost on those machines. The display would still work — it would just not enter LOBF mode. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156312/+subscriptions