└─[$] <> 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.3 for AMD Radeon Vega 8 Graphics (radeonsi, raven, LLVM 19.1.6, DRM 3.59, 6.12.8-2-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 Jan 12 23:24:31 tumbleweed-msi kernel: [drm] amdgpu kernel modesetting enabled. Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: Virtual CRAT table created for CPU Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: Topology: Add CPU node Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: enabling device (0006 -> 0007) Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: Fetched VBIOS from VFCT Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: ATOM BIOS: 113-PICASSO-118 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: vgaarb: deactivate vga console Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF Jan 12 23:24:31 tumbleweed-msi kernel: [drm] amdgpu: 2048M of VRAM memory ready Jan 12 23:24:31 tumbleweed-msi kernel: [drm] amdgpu: 6950M of GTT memory ready. Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: hwmgr_sw_init smu backed is smu10_smu Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: reserve 0x400000 from 0xf47fc00000 for PSP TMR Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: RAS: optional ras ta ucode is not available Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: RAP: optional rap ta ucode is not available Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7) Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4) Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: Secure display: Generic Failure. Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0 Jan 12 23:24:31 tumbleweed-msi kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart Jan 12 23:24:31 tumbleweed-msi kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: Virtual CRAT table created for GPU Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: Topology: Add dGPU node [0x15d8:0x1002] Jan 12 23:24:31 tumbleweed-msi kernel: kfd kfd: amdgpu: added device 1002:15d8 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 11, active_cu_number 8 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8 Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: pp_dpm_get_sclk_od was not implemented. Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu: pp_dpm_get_mclk_od was not implemented. Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: amdgpu: Runtime PM not available Jan 12 23:24:31 tumbleweed-msi kernel: [drm] Initialized amdgpu 3.59.0 for 0000:30:00.0 on minor 1 Jan 12 23:24:31 tumbleweed-msi kernel: fbcon: amdgpudrmfb (fb0) is primary device Jan 12 23:24:31 tumbleweed-msi kernel: amdgpu 0000:30:00.0: [drm] fb0: amdgpudrmfb frame buffer device Jan 12 23:24:47 tumbleweed-msi kernel: snd_hda_intel 0000:30:00.1: bound 0000:30:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Informational messages can generally be disregarded. As for functional bugs you can file them here: https://gitlab.freedesktop.org/drm/amd/-/issues
Also, you don't post multiple issues as a single bug report. Split them and post separately.
(In reply to Artem S. Tashkinov from comment #1) > Informational messages can generally be disregarded. > > As for functional bugs you can file them here: > > https://gitlab.freedesktop.org/drm/amd/-/issues (In reply to Artem S. Tashkinov from comment #2) > Also, you don't post multiple issues as a single bug report. > > Split them and post separately. Thank you for responding PSP (Platform Security Processor) Issues: https://gitlab.freedesktop.org/drm/amd/-/issues/3897 Secure Display Issues: https://gitlab.freedesktop.org/drm/amd/-/issues/3898 Power Management Issue: https://gitlab.freedesktop.org/drm/amd/-/issues/3899 Missing TA (Trusted Application) Components: https://gitlab.freedesktop.org/drm/amd/-/issues/3900
AMD GPU developers aren't here. There's no point in keeping this bug report open.