[Bug 81638] [BYT]igt/gem_concurrent_blit some subcases unable to exit sporadically

[bugzilla-daemon at freedesktop.org]

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

Guo Jinxian <jinxianx.guo at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED

--- Comment #2 from Guo Jinxian <jinxianx.guo at intel.com> ---
(In reply to comment #1)
> Try with
> 
> commit 4f7d4dcae56e5f993f3f0b331556d4df3b0b33ab
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date:   Mon Jul 21 07:54:29 2014 +0100
> 
>     Use SIGTERM in replace of SIGQUIT
>     
>     SIGTERM is the normal signal to use when instructing a process to exit.
>     The only difference is that an unhandled SIGQUIT is meant to generate a
>     coredump, which is not what we want, but in practice I encountered an
>     issue where SIGTERM seemed to be deliverable more reliably than SIGQUIT
>     (in tests using multiple signal helpers).
>     
>     Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>

I tried 10 times with latest igt(70e6ed92abbca575f03f5a28402ef1eb9a6b97b8),
didn't find this issue.

root at x-bytm02:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time
./gem_concurrent_blit --run-subtest cpu-early-read-forked
IGT-Version: 1.7-g70e6ed9 (x86_64) (Linux:
3.16.0-rc6_drm-intel-nightly_d62845_20140723+ x86_64)
using 2x512 buffers, each 1MiB
Subtest cpu-early-read-forked: SUCCESS

real    0m5.487s
user    0m10.724s
sys     0m9.445s

-- 
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/20140723/7623b22c/attachment.html>