<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BXT/APL] Everything using GPU gets stuck after running parallel Media loads after 3D benchmarks"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110848#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BXT/APL] Everything using GPU gets stuck after running parallel Media loads after 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 Chris Wilson from <a href="show_bug.cgi?id=110848#c1">comment #1</a>)
<span class="quote">> What's the latest tip tested?</span >
Yesterday evening:
2019-06-05 16:28:24 7a984cf096: drm-tip: 2019y-06m-05d-16h-27m-26s UTC
integration manifest
(In reply to Eero Tamminen from <a href="show_bug.cgi?id=110848#c0">comment #0</a>)
<span class="quote">> 50 ffmpeg instances can use a bit of GEM objects (and FFmpeg QSV uses more
> of them than MediaSDK alone, or FFmpeg VAAPI)</span >
About this much (in total 2GB which shouldn't be a problem):
------------------------------------------
12769 shrinkable objects, 2378752000 bytes
491 unbound objects, 29552640 bytes
12277 bound objects, 2349133824 bytes
51 purgeable objects, 10121216 bytes
220 mapped objects, 11239424 bytes
2220 huge-paged objects (2M, 64K, 4K) 2080702464 bytes
12 display objects (globally pinned), 8851456 bytes
4294967296 [0x0000000010000000] gtt total
Supported page sizes: 2M, 64K, 4K
------------------------------------------
On each round the max number of huge-paged objects seems to grow, although it
drops back to same number after tests have finished.</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>