[Bug 1234732] New: System Freeze with AMD Vega GPUs After Mesa 24.3.x Update & Kernel Logs Reveal Multiple AMD Driver Issues
https://bugzilla.suse.com/show_bug.cgi?id=1234732 Bug ID: 1234732 Summary: System Freeze with AMD Vega GPUs After Mesa 24.3.x Update & Kernel Logs Reveal Multiple AMD Driver Issues Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: dacia.mountable282@aleeas.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Environment: Distribution: OpenSUSE TW GPU: AMD Vega (Picasso architecture) DE/WM: KDE Plasma (Wayland) Detailed Problem Description: I am experiencing critical system stability issues with my AMD graphics card after updating to Mesa 24.3.x (specifically, Mesa 24.3.0 and above). The system completely freezes after just a few minutes of use, rendering the computer unresponsive. I am unable to interact with the system, and the only solution is to perform a hard reboot. This issue is consistent across both X11 and Wayland environments and primarily affects Chromium-based browsers. Symptoms: The system experiences a complete freeze after a short period of use, typically within minutes, especially when using Chromium-based browsers. No apparent trigger or consistent pattern for the freeze. The system becomes unresponsive, requiring a hard reboot to recover. Driver and GPU Information: └─[$] vainfo Trying display: wayland libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.22 (libva 2.22.0) vainfo: Driver version: Mesa Gallium driver 24.3.1 for AMD Radeon Vega 8 Graphics (radeonsi, raven, LLVM 19.1.5, DRM 3.59, 6.11.8-1-default) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc Kernel Logs Reveal Multiple AMD Driver Issues: 1. PSP (Platform Security Processor) Failures: - Failed PSP commands: `LOAD_TA` and `INVOKE_CMD` - Secure display generic failure - PSP-related command responses returning error status 2. Missing Critical GPU Functionalities: - RAS (Reliability, Availability, and Serviceability) Trusted Application unavailable - RAP Trusted Application not available 3. Power Management Limitations: - Runtime Power Management (PM) not available └─[$] sudo journalctl -b -1 -g amdgpu Dec 18 17:59:39 tumbleweed-msi kernel: [drm] amdgpu kernel modesetting enabled. Dec 18 17:59:39 tumbleweed-msi kernel: amdgpu: Virtual CRAT table created for CPU Dec 18 17:59:39 tumbleweed-msi kernel: amdgpu: Topology: Add CPU node Dec 18 17:59:39 tumbleweed-msi kernel: amdgpu 0000:30:00.0: enabling device (0006 -> 0007) Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: Fetched VBIOS from VFCT Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu: ATOM BIOS: 113-PICASSO-118 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: vgaarb: deactivate vga console Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF Dec 18 17:59:40 tumbleweed-msi kernel: [drm] amdgpu: 2048M of VRAM memory ready Dec 18 17:59:40 tumbleweed-msi kernel: [drm] amdgpu: 6950M of GTT memory ready. Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu: hwmgr_sw_init smu backed is smu10_smu Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: reserve 0x400000 from 0xf47fc00000 for PSP TMR Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: RAS: optional ras ta ucode is not available Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: RAP: optional rap ta ucode is not available Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7) Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4) Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: Secure display: Generic Failure. Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0 Dec 18 17:59:40 tumbleweed-msi kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart Dec 18 17:59:40 tumbleweed-msi kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu: Virtual CRAT table created for GPU Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu: Topology: Add dGPU node [0x15d8:0x1002] Dec 18 17:59:40 tumbleweed-msi kernel: kfd kfd: amdgpu: added device 1002:15d8 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 11, active_cu_number 8 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Dec 18 17:59:40 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Dec 18 17:59:40 tumbleweed-ms -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234732 Dacia Mountable <dacia.mountable282@aleeas.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major Found By|--- |Community User Target Milestone|--- |Current Priority|P5 - None |P2 - High -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234732 Dacia Mountable <dacia.mountable282@aleeas.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234732 Dacia Mountable <dacia.mountable282@aleeas.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234732 https://bugzilla.suse.com/show_bug.cgi?id=1234732#c1 Sjoerd <suse@brinkmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse@brinkmail.org --- Comment #1 from Sjoerd <suse@brinkmail.org> --- I'm also experiencing system freezes on my AMD system since a couple of weeks on Tumbleweed. I used an older snapshot for a while hoping updates would fix it, but that snapshot has become to old to use, and my system still freezes with the latest updates. I can't really pinpoint what causes the freezes, they just happen. Sometimes within a few minutes, sometimes hours. I don't use Chromium, but I do sometimes use Falkon which is a derivative. My CPU is an AMD Ryzen 5 3400G with Radeon Vega Graphics. I found a thread on the Arch forum with the same problem: https://bbs.archlinux.org/viewtopic.php?id=301849 And they linked to this thread on the freedesktop forum: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12310#note_2705331 My journalctl from right before I hard resetted my system: Dec 17 11:11:45 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:11:45 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:12:10 sephora systemd[1]: systemd-hostnamed.service: Deactivated successfully. Dec 17 11:13:49 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:13:49 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:14:16 sephora kernel: perf: interrupt took too long (3944 > 3935), lowering kernel.perf_event_max_sample_rate to 50700 Dec 17 11:14:22 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:14:22 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:14:24 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:14:24 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:14:26 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:14:26 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:15:11 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:15:11 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:15:11 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:15:18 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:15:18 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:15:18 sephora kwin_wayland[2206]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Dec 17 11:15:33 sephora kwin_wayland[2206]: kwin_xwl: Could not create a source from 0x56089e1e7120 0 Dec 17 11:15:37 sephora kwin_wayland[2206]: kwin_xwl: Could not create a source from 0x7f21e40869c0 0 Dec 17 11:15:59 sephora kwin_wayland[2206]: kwin_xwl: Could not create a source from 0x7f21e4009730 0 Dec 17 11:16:20 sephora kwin_wayland[2206]: kwin_xwl: Could not create a source from 0x7f21e4003450 0 Dec 17 11:16:30 sephora kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx timeout, signaled seq=3581631, emitted seq=3581633 Dec 17 11:16:30 sephora kernel: amdgpu 0000:07:00.0: amdgpu: Process information: process kwin_wayland pid 2206 thread kwin_wayla:cs0 pid 2242 Dec 17 11:16:30 sephora kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset begin! Dec 17 11:16:56 sephora kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [kworker/u32:1:46287] Dec 17 11:16:56 sephora kernel: Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace sunrpc netfs snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_packet nft_fib_inet n> Dec 17 11:16:56 sephora kernel: loop fuse efi_pstore configfs nfnetlink dmi_sysfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee hid_generic usbhid amdgpu crct10dif_pclmul crc32_p> Dec 17 11:16:57 sephora kwin_wayland[2206]: kwin_scene_opengl: 0x2: GL_CONTEXT_LOST in context lost Dec 17 11:16:57 sephora kwin_wayland[2206]: kwin_scene_opengl: 0x2: GL_CONTEXT_LOST in context lost Dec 17 11:16:57 sephora kwin_wayland[2206]: kwin_scene_opengl: 0x2: GL_CONTEXT_LOST in context lost -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234732 https://bugzilla.suse.com/show_bug.cgi?id=1234732#c2 Yash Shirsat <yashshirsat60@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yashshirsat60@gmail.com --- Comment #2 from Yash Shirsat <yashshirsat60@gmail.com> --- System Specs : Ryzen 5 2400g | 4*2 GB DD4 Corsair Ram | Crucial M.2 SSD 500GB | ASUS B450M-A Environment : Operating System: openSUSE Tumbleweed 20241208 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 Kernel Version: 6.11.8-1-default (64-bit) Graphics Platform: Wayland journalctl -b File : https://justpaste.it/fzv13 Detailed Problem Description: I have been facing an issue with my KDE environment freezing, which started this month. The system sometimes works perfectly for the whole day, but at other times, it freezes unexpectedly, even with minimal workload. Here are the scenarios when this happens: • Sometimes right after turning the system on. • While browsing on Firefox (it freezes if I open multiple tabs quickly or close Firefox). • Randomly, such as: Watching a YouTube video (even with only one browser tab open). Playing media in VLC and opening a second file quickly, which can cause the system to hang. Closing multiple tasks/activities quickly. i have this PC for 5 system for 5 year now (motherboard changed 2 year ago) as i think its hardware issue but not able diagnose it fully on Linux so please help me out with this one Also after reading this others comments on this i fill like i also have same which i can't able diagnose -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234732 Dacia Mountable <dacia.mountable282@aleeas.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P0 - Crit Sit -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com