<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - [BYT]Some subcases of igt/gem_exec_parse fails"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=78426">78426</a>
          </td>
        </tr>

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

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

        <tr>
          <th>Summary</th>
          <td>[BYT]Some subcases of igt/gem_exec_parse fails
          </td>
        </tr>

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

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

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

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

        <tr>
          <th>Reporter</th>
          <td>jinxianx.guo@intel.com
          </td>
        </tr>

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

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

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

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

        <tr>
          <th>Product</th>
          <td>DRI
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Created <span class=""><a href="attachment.cgi?id=98666" name="attach_98666" title="dmesg">attachment 98666</a> <a href="attachment.cgi?id=98666&action=edit" title="dmesg">[details]</a></span>
dmesg

*System Environment:
--------------------------
Regression: No.  
The cases always fails

Non-working platforms: BYT

 *kernel: 
--------------------------
-nightly: dd28119c31cf06fc4c3bb548699018a91e45a676 (fails)
-queued: 1cf0ba14740d96fbf6f58a201f000a34b74f4725 (fails)
    Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
    Date:   Mon May 5 09:07:33 2014 +0100

    drm/i915: Flush request queue when waiting for ring space

    During the review of

    commit 1f70999f9052f5a1b0ce1a55aff3808f2ec9fe42
    Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
    Date:   Mon Jan 27 22:43:07 2014 +0000

        drm/i915: Prevent recursion by retiring requests when the ring is full

    Ville raised the point that our interaction with request->tail was
    likely to foul up other uses elsewhere (such as hang check comparing
    ACTHD against requests).

    However, we also need to restore the implicit retire requests that certain
    test cases depend upon (e.g. igt/gem_exec_lut_handle), this raises the
    spectre that the ppgtt will randomly call i915_gpu_idle() and recurse
    back into intel_ring_begin().

    Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
    Bugzilla: <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - [PNV/HSW/BDW bisected]igt/gem_exec_lut_handle is slow"
   href="show_bug.cgi?id=78023">https://bugs.freedesktop.org/show_bug.cgi?id=78023</a>
    Reviewed-by: Brad Volkin <<a href="mailto:bradley.d.volkin@intel.com">bradley.d.volkin@intel.com</a>>
    [danvet: Remove now unused 'tail' variable as spotted by Brad.]
    Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>


-fixes: e4c610fe051579ba0a1fadf339905b0231c6ef94 (skips)
    Author: Egbert Eich <<a href="mailto:eich@suse.de">eich@suse.de</a>>
    Date:   Fri Apr 11 19:07:44 2014 +0200

    drm/i915/SDVO: For sysfs link put directory and target in correct order

    When linking the i2c sysfs file into the connector's directory
    pass directory and link target in the right order.
    This code was introduced with:

      commit 931c1c26983b4f84e33b78579fc8d57e4a14c6b4
      Author: Imre Deak <<a href="mailto:imre.deak@intel.com">imre.deak@intel.com</a>>
      Date:   Tue Feb 11 17:12:51 2014 +0200

        drm/i915: sdvo: add i2c sysfs symlink to the connector's directory

        This is the same what we do for DP connectors, so make things more
        consistent.

    Signed-off-by: Egbert Eich <<a href="mailto:eich@suse.de">eich@suse.de</a>>
    Reviewed-by: Imre Deak <<a href="mailto:imre.deak@intel.com">imre.deak@intel.com</a>>
    Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
    Signed-off-by: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>


 *Bug detailed description:
-----------------------------
Some subcases of igt/gem_exec_parse below fails
igt/gem_exec_parse/basic-rejected
igt/gem_exec_parse/batch-without-end
igt/gem_exec_parse/bitmasks
igt/gem_exec_parse/oacontrol-tracking
igt/gem_exec_parse/registers


Output:
 ./gem_exec_parse --run-subtest registers
IGT-Version: 1.6-g7935bbd (x86_64) (Linux:
3.15.0-rc3_drm-intel-next-queued_1cf0ba_20140508+ x86_64)
Test assertion failure function exec_batch, file gem_exec_parse.c:134:
Last errno: 0, Success
Failed assertion: expected_ret == 0
Subtest registers: FAIL

The result on -fixes was skipped:
./gem_exec_parse --run-subtest registers
IGT-Version: 1.6-g7935bbd (x86_64) (Linux:
3.15.0-rc3_drm-intel-fixes_e4c610_20140508+ x86_64)
Test requirement not met in function __real_main210, file gem_exec_parse.c:222:
Last errno: 22, Invalid argument
Test requirement: (!(!rc && parser_version > 0))
Subtest registers: SKIP


 *Reproduce steps:
---------------------------- 
1. ./gem_exec_parse --run-subtest registers</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are on the CC list for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>