<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Everything using GPU gets stuck after running+killing parallel Media loads (after running 3D benchmarks)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110848#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Everything using GPU gets stuck after running+killing parallel Media loads (after running 3D benchmarks)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110848">bug 110848</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=110848#c17">comment #17</a>)
<span class="quote">> So far the smallest set of tests with which I've managed to reproduce the
> freeze is this set of tests (in this order):</span >
[...]
I have slightly smaller test-case, with freeze reproducibility of about 1/3:
1. Start Ubuntu 18.04 with X/Unity & latest git gfx/media stack
2. Run large number of Wayland test cases which fail immediately at start
because there's no Wayland. I don't think these are relevant, but if some
of them briefly open window before exiting, it does exercise i915
3. Run 3x 7 (very heavy / low FPS) windowed GPU bandwidth tests
4. Run 3x 8 different FFmpeg QSV (=using MediaSDK) transcode operations,
alternating betwee multiple processes (parallel process count being from
5 to 50) and single transcode process versions of them
5. Run same things as in 4), but using MediaSDK (transcode sample app) directly
In some of these 1/3 freeze occurrences, freezing happens in step 3), sometimes
in step 4).
After Media freeze, reboot seems stuck at shutdown, device needs to be
power-cycled.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>