Bug 102422

Summary:	[drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [389], reason: Hang on rcs, action: reset
Product:	Mesa	Reporter:	Anthony L. Eden <anthony.louis.eden>
Component:	Drivers/DRI/i965	Assignee:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Status:	RESOLVED MOVED	QA Contact:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity:	major
Priority:	medium	CC:	anthony.louis.eden, intel-gfx-bugs, rtentser
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	/sys/class/drm/card0/error

Description Anthony L. Eden 2017-08-25 21:26:19 UTC

[13486.150685] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [389], reason: Hang on rcs, action: reset
[13486.150686] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[13486.150687] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[13486.150687] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[13486.150687] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[13486.150688] [drm] GPU crash dump saved to /sys/class/drm/card0/error

Kernel version: 4.12.8-2-ARCH

Comment 1 Anthony L. Eden 2017-08-25 21:27:25 UTC

Created attachment 133803 [details]
/sys/class/drm/card0/error

/sys/class/drm/card0/error

Comment 2 Elizabeth 2018-03-06 21:10:17 UTC

Hi, is this still reproducible? Which mesa version are you using? Is it possible that you upgrade at least to kernel version 4.13 to get more debug information in the log? Thank you.

Comment 3 GitLab Migration User 2019-09-25 19:03:43 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/mesa/mesa/issues/1620.

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.