Summary: | [CI] igt@drv_selftest@live_gtt - incomplete | ||
---|---|---|---|
Product: | DRI | Reporter: | Tomi Sarvela <tomi.p.sarvela> |
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, martin.peres |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | BDW, CFL, KBL, SKL | i915 features: | GEM/Other |
Description
Tomi Sarvela
2018-07-05 14:10:34 UTC
At the beginning of the test on these platforms we try to create a fully populated 4G ppgtt, and then the test goes on to try and fill all of memory to see how close to a 48b gtt we can create (although it gives up on a timeout). This test is prone to oom and watchdog. I think it makes some sense to prune the worst offenders for fast-feedback (in the same way as we limit individual tests to run within a timeout rather than try and exercise the whole parameter space). Not sure on how we want to go about that though. drv_selftest --fast-feedback drv_selftest --quick ? Which then feed through to a i915 module parameter. commit 207b700050b8d323d0c23b457c200b22c7ed3737 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Jul 6 13:53:38 2018 +0100 drm/i915/selftests: Limit live_gtt allocation test to fit within RAM Limit the GTT size we try and allocate to ensure that it fits within RAM and does not trigger the oomkiller indiscriminately. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Matthew Auld <matthew.auld@intel.com> Reviewed-by: Matthew Auld <matthew.auld@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180706125338.24432-1-chris@chris-wilson.co.uk should be enough... (In reply to Chris Wilson from comment #3) > commit 207b700050b8d323d0c23b457c200b22c7ed3737 > Author: Chris Wilson <chris@chris-wilson.co.uk> > Date: Fri Jul 6 13:53:38 2018 +0100 > > drm/i915/selftests: Limit live_gtt allocation test to fit within RAM > > Limit the GTT size we try and allocate to ensure that it fits within RAM > and does not trigger the oomkiller indiscriminately. > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Matthew Auld <matthew.auld@intel.com> > Reviewed-by: Matthew Auld <matthew.auld@intel.com> > Link: > https://patchwork.freedesktop.org/patch/msgid/20180706125338.24432-1- > chris@chris-wilson.co.uk > > > should be enough... Looks good! Thanks! *** Bug 107203 has been marked as a duplicate of this bug. *** |
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.