[Bug 80208] [ILK/SNB/IVB/HSW/BDW]igt/gem_userptr_blits unable to exit

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jun 23 20:45:49 PDT 2014


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

--- Comment #2 from Guo Jinxian <jinxianx.guo at intel.com> ---
The test still unable to exit on IVB on latest -fixes.

Output:
[root at x-ivb6 tests]# time ./gem_userptr_blits --run-subtest
forked-sync-swapping-multifd-mempressure-interruptible
IGT-Version: 1.7-gfedb9b6 (x86_64) (Linux:
3.15.0-rc8_drm-intel-fixes_4a11e3_20140623_debug+ x86_64)
Aperture size is 2048 MiB
Total RAM is 7873 MiB
Testing unsynchronized mappings...
Testing synchronized mappings...
child 0 died with signal 9, Killed
Subtest forked-sync-swapping-multifd-mempressure-interruptible: FAIL
Test assertion failure function igt_stop_helper, file igt_core.c:818:
Last errno: 0, Success
Failed assertion: WIFSIGNALED(status) && WTERMSIG(status) == (proc->use_SIGKILL
? SIGKILL : SIGQUIT)
gem_userptr_blits: igt_core.c:753: fork_helper_exit_handler: Assertion `ret ==
0' failed.
Test assertion failure function igt_stop_helper, file igt_core.c:818:
Last errno: 0, Success
Failed assertion: WIFSIGNALED(status) && WTERMSIG(status) == (proc->use_SIGKILL
? SIGKILL : SIGQUIT)
gem_userptr_blits: igt_core.c:753: fork_helper_exit_handler: Assertion `ret ==
0' failed.
Test assertion failure function igt_stop_helper, file igt_core.c:818:
Last errno: 0, Success
Failed assertion: WIFSIGNALED(status) && WTERMSIG(status) == (proc->use_SIGKILL
? SIGKILL : SIGQUIT)
gem_userptr_blits: igt_core.c:753: fork_helper_exit_handler: Assertion `ret ==
0' failed.

^Cgem_userptr_blits: igt_core.c:859: children_exit_handler: Assertion `ret ==
0' failed.
Aborted (core dumped)

real    12m53.437s
user    0m0.058s
sys     0m2.270s

-- 
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/20140624/0eb02e35/attachment.html>


More information about the intel-gfx-bugs mailing list