Bug 111210

Summary:	[CI][DRMTIP] igt@gem_eio@suspend - incomplete - GPU hang
Product:	DRI	Reporter:	Lakshmi <lakshminarayana.vudum>
Component:	DRM/Intel	Assignee:	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
Whiteboard:
i915 platform:	KBL	i915 features:

Description Lakshmi 2019-07-24 15:44:30 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_333/fi-kbl-7500u/igt@gem_eio@suspend.html
<6> [184.786185] Console: switching to colour dummy device 80x25
<6> [184.786229] [IGT] gem_eio: executing
<5> [184.791196] Setting dangerous option reset - tainting kernel
<5> [184.791244] Setting dangerous option reset - tainting kernel
<6> [184.793524] i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, Manually set wedged engine mask = ffffffffffffffff

Comment 1 CI Bug Log 2019-07-24 15:47:10 UTC

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

### New filters associated

* KBL:  igt@gem_eio@suspend - incomplete - GPU hang
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_333/fi-kbl-7500u/igt@gem_eio@suspend.html

Comment 2 Chris Wilson 2019-07-24 16:51:27 UTC

Nothing there indicates our bug.

Comment 3 CI Bug Log 2019-07-25 12:36:40 UTC

A CI Bug Log filter associated to this bug has been updated:

{- KBL:  igt@gem_eio@suspend - incomplete - GPU hang -}
{+ KBL:  igt@gem_eio@suspend - incomplete - GPU hang +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_334/fi-kbl-7500u/igt@gem_eio@suspend.html

Comment 4 Martin Peres 2019-11-29 19:20:29 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/350.

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.