| Summary: | [CI] igt@drv_selftest@live_gtt - dmesg-fail - drv_selftest invoked oom-killer | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | BXT | i915 features: | GEM/Other |
|
Description
Martin Peres
2018-05-22 07:35:08 UTC
Suppression applied, commit 1abb70f5955d1a9021f96359a2c6502ca569b68d Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue May 22 09:36:43 2018 +0100 drm/i915/gtt: Allow pagedirectory allocations to fail As we handle the allocation failure of the page directory and tables by propagating the failure back to userspace, allow it to fail if direct reclaim is unable to satisfy the request (i.e. disable the oomkiller). The premise being that if we are unable to allocate a single page for the pagetable, we will not be able to handle the multitude of pages required for the gfx operation and we should back off to allow the system to recover. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106609 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Matthew Auld <matthew.william.auld@gmail.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Reviewed-by: Matthew Auld <matthew.william.auld@gmail.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180522083643.29601-1-chris@chris-wilson.co.uk (In reply to Chris Wilson from comment #1) > Suppression applied, > > commit 1abb70f5955d1a9021f96359a2c6502ca569b68d > Author: Chris Wilson <chris@chris-wilson.co.uk> > Date: Tue May 22 09:36:43 2018 +0100 > > drm/i915/gtt: Allow pagedirectory allocations to fail > > As we handle the allocation failure of the page directory and tables by > propagating the failure back to userspace, allow it to fail if direct > reclaim is unable to satisfy the request (i.e. disable the oomkiller). > The premise being that if we are unable to allocate a single page for > the pagetable, we will not be able to handle the multitude of pages > required for the gfx operation and we should back off to allow the > system to recover. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106609 > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Matthew Auld <matthew.william.auld@gmail.com> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> > Reviewed-by: Matthew Auld <matthew.william.auld@gmail.com> > Link: > https://patchwork.freedesktop.org/patch/msgid/20180522083643.29601-1- > chris@chris-wilson.co.uk I'll trust you on that! Note that the oom still exists; just the oomkiller shouldn't be triggered directly by our code ;) #105347 is a good dumping ground for the oom by java or avahi-daemon etc that unfortunately try to run concurrently to the test that is eating all the memory. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.