Bug 107219 - [BAT] igt@drv_selftest@mock_gtt - fail - no logs
Summary: [BAT] igt@drv_selftest@mock_gtt - fail - no logs
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-13 11:49 UTC by Martin Peres
Modified: 2018-07-23 15:09 UTC (History)
1 user (show)

See Also:
i915 platform: BDW, SKL
i915 features:


Attachments

Comment 1 Chris Wilson 2018-07-13 11:52:44 UTC
Those gvt machines ran out of memory. A brief inspection suggested that gvt was allocating every page and not just the range...

commit ebfa7944d6d951c77dca6911a252917f6cecaab3
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Jul 10 09:04:24 2018 +0100

    drm/i915/selftests: Constrain mock_gtt tests to fit within RAM
    
    Be pessimistic and presume that we actually allocate every page we
    exercise via the mock_gtt (e.g. for gvt). In which case we have to keep
    our working set under the available physical memory to prevent oom.
    
    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/20180710080424.7821-1-chris@chris-wilson.co.uk
Comment 2 Dhinakaran Pandiyan 2018-07-21 00:25:21 UTC
Test has been passing since CI_DRM_4463 at least (https://intel-gfx-ci.01.org/tree/drm-tip/igt@drv_selftest@mock_gtt.html)

Martin, close this too?
Comment 3 Martin Peres 2018-07-23 15:09:08 UTC
(In reply to Dhinakaran Pandiyan from comment #2)
> Test has been passing since CI_DRM_4463 at least
> (https://intel-gfx-ci.01.org/tree/drm-tip/igt@drv_selftest@mock_gtt.html)
> 
> Martin, close this too?

Indeed, this looks good!


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.