[Bug 85312] New: [SNB]igt/kms_flip/nonblocking-read unable exit

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 85312
           Summary: [SNB]igt/kms_flip/nonblocking-read unable exit
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: jinxianx.guo at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

==System Environment==
--------------------------
Regression: Not sure.
Unable to find good commit on both igt and kernel

Non-working platforms: SNB

==kernel==
--------------------------
origin/drm-intel-nightly: 1e61c930ec1745ec3cfc77be1cdd023c409de26d(fails)
    drm-intel-nightly: 2014y-10m-21d-17h-46m-36s UTC integration manifest
origin/drm-intel-next-queued: f3b190654cbceb0788bfc3b67e4f38ad870dfb84(fails)
    drm/i915: add runtime PM get/put call in i915_execlists
origin/drm-intel-fixes: f114040e3ea6e07372334ade75d1ee0775c355e1(fails)
    Linux 3.18-rc1

==Bug detailed description==
igt/kms_flip/nonblocking-read unable exit


Output:
"[root at x-sgb3 tests]# time ./kms_flip --run-subtest nonblocking-read
IGT-Version: 1.8-gbba1cd0 (x86_64) (Linux:
3.18.0-rc1_drm-intel-fixes_f11404_20141022+ x86_64)
Using monotonic timestamps

^C
real    18m22.330s
user    0m0.002s
sys     0m0.007s
"


==Reproduce steps==
---------------------------- 
1. ./kms_flip --run-subtest nonblocking-read

-- 
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/20141022/2073308f/attachment.html>