[Bug 110848] Everything using GPU gets stuck after running+killing parallel Media loads (after running 3D benchmarks)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jul 10 13:48:14 UTC 2019


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

--- Comment #17 from Eero Tamminen <eero.t.tamminen at intel.com> ---
So far the smallest set of tests with which I've managed to reproduce the
freeze is this set of tests (in this order):
* running 3x 33 Synmark tests in fullscreen
* running 5x 3 GLBenchmark windowed tests, all both onscreen & offscreen
* running 3x 10 GpuTest windowed & fullscreen tests
* running 3x 5 different FFmpeg VAAPI transcode operations, alternating
multiple processes (parallel process count being from 5 to 50) and single
transcode process
* at end doing process group kill for the 50 parallel processes case before
next single transcode process

However, that freeze wasn't reproducible on next boot.

>From earlier data, it seems that running with this amount of 3D tests before
media tests results in approximately 1/2 reproducibility, and 2x larger set of
3D tests before the Media tests, makes it nearly fully reproducible (not sure
whether use of MediaSDK made it also more reproducible, as I hadn't tried plain
VAAPI backend before).

I haven't been able to trigger the media freeze by using just fullscreen 3D
applications, so I assume some parallel 3D engine usage is needed (X or Weston
compositing in addition to 3D benchmark itself) before parallel media engine
usage.  But running just the (above) windowed 3D benchmarks before media tests
hasn't yet been enough to trigger the freeze either.

=> I think i915 would need some specific IGT tests that:
* access i915 from multiple processes in parallel
* do that for each supported engine in turn, and then all of them at same time
* some of those processes are in separate process group and get killed as a
group during testing, and tester just forks more of them as replacement
* is run under lockdep

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190710/6d4bac6b/attachment.html>


More information about the intel-gfx-bugs mailing list