[Bug 93679] New: Heavy tearing with xf86-video-intel

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 93679
           Summary: Heavy tearing with xf86-video-intel
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: carstenmattner at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

I'm consistently seeing heavy tearing in Firefox and mpv on Intel HD
Graphics 3000 (i7 2640M), even with _any combination_ of the following
xorg.conf settings. Tested on linux 4.1.15 and 4.3.3.

   Option      "DRI"         "3"/"2"
   Option      "TearFree"    "true"/"false"
   Option      "SwapbuffersWait" "true"/"false"
   Option      "AccelMethod" "glamor"/"sna"

It happens with all video-out modes in mpv (x11, xv, vaapi, opengl,
opengl-hq), with or without vaapi decoding. The only way to avoid this
is by running 'compton --backend xr_glx_hybrid --vsync opengl-swc. But
this is a workaround that forces vsync unconditionally for everything,
anytime, with its disadvantages.

Aren't TearFree and SwapbuffersWait supposed to prevent this?

On 945GM, with no custom Xorg configuration, I see minimal tearing in
Firefox and sometimes mpv, which also can be worked around with forced
vsync. Tested on linux 4.1.15.

Distro: Arch Linux
Kernel: 4.1.15 and 4.3.3
Driver: xf86-video-intel 1:2.99.917+519+g8229390
Xorg: xorg-server 1.18.0-4
mpv: 0.14.0

There are no warnings or errors in any of the logs.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160112/15ba063f/attachment.html>