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

--- Comment #2 from denisgolovan@yandex.ru --- Created attachment 135553 --> https://bugs.freedesktop.org/attachment.cgi?id=135553&action=edit dmesg

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

Michel Dänzer michel@daenzer.net changed:

What |Removed |Added ---------------------------------------------------------------------------- Attachment #135554|text/x-log |text/plain mime type| |

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

--- Comment #5 from denisgolovan@yandex.ru --- (In reply to Michel Dänzer from comment #4)

We need to find out why the kernel starts returning -EINVAL from the page flip and wait for vblank ioctls.

Can you try writing 255 to /sys/module/drm/parameters/debug before reproducing the problem, and attach the resulting dmesg output? (Note that writing non-0 to /sys/module/drm/parameters/debug will cause a lot of debugging output to be generated, so you'll want to write 0 to it again soon afterwards)

Got it. I'll attach dmesg as soon as I reproduce the issue.

In case that doesn't reveal why -EINVAL is being returned, are you able to recompile the drm.ko / amdgpu.ko kernel modules with a patch applied?

Sure. Gentoo is there :)

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

--- Comment #7 from denisgolovan@yandex.ru --- See attached dmesg with debug. Tearing appeared after turning display on.

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

--- Comment #9 from Michel Dänzer michel@daenzer.net --- Created attachment 135808 --> https://bugs.freedesktop.org/attachment.cgi?id=135808&action=edit Add debugging output why the ioctls return -EINVAL

Sorry, been busy with other fires.

Please recompile the drm.ko module with this patch applied, reproduce the result with the resulting binary and attach the dmesg output.

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

--- Comment #11 from denisgolovan@yandex.ru --- Yes, I fixed some small issues with the patch. Now I have following appear in dmesg: [ 2108.319205] [drm] drm_crtc_vblank_get returned -EINVAL [ 2108.319235] [drm] crtc 0 failed to acquire vblank counter, -22

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

--- Comment #13 from Michel Dänzer michel@daenzer.net --- Created attachment 135923 --> https://bugs.freedesktop.org/attachment.cgi?id=135923&action=edit drm_vblank_get debugging output

Please do the same with this patch, to see why drm_vblank_get returns -EINVAL.

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

--- Comment #15 from Michel Dänzer michel@daenzer.net --- Created attachment 135969 --> https://bugs.freedesktop.org/attachment.cgi?id=135969&action=edit Debugging output related to enabling/disabling the vblank interrupt

Another iteration, to find out why the vblank interrupt doesn't get enabled.

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

--- Comment #17 from Michel Dänzer michel@daenzer.net --- Thanks. I think I see what's happening, but I need some time to think about how to address it.

Meanwhile, you should be able to re-enable TearFree by forcing a modeset, e.g. by re-enabling the TearFree property:

xrandr --output DisplayPort-0 --set TearFree on

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

--- Comment #19 from denisgolovan@yandex.ru --- Still better to have a proper fix first as New Year present to us (poor users) ;)

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

--- Comment #21 from Michel Dänzer michel@daenzer.net --- (In reply to Anthony Parsons from comment #18)

Running xrandr doesn't seem to work as a workaround but flipping VTs does.

Have you tried turning it off and on again? (Who gets the reference? :)

xrandr --output DisplayPort-0 --set TearFree off xrandr --output DisplayPort-0 --set TearFree on