Long-tracked (and apparently hard to pinpoint) bug in the AMD graphics stack, it seems. Since you have a very reproducible case it’s worth posting about it in the AMDGPU driver bugtracker thread
Workaround is to add a kernel command line argument (which I have also had active since I opened that issue):