<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [CI] igt@gem_busy@extended-* - fail - Failed assertion: write[0] == ring - and skips on other gem tests."
   href="https://bugs.freedesktop.org/show_bug.cgi?id=105248">105248</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[CI] igt@gem_busy@extended-* - fail - Failed assertion: write[0] == ring - and skips on other gem tests.
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DRI
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>DRI git
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>DRM/Intel
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>marta.lofstedt@intel.com
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Starting at:
<a href="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-kbl2/igt@gem_busy@extended-bsd1.html</a>
<a href="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-kbl7/igt@gem_busy@extended-bsd2.html</a>
<a href="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-kbl1/igt@gem_busy@extended-parallel-blt.html</a>
<a href="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-bsd1.html</a>
<a href="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-kbl6/igt@gem_busy@extended-parallel-bsd2.html</a>
<a href="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-kbl2/igt@gem_busy@extended-parallel-render.html</a>
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl7/igt@gem_busy@extended-parallel-vebox.html">https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4292/shard-kbl7/igt@gem_busy@extended-parallel-vebox.html</a>

(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 <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
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).</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
          <li>You are the QA Contact for the bug.</li>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>