Comment # 2 on bug 1225147 from llyyr

(In reply to Takashi Iwai from comment #1)
> It's quite difficult to debug without any logs, unfortunately.
> You can try to set up kdump and get the kernel crash dump (at least the
> dmesg output), too.  If it were a kernel panic, the crash dump will be
> triggered automatically.  Other than that, you can trigger manually via
> magic sysrq-c.

I bisected it down to amdgpu changes in 6.7-rc1 and reported it upstream here
https://gitlab.freedesktop.org/drm/amd/-/issues/3403

Unfortunately I can't bisect it down to a specific commit because amdgpu is
broken at random commits in that tree