<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@gem_ppgtt@blt-vs-render-ctxn - dmesg-warn - swap is full" href="https://bugs.freedesktop.org/show_bug.cgi?id=109801#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@gem_ppgtt@blt-vs-render-ctxn - dmesg-warn - swap is full" href="https://bugs.freedesktop.org/show_bug.cgi?id=109801">bug 109801</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>So fingers crossed this is just bad resource estimation and not a true leak: commit 4e7296aa879350b10a216b88fa7f44d919765765 (HEAD, upstream/master) Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Thu Feb 28 15:30:43 2019 +0000 i915/gem_ppgtt: Estimate resource usage and bail if it means swapping! fi-kbl-guc's swap ran dry while running blt-vs-render-ctxN, which is mildly concerning but conceivable as we never checked there was enough memory to run the test to begin with. Each child needs to keep its own surface and possible a pair of logical contexts (one for rcs and one for bcs) so check that there is enough memory to allow all children to co-exist. During execution, we require another surface and batch, but these are temporary and so should fit fine with a small amount of thrashing on the boundary. References: <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@gem_ppgtt@blt-vs-render-ctxn - dmesg-warn - swap is full" href="show_bug.cgi?id=109801">https://bugs.freedesktop.org/show_bug.cgi?id=109801</a> Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Reviewed-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>></pre> </div> <hr> You are receiving this mail because: <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>