[Bug 109618] New: Intel TearFree feature stops working at random

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 13 01:19:29 UTC 2019


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

            Bug ID: 109618
           Summary: Intel TearFree feature stops working at random
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/intel
          Assignee: chris at chris-wilson.co.uk
          Reporter: sultan at kerneltoast.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org

Created attachment 143369
  --> https://bugs.freedesktop.org/attachment.cgi?id=143369&action=edit
Xorg config info

On multiple different Intel machines running Arch Linux, the TearFree option
works great but it randomly stops working completely and requires a xorg
restart to make it work again. I haven't observed any log messages produced
when TearFree stops working. Running an application in full-screen mode (such
as watching a YouTube video in full-screen mode) seems to be the most frequent
way to reproduce the issue.

When TearFree stops working, it is graceful and the only indication that it has
stopped working is that vsync tearing is suddenly present. I have experienced
this issue intermittently for several months, so it's likely not a (recent)
regression. This issue is noticeable to me because I don't use a window manager
to smooth out vsync tearing, and instead rely on the TearFree feature to do so.

Any suggestions on how to go about collecting debugging information for this?
I've attached a xorg log that contains information about my
system/configuration but nothing remarkable about this bug itself.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190213/6054e03b/attachment.html>


More information about the intel-gfx-bugs mailing list