[Bug 111936] [ICL] (Recoverable) GPU hangs in TerrainFlyTess with Iris
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Oct 9 14:29:51 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111936
--- Comment #5 from Eero Tamminen <eero.t.tamminen at intel.com> ---
Created attachment 145684
--> https://bugs.freedesktop.org/attachment.cgi?id=145684&action=edit
TerrainFlyTess ICL error state (2019-10-09 drm-tip)
Jani extended the ICL loan.
Unfortunately neither drm.debug nor CONFIG_LOCKDEP=y shows anything:
-----------------------------------------------------------------------
[ 151.523178] [drm:intel_combo_phy_init [i915]] Combo PHY A already enabled,
won't reprogram it.
[ 151.523211] [drm:intel_combo_phy_init [i915]] Combo PHY B already enabled,
won't reprogram it.
[ 153.874368] Iteration 1/3: synmark2 OglTerrainFlyTess
[ 180.033099] Iteration 2/3: synmark2 OglTerrainFlyTess
[ 187.993335] i915 0000:00:02.0: GPU HANG: ecode 11:1:0x00000000, hang on rcs0
[ 187.993338] GPU hangs can indicate a bug anywhere in the entire gfx stack,
including userspace.
[ 187.993339] Please file a _new_ bug report on bugs.freedesktop.org against
DRI -> DRM/Intel
[ 187.993340] drm/i915 developers can then reassign to the right component if
it's not a kernel issue.
[ 187.993341] The GPU crash dump is required to analyze GPU hangs, so please
always attach it.
[ 187.993342] GPU crash dump saved to /sys/class/drm/card0/error
[ 187.993406] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 208.151967] Iteration 3/3: synmark2 OglTerrainFlyTess
-----------------------------------------------------------------------
No idea whether the worse reproducibility (1/3 instead of 1/1), is due to using
latest git kernel, or debug options. Attached is new error state.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191009/9ba49780/attachment.html>
More information about the intel-gfx-bugs
mailing list