@oprizal: you’re probably right that it’s dpm-related, here are the log messages from the crash (which, if anyone is curious, I obtained by running journalctl -b -1 on the next boot):
Feb 13 02:56:46 fedora kernel: amdgpu: [powerplay] No response from smu
Feb 13 02:56:46 fedora kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0
Feb 13 02:56:48 fedora kernel: amdgpu: [powerplay] No response from smu
Feb 13 02:56:50 fedora kernel: amdgpu: [powerplay] No response from smu
Feb 13 02:56:50 fedora kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0
Feb 13 02:56:53 fedora kernel: amdgpu: [powerplay] No response from smu
Feb 13 02:56:55 fedora kernel: amdgpu: [powerplay] No response from smu
Feb 13 02:56:55 fedora kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0
Feb 13 02:56:57 fedora kernel: amdgpu: [powerplay] No response from smu
Feb 13 02:56:59 fedora kernel: amdgpu: [powerplay] No response from smu
Feb 13 02:56:59 fedora kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0
Feb 13 02:57:04 fedora kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
I’ll try the kernel parameter and report back.