[Bug 107254] [BAT] igt at drv_selftest@mock_hugepages - dmesg-fail - Failed assertion: err == 0
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jul 17 09:30:18 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=107254
Chris Wilson <chris at chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Chris Wilson <chris at chris-wilson.co.uk> ---
If my guess is correct that this is self-inflicted (as opposed to external
fragmentation), this should be prevented by:
commit d778847208c016f66a44d4c40baa74ca3bf724fd (HEAD -> drm-intel-next-queued,
drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Tue Jul 17 09:23:34 2018 +0100
drm/i915/selftests: Free the backing store between iterations
In the huge pages tests, we may have lots of objects being trapped on
the freelist as we hold the struct_mutex allowing the free worker no
opportunity to recover the backing store. We also have stricter
requirements and the desire for large contiguous pages, further
increasing the allocation pressure. To reduce the chance of running out
of memory, we could either drop the mutex and flush the free worker, or
we could release the backing store directly. We do the latter in this
patch for simplicity.
References: https://bugs.freedesktop.org/show_bug.cgi?id=107254
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Matthew Auld <matthew.william.auld at gmail.com>
Reviewed-by: Matthew Auld <matthew.william.auld at gmail.com>
Link:
https://patchwork.freedesktop.org/patch/msgid/20180717082334.18774-1-chris@chris-wilson.co.uk
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180717/418d5000/attachment.html>
More information about the intel-gfx-bugs
mailing list