https://bugs.freedesktop.org/show_bug.cgi?id=108037

--- Comment #3 from Öyvind Saether oyvinds@everdot.org --- (In reply to Michel Dänzer from comment #1)

Can you bisect? P.S. FYI, this is what's called an oops, not a panic.

oops, then. yes I now know how to bisect. I can.

(In reply to Alex Deucher from comment #2)

When you say turn them off/on, do you mean via software (e.g., dpms) or via the switch on the monitor?

I used the actual power button on the monitors that have them and the stupid joystick thing on the third monitor (works like a button) when this first happens but I just found that it doesn't matter, triggered it on 4.18.9 with dpms too.

On 4.18.9:

set xscreensaver to immediately turn monitors off with dpms lock screen wait for monitors go into suspend press button on keyboard monitors don't come back on, system freeze

will attach same-problem-4.18.9.txt with that one. 4.18.5 is fine. I notice there was a lot of amdgpu changes between 4.18.7 and 4.18.8 in the log. I have used 4.19 git kernels for some time and this didn't happen to me until 4.19rc4 but that could simply be because I didn't turn off the monitors(???).

bisecting will take time.