[Bug 102856] [bdw hsw] many intermittent dEQP regressions

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 102856
           Summary: [bdw hsw] many intermittent dEQP regressions
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: jason at jlekstrand.net
          Reporter: mark.a.janes at intel.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org
                CC: chadversary at chromium.org, daniel at fooishbar.org,
                    topi.pohjolainen at intel.com

Beginning with 0699319bb0c3fb247e748e26a8158a0397c80632, thousands of
intermittent assertions occur in Intel's mesa CI, with the following assertion:

mesa/drivers/dri/i965/intel_mipmap_tree.c:2079: get_ccs_d_resolve_op: Assertion
`!"Invalid aux state for CCS_D"' failed.


The problematic series ends with:
Author:     Jason Ekstrand <jason at jlekstrand.net>

i965: Use prepare_external instead of make_shareable in setTexBuffer2

The setTexBuffer2 hook from GLX is used to implement glxBindTexImageEXT
which has tighter restrictions than just "it's shared".  In particular,
it says that any rendering to the image while it is bound causes the
contents to become undefined.  This means that we can do whatever aux
tracking we want between glxBindTexImageEXT and glxReleaseTexImageEXT so
long as we always transition from external in Bind and to external in
Release.

The fact that we were using make_shareable before was a problem because
it would resolve away 100% of the aux data and then throw away our
reference to the aux buffer.  If the aux data was shared with some other
application (i.e. if we're using I915_FORMAT_MOD_Y_TILED_CCS) then we
would forget that the aux data even existed for the rest of eternity.
This is fine for the first frame but any subsequent calls to
glxBindTexImageEXT would bind the texture as if it has no aux
whatsoever and no resolves would happen and texturing would happen as if
there is no aux.  This was causing rendering corruption in mutter when
running on top of X11 with modifiers.

Reviewed-by: Topi Pohjolainen <topi.pohjolainen at intel.com>
Reviewed-by: Daniel Stone <daniels at collabora.com>
Reviewed-by: Chad Versace <chadversary at chromium.org>

Mesa's CI is unusable due to this issue, because the large number of
intermittent tests cannot be disabled or attributed to a commit, creating noise
in all CI results.

The issue has been mostly fixed by a patch awaiting review:
https://patchwork.freedesktop.org/patch/177582/

-- 
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-3d-bugs/attachments/20170919/7ec4f55a/attachment.html>