[Bug 102457] New: [BAT][GLK] igt at kms_frontbuffer_tracking@basic requires igt_require_gem

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Aug 28 15:48:07 UTC 2017


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

            Bug ID: 102457
           Summary: [BAT][GLK] igt at kms_frontbuffer_tracking@basic requires
                    igt_require_gem
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: martin.peres at free.fr
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

On CI_DRM_3011, the machine fi-glk-2a hit the following issue when running
igt at kms_frontbuffer_tracking@basic:

(kms_frontbuffer_tracking:3506) intel-batchbuffer-CRITICAL: Test assertion
failure function intel_batchbuffer_flush_on_ring, file intel_batchbuffer.c:184:
(kms_frontbuffer_tracking:3506) intel-batchbuffer-CRITICAL: Failed assertion:
(drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0
(kms_frontbuffer_tracking:3506) intel-batchbuffer-CRITICAL: Last errno: 5,
Input/output error

This appears to be due to the test igt at gem_exec_suspend@basic-s3 htting the
WARN_ON(wait_for_engine(engine, 50))
(https://bugs.freedesktop.org/show_bug.cgi?id=102456) which led to a jammed
GEM. Many tests just skip after that, but this test apparently is relying on
GEM without testing for its availability using igt_require_gem.

Full logs:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3011/fi-glk-2a/igt@kms_frontbuffer_tracking@basic.html

-- 
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170828/6033a363/attachment.html>


More information about the intel-gfx-bugs mailing list