<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@gem_ppgtt@blt-vs-render-ctx[0n] - dmesg-warn/dmesg-fail/incomplete - swap is full"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109801#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@gem_ppgtt@blt-vs-render-ctx[0n] - dmesg-warn/dmesg-fail/incomplete - swap is full"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109801">bug 109801</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to Francesco Balestrieri from <a href="show_bug.cgi?id=109801#c12">comment #12</a>)
<span class="quote">> Chris,
>
> > I suppose if I dump meminfo/slabinfo before the test begins, we should then be able
> > to compare with the allocation failure to see if the shmem usage is solely due to the > test.
>
> Should we do just that? It seems to be reproducible fairly easily.</span >
The CI kernel is missing the slabinfo dump on oom -- not sure which config flag
that we are missing, I see it on my oomkiller but CI does not. Without that, we
don't have much indication of what changed inside the test -- you may as well
just log in remotely and look at slabinfo / i915_gem_objects and decide where
to go from there.
Why, oh why, does this appear to be icl specific?!!!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>