Bug 208587 - amdgpu hang and gnome shell crash if playing video on 5600M with DRI_PRIME
Summary: amdgpu hang and gnome shell crash if playing video on 5600M with DRI_PRIME
Status: RESOLVED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-16 18:37 UTC by dani
Modified: 2020-07-29 19:27 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.8.0-rc5
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (107.81 KB, text/plain)
2020-07-16 18:37 UTC, dani
Details

Description dani 2020-07-16 18:37:05 UTC
Created attachment 290321 [details]
dmesg

On my Dell Inc. G5 5505 the Gnome Shell Wayland session crashes when I try to watch a video with "DRI_PRIME=1 firefox" on the AMD 5600M I get the following kernel error messages

[Do Jul 16 20:16:03 2020] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.
[Do Jul 16 20:16:03 2020] [drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0
[Do Jul 16 20:16:03 2020] ------------[ cut here ]------------
[Do Jul 16 20:16:03 2020] WARNING: CPU: 7 PID: 181 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3194 dcn20_validate_bandwidth_fp+0x7a/0xb0 [amdgpu]

CPU Brand:  AMD Ryzen 7 4800H with Radeon Graphics   

Operating System Version:
    "Arch Linux" (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.8.0-rc5-1-mainline
    Window Manager:  GNOME Shell (Wayland)
    Firefox 78

DRI_PRIME=1 glxinfo

Device: AMD Radeon RX 5600M (NAVI10, DRM 3.38.0, 5.8.0-rc5-1-mainline, LLVM 10.0.0) (0x731f)
    Version: 20.1.3

DRI_PRIME=0 glxinfo

    Device: AMD RENOIR (DRM 3.38.0, 5.8.0-rc5-1-mainline, LLVM 10.0.0) (0x1636)
    Version: 20.1.3
Comment 1 Alex Deucher 2020-07-17 04:36:48 UTC
Does appending amdgpu.runpm=0 to the kernel command line in grub fix the issue?

Note You need to log in before you can comment on or make changes to this bug.