Bug 111927 - [CI][DRMTIP] igt@gem_exec_parse@basic-allocation - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0
Summary: [CI][DRMTIP] igt@gem_exec_parse@basic-allocation - fail - Failed assertion: _...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: low normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2019-10-08 16:52 UTC by Lakshmi
Modified: 2019-10-10 06:04 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: GEM/Other


Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-10-08 16:52:21 UTC
Starting subtest: basic-allocation
(gem_exec_parse:1137) ioctl_wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ../lib/ioctl_wrappers.c:609:
(gem_exec_parse:1137) ioctl_wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0
(gem_exec_parse:1137) ioctl_wrappers-CRITICAL: error: -12 != 0
Subtest basic-allocation failed.
Comment 1 CI Bug Log 2019-10-08 16:52:52 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* HSW: igt@gem_exec_parse@basic-allocation - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_384/fi-hsw-peppy/igt@gem_exec_parse@basic-allocation.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_385/fi-hsw-peppy/igt@gem_exec_parse@basic-allocation.html
Comment 2 Chris Wilson 2019-10-09 11:14:05 UTC
ENOMEM, sadly not common to all HSW (and not trivially reproducible here) so I presume it's memory configuration and genuine exhaustion. The only real concern is whether we did everything we could to prevent the exhaustion and recover memory for use. For example, it did not originate from shmem_get_pages as we don't have the allocation failure trace, so one of the other kmallocs.

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.