Bug 112164

Summary: [CI][RESUME] igt@gem_unfence_active_buffers - fail - Failed assertion: (drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
i915 platform: TGL i915 features: GEM/Other

Description Lakshmi 2019-10-29 09:02:32 UTC
gem_unfence_active_buffers:975) intel_batchbuffer-CRITICAL: Test assertion failure function intel_batchbuffer_flush_on_ring, file ../lib/intel_batchbuffer.c:239:
(gem_unfence_active_buffers:975) intel_batchbuffer-CRITICAL: Failed assertion: (drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0
(gem_unfence_active_buffers:975) intel_batchbuffer-CRITICAL: Last errno: 5, Input/output error
Test gem_unfence_active_buffers failed.
Comment 1 CI Bug Log 2019-10-29 09:03:23 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@gem_unfence_active_buffers - fail - Failed assertion: (drm_intel_gem_bo_context_exec(batch-&gt;bo, ctx, used, ring)) == 0
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7197/re-tgl-y/igt@gem_unfence_active_buffers.html
Comment 2 Chris Wilson 2019-10-29 09:05:39 UTC
It's complaining about being too slow. Sorting out rps would probably help, investigating why this test is not responsive enough would also be sensible.
Comment 3 Martin Peres 2019-11-29 19:44:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/557.

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.