[Bug 89633] New: [BSW]igt/gem_exec_nop/render causes [drm:i915_context_is_banned [i915]] *ERROR* gpu hanging too fast, banning!

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 89633
           Summary: [BSW]igt/gem_exec_nop/render causes
                    [drm:i915_context_is_banned [i915]] *ERROR* gpu
                    hanging too fast, banning!
           Product: DRI
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: huax.lu at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 114423
  --> https://bugs.freedesktop.org/attachment.cgi?id=114423&action=edit
dmesg

==System Environment==
--------------------------
Regression: not sure, it has bug 88845

no-working platforms: BSW

==kernel==
--------------------------
drm-intel-nightly/3753ea527e539d3358a6368e77cb29ecb2e71c42
commit 3753ea527e539d3358a6368e77cb29ecb2e71c42
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date:   Tue Mar 17 22:36:04 2015 +0100

    drm-intel-nightly: 2015y-03m-17d-21h-35m-20s UTC integration manifest

==Bug detailed description==
-----------------------------
It happens on drm-intel-nightly kernel, works well on drm-intel-next-queued
kernel.

output:
IGT-Version: 1.10-g505645c (x86_64) (Linux:
4.0.0-rc4_drm-intel-nightly_3753ea_20150318+ x86_64)
Time to exec x 1:               487.000µs (ring=render)
Time to exec x 2:                65.500µs (ring=render)
Time to exec x 4:                28.000µs (ring=render)
Time to exec x 8:                19.125µs (ring=render)
Time to exec x 16:               12.750µs (ring=render)
Time to exec x 32:               10.688µs (ring=render)
Time to exec x 64:                7.156µs (ring=render)
Time to exec x 128:               6.453µs (ring=render)
Time to exec x 256:               5.773µs (ring=render)
Time to exec x 512:               5.232µs (ring=render)
Time to exec x 1024:              5.241µs (ring=render)
Time to exec x 2048:              5.426µs (ring=render)
Time to exec x 4096:              4.485µs (ring=render)
Time to exec x 8192:              4.476µs (ring=render)
Time to exec x 16384:             5.002µs (ring=render)
Test assertion failure function loop, file gem_exec_nop.c:100:
Failed assertion: exec(fd, handle, count, ring_id) == 0
error: -1 != 0
Subtest render failed.
**** DEBUG ****
Time to exec x 1:               487.000µs (ring=render)
Time to exec x 2:                65.500µs (ring=render)
Time to exec x 4:                28.000µs (ring=render)
Time to exec x 8:                19.125µs (ring=render)
Time to exec x 16:               12.750µs (ring=render)
Time to exec x 32:               10.688µs (ring=render)
Time to exec x 64:                7.156µs (ring=render)
Time to exec x 128:               6.453µs (ring=render)
Time to exec x 256:               5.773µs (ring=render)
Time to exec x 512:               5.232µs (ring=render)
Time to exec x 1024:              5.241µs (ring=render)
Time to exec x 2048:              5.426µs (ring=render)
Time to exec x 4096:              4.485µs (ring=render)
Time to exec x 8192:              4.476µs (ring=render)
Time to exec x 16384:             5.002µs (ring=render)
Test assertion failure function loop, file gem_exec_nop.c:100:
Failed assertion: exec(fd, handle, count, ring_id) == 0
error: -1 != 0
****  END  ****
Subtest render: FAIL (12.488s)

==Reproduce steps==
---------------------------- 
1.  ./gem_exec_nop --run-subtest render

-- 
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: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150318/e310bc88/attachment.html>