Bug 111115

Summary:	[CI][BAT] igt@i915_selftest@live_execlists - dmesg-warn - Failed to idle engines, declaring wedged!
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	RESOLVED INVALID	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	highest	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:		i915 features:	GEM/Other

Description Martin Peres 2019-07-12 08:56:07 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5094/fi-bwr-2160/igt@i915_selftest@live_execlists.html

<6> [314.397019] [drm] RC6 disabled, disabling runtime PM support
<3> [314.609198] i915 0000:00:02.0: Failed to idle engines, declaring wedged!

Comment 1 CI Bug Log 2019-07-12 09:02:37 UTC

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

### New filters associated

* BWR: igt@i915_selftest@live_hangcheck - dmesg-fail - igt_reset_wait failed with error -5
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3231/fi-bwr-2160/igt@i915_selftest@live_hangcheck.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5094/fi-bwr-2160/igt@i915_selftest@live_hangcheck.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6461/fi-bwr-2160/igt@i915_selftest@live_hangcheck.html

* BWR: igt@i915_selftest@live_execlists - dmesg-warn - Failed to idle engines, declaring wedged!
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3231/fi-bwr-2160/igt@i915_selftest@live_execlists.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5094/fi-bwr-2160/igt@i915_selftest@live_execlists.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6461/fi-bwr-2160/igt@i915_selftest@live_execlists.html

Comment 2 Chris Wilson 2019-07-12 09:11:49 UTC

The GPU died in the previous test with a nice big failure message. That's the one that needs reporting :)

Comment 3 Chris Wilson 2019-07-12 10:13:36 UTC

It was already dead.

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.