The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@i915_selftest@live_hangcheck - dmesg-fail - igt_reset_evict_ggtt failed with error -5
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5482/shard-skl8/igt@i915_selftest@live_hangcheck.html

It's complaining that it didn't block on eviction... Quite possibly it found some space and didn't have to evict.

Seen once so far (179 runs ago)

I have tried to recreate this issue locally at my end, but I had no luck evem after running several iterations of test.

Further from CI bug log I see that it is never seen(0/242)

[CI][SHARDS] igt@i915_selftest@live_hangcheck - dmesg-fail - igt_reset_evict_ggtt failed with error -5
SKL: igt@i915_selftest@live_hangcheck - dmesg-fail - igt_reset_evict_ggtt failed with error -5 : 0 / 242 runs (0.0%)
Never seen.

We will monitor for this issue until there is an way to recreate the issue.

Please let me know if you have an easy way to reproduce the issue.

(In reply to Chris Wilson from comment #2)
> It's complaining that it didn't block on eviction... Quite possibly it found
> some space and didn't have to evict.
may be the if-check need to be updated, to reflect the thread didn't require to evict
12) if (wait_for(waitqueue_active(&rq->execute), 10)) { 
		struct drm_printer p = drm_info_printer(i915->drm.dev);

		pr_err("igt/evict_vma kthread did not wait\n");
		intel_engine_dump(rq->engine, &p, "%s\n", rq->engine->name);

		i915_gem_set_wedged(i915);
		goto out_reset;
}

Still no other occurrence in 548 runs. Resolving.

Happened only once CI_DRM_5482_full (6 months old) Closing this issue as WORKSFORME.

The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.