[Bug 105248] New: [CI] igt at gem_busy@extended-* - fail - Failed assertion: write[0] == ring - and skips on other gem tests.

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 105248
           Summary: [CI] igt at gem_busy@extended-* - fail - Failed
                    assertion: write[0] == ring - and skips on other gem
                    tests.
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: marta.lofstedt at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Starting at:
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl2/igt@gem_busy@extended-bsd1.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl7/igt@gem_busy@extended-bsd2.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl1/igt@gem_busy@extended-parallel-blt.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl6/igt@gem_busy@extended-parallel-bsd1.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl6/igt@gem_busy@extended-parallel-bsd2.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl2/igt@gem_busy@extended-parallel-render.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl7/igt@gem_busy@extended-parallel-vebox.html

(gem_busy:1919) CRITICAL: Test assertion failure function one, file
gem_busy.c:270:
(gem_busy:1919) CRITICAL: Failed assertion: write[0] == ring
(gem_busy:1919) CRITICAL: error: 2 != 8194
Subtest extended-bsd1 failed.

Also, a lot of gem_busy and gem_exec subtests started skipping after the same
commit.

This issue is repeated on all IGT runs IGT_4292 - IGT_4297. 
Note, for the runs I am referring to; IGT_4292 - IGT_4297, have both the same
IGT commit and kernel.    

IGT-Version: 1.21-g305ebced (x86_64) (Linux: 4.16.0-rc2-CI-CI_DRM_3830+ x86_64)

The test look OK on CI_DRM_3830, this is the IGT commit that was integrated to
IGT_4292:

commit 305ebcedc36e98f3118ac27a5bbde0ce7cd71a74
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Wed Feb 21 14:13:16 2018 +0000

    Iterate over physical engines

    We current have a single for_each_engine() iterator which we use to
    generate both a set of uABI engines and a set of physical engines.
    Determining what uABI ring-id corresponds to an actual HW engine is
    tricky, so pull that out to a library function and introduce
    for_each_physical_engine() for cases where we want to issue requests
    once on each HW ring (avoiding aliasing issues).

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