https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #76 from dwagner jb5sgc1n.nya@20mm.eu --- Just for the record, since another month has passed: I can still reproduce the crash with today's git head of amd-staging-drm-next within minutes.
As a bonus bug, with today's git head I also get unexplainable "minimal" memory and shader clock values - and a doubled power consumption (12W instead of 6W) for my default 3840x2160 60Hz display mode in comparison to last month's drm-next of the day:
cd /sys/class/drm/card0/device
xrandr --output HDMI-A-0 --mode 3840x2160 --rate 30 echo manual >power_dpm_force_performance_level echo 0 >pp_dpm_mclk echo 0 >pp_dpm_sclk grep -H \* pp_dpm_mclk pp_dpm_sclk
pp_dpm_mclk:0: 300Mhz * pp_dpm_sclk:0: 214Mhz *
xrandr --output HDMI-A-0 --mode 3840x2160 --rate 50 echo manual >power_dpm_force_performance_level echo 0 >pp_dpm_mclk echo 0 >pp_dpm_sclk grep -H \* pp_dpm_mclk pp_dpm_sclk
pp_dpm_mclk:1: 1750Mhz * pp_dpm_sclk:1: 481Mhz *
xrandr --output HDMI-A-0 --mode 3840x2160 --rate 60 echo manual >power_dpm_force_performance_level echo 0 >pp_dpm_mclk echo 0 >pp_dpm_sclk grep -H \* pp_dpm_mclk pp_dpm_sclk
pp_dpm_mclk:0: 300Mhz * pp_dpm_sclk:6: 1180Mhz *
But that power consumption issue is negligible in comparison to the show-stopping crashes that are the topic of this bug report.