https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #32 from L.S.S. <ragnaros39...@yandex.com> ---
So it seems there definitely is a regression on 4.17 on this issue (the patches
are not required as the lines were already there in 4.17). This time it isn't a
kernel panic, but an "invalid opcode" error caused by dm_update_crtcs_state
that was called by amdgpu_dm_atomic_check.
The issue is not 100% reproducible, but still means going to standby with an
AMD GPU and DC is still dangerous and may result in losses of unsaved work.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel