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
[Bug 2156559] Re: Fix no sound output device on Dell GhostRider PTL no camera SKU
** 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/2156559 Title: Fix no sound output device on Dell GhostRider PTL no camera SKU Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Resolute: In Progress Bug description: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156559/+subscriptions
[Bug 2156559] [NEW] Fix no sound output device on Dell GhostRider PTL no camera SKU
Public bug reported: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: In Progress ** Tags: jira-wtn-416 oem-priority wtn ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Tags added: jira-wtn-416 oem-priority wtn -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156559 Title: Fix no sound output device on Dell GhostRider PTL no camera SKU Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Resolute: In Progress Bug description: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156559/+subscriptions
среда
[Bug 2148538] Re: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350
Set verification-done due to positive test result from user. ** Tags removed: verification-needed-noble-linux-oem-6.17 ** Tags added: verification-done-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148538 Title: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350 Status in linux package in Ubuntu: Confirmed 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: Fix Committed Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: I have a Lenovo ThinkPad P14s Gen 6 AMD Ryzen AI 7 pro 350 I have installed - 24.04 LTS - 6.17.0-1017-oem - linux-image-6.17.0-1017-oem 6.17.0-1017.17 Regularly (at this point, seems to happen once per day), the kernel locks up (actually, let me amend that; I just noticed that the key combination I thought would go into terminal mode doesn't do that, so I don't know if the kernel has locked up or gnome has frozen). I haven't been able to identify particular workloads that are causing this behavior. At any given instance, I am running firefox, brave, mattermost, vs code, multiple terminal sessions, obsidian, perhaps some qemu vms (no GUI). Looking at the journal, after one recent lockup, I saw the following: amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. workqueue: amdgpu_tlb_fence_work [amdgpu] hogged CPU for >13333us 35 times, consider switching to WQ_UNBOUND amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. INFO: task kworker/7:0:37823 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/7:0 state:D stack:0 pid:37823 tgid:37823 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:0:39916 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:0 state:D stack:0 pid:39916 tgid:39916 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/12:4:40454 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/12:4 state:D stack:0 pid:40454 tgid:40454 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/5:4:40750 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/5:4 state:D stack:0 pid:40750 tgid:40750 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:3:40825 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:3 state:D stack:0 pid:40825 tgid:40825 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:8:40844 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:8 state:D stack:0 pid:40844 tgid:40844 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:9:40845 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:9 state:D stack:0 pid:40845 tgid:40845 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:2:41419 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:2 state:D stack:0 pid:41419 tgid:41419 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:0:41524 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:0 state:D stack:0 pid:41524 tgid:41524 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? _raw_spin_lock_irqsave+0xe/0x20 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:0:42116 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:0 state:D stack:0 pid:42116 tgid:42116 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. Supervising 9 threads of 6 processes of 1 users. Supervising 9 threads of 6 processes of 1 users. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. kauditd_printk_skb: 4 callbacks suppressed SRU Justification: [ Impact ] On Lenovo ThinkPad P14s Gen 6 systems with AMD Ryzen AI 7 PRO 350, the system can lock up under graphical workloads. Kernel logs show the AMDGPU MES ring buffer becoming full and hung task reports involving amdgpu_tlb_fence_work. The issue is caused by commit f3854e04b708 ("drm/amdgpu: attach tlb fence to the PTs update") which attaches TLB fences too broadly and can flood KIQ/MES TLB invalidation work. [ Fix ] Backport upstream fixes: - d967509651601 ("drm/amdgpu: make sure userqs are enabled in userq IOCTLs") - 9163fe4d790f (Revert "drm/amdgpu: don't attach the tlb fence for SI") - e9f58ff991dd ("drm/amdgpu: rework how we handle TLB fences") [ Test Plan ] 1. Boot the affected Lenovo P14s Gen 6 AMD Ryzen AI 7 PRO 350 system. 2. Exercise the graphical workload that previously reproduced the lockup. 3. Verify the system remains responsive and dmesg does not show MES ring buffer full or amdgpu_tlb_fence_work hung task messages. A test kernel with this fix series ran for 12 hours on the affected system without reproducing the lockup (LP #2148538 comment #29). [ Where problems could occur ] Regressions could appear as GPU hangs, failed VM updates, TLB flush failures, or user queue/KFD workload failures on AMD GPUs. [ Other Info ] Noble linux is not affected (offending commit absent). Resolute linux is not affected (fixes already present). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148538/+subscriptions
[Bug 2156421] [NEW] bug on keyboard keys kernel 7
Public bug reported: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156421 Title: bug on keyboard keys kernel 7 Status in linux package in Ubuntu: New Bug description: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156421/+subscriptions