Bug 109484 - [CI][SHARDS] igt@i915_selftest@live_hangcheck - dmesg-fail - igt_reset_evict_ggtt failed with error -5
Summary: [CI][SHARDS] igt@i915_selftest@live_hangcheck - dmesg-fail - igt_reset_evict_...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: sandeep
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-28 14:38 UTC by Martin Peres
Modified: 2019-07-31 11:46 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-01-28 14:38:40 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5482/shard-skl8/igt@i915_selftest@live_hangcheck.html

<3> [425.281494] i915/intel_hangcheck_live_selftests: igt_reset_evict_ggtt failed with error -5
Comment 1 CI Bug Log 2019-01-28 14:39:54 UTC
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
Comment 2 Chris Wilson 2019-01-28 14:48:47 UTC
It's complaining that it didn't block on eviction... Quite possibly it found some space and didn't have to evict.
Comment 3 Francesco Balestrieri 2019-02-06 08:00:13 UTC
Seen once so far (179 runs ago)
Comment 4 sandeep 2019-02-14 03:32:23 UTC
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.
Comment 5 sandeep 2019-02-14 18:28:42 UTC
(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;
}
Comment 6 Francesco Balestrieri 2019-03-01 12:02:37 UTC
Still no other occurrence in 548 runs. Resolving.
Comment 7 Lakshmi 2019-07-31 11:45:55 UTC
Happened only once CI_DRM_5482_full (6 months old) Closing this issue as WORKSFORME.
Comment 8 CI Bug Log 2019-07-31 11:46:10 UTC
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.


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.