[Bug 110255] [CI][SHARDS] igt at gem_exec_nop@basic-sequential - incomplete - No logs

[bugzilla-daemon at freedesktop.org]

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

--- Comment #5 from Francesco Balestrieri <francesco.balestrieri at intel.com> ---
I may be totally mistaken here, but I can see that for every occurrence, in the
same run, OOM is reported due to gem_exec_big. Is it possible that this is
causing the incomplete on this test? If that's the case, the disappearance of
the issue would be explained by this patch:

https://lists.freedesktop.org/archives/igt-dev/2019-March/011173.html

[PATCH i-g-t] i915/gem_exec_big: 128MiB not enough slack? Let out the rope!

Even with 128MiB reserved for other use, a single pass of gem_exec_big
runs out of memory. Give in and halve our batch size, that has to be
enough slack! As to why it keeps on failing, is left as an exercise to
the reader -- we have to solve the mm/ mystery one day, as eventually it
will be our only remaining source of bugs!

Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin at linux.intel.com>
---
 tests/i915/gem_exec_big.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/i915/gem_exec_big.c b/tests/i915/gem_exec_big.c
index 015f59e29..440136ee8 100644
--- a/tests/i915/gem_exec_big.c
+++ b/tests/i915/gem_exec_big.c
@@ -260,7 +260,7 @@ static void single(int i915)
        uint32_t handle;
        void *ptr;

-       batch_size = (intel_get_avail_ram_mb() - 128) << 20; /* CI slack */
+       batch_size = (intel_get_avail_ram_mb() / 2) << 20; /* XXX CI slack? */
        limit = gem_aperture_size(i915) - (256 << 10); /* low pages reserved */
        if (!gem_uses_full_ppgtt(i915))
                limit = 3 * limit / 4;
-- 
2.20.1

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