[Bug 78247] [BDW]igt/gem_concurrent_blit unable to exit sporadically

[bugzilla-daemon at freedesktop.org]

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

--- Comment #5 from Guo Jinxian <jinxianx.guo at intel.com> ---
Created attachment 99472
  --> https://bugs.freedesktop.org/attachment.cgi?id=99472&action=edit
dmesg

The test is able to finish on latest
-nightly(36765340cb068dec1216342bfcdbf2678ec29860).
time ./gem_concurrent_blit
IGT-Version: 1.6-g737d248 (x86_64) (Linux:
3.15.0-rc5_drm-intel-nightly_367653_20140521+ x86_64)
using 2x512 buffers, each 1MiB
Subtest prw-overwrite-source: SUCCESS
Subtest prw-early-read: SUCCESS
Subtest prw-gpu-read-after-write: SUCCESS
Subtest prw-overwrite-source-interruptible: SUCCESS
Subtest prw-early-read-interruptible: SUCCESS
Subtest prw-gpu-read-after-write-interruptible: SUCCESS
Subtest prw-overwrite-source-forked: SUCCESS
Subtest prw-early-read-forked: SUCCESS
Subtest prw-gpu-read-after-write-forked: SUCCESS
Subtest cpu-overwrite-source: SUCCESS
Subtest cpu-early-read: SUCCESS
Subtest cpu-gpu-read-after-write: SUCCESS
Subtest cpu-overwrite-source-interruptible: SUCCESS
Subtest cpu-early-read-interruptible: SUCCESS
Subtest cpu-gpu-read-after-write-interruptible: SUCCESS
Subtest cpu-overwrite-source-forked: SUCCESS
Subtest cpu-early-read-forked: SUCCESS
Subtest cpu-gpu-read-after-write-forked: SUCCESS
Subtest gtt-overwrite-source: SUCCESS
Subtest gtt-early-read: SUCCESS
Subtest gtt-gpu-read-after-write: SUCCESS
Subtest gtt-overwrite-source-interruptible: SUCCESS
Subtest gtt-early-read-interruptible: SUCCESS
Subtest gtt-gpu-read-after-write-interruptible: SUCCESS
Subtest gtt-overwrite-source-forked: SUCCESS
Subtest gtt-early-read-forked: SUCCESS
Subtest gtt-gpu-read-after-write-forked: SUCCESS

real    17m14.136s
user    26m8.028s
sys     1m22.114s

-- 
You are receiving this mail because:
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: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140521/e53ac2c2/attachment.html>