Bug 99864 - GPU HANG: ecode 6:0:0x85fffffc, in Xorg [1689], reason: Hang on render ring, action: reset
Summary: GPU HANG: ecode 6:0:0x85fffffc, in Xorg [1689], reason: Hang on render ring, ...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-19 19:50 UTC by Markus Witt
Modified: 2019-09-25 19:00 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (898.18 KB, text/plain)
2017-02-19 19:50 UTC, Markus Witt
Details

Description Markus Witt 2017-02-19 19:50:37 UTC
Created attachment 129747 [details]
/sys/class/drm/card0/error

[28062.700836] [drm] GPU HANG: ecode 6:0:0x85fffffc, in Xorg [1689], reason: Hang on render ring, action: reset
[28062.700841] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[28062.700842] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[28062.700843] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[28062.700843] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[28062.700844] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[28062.700887] drm/i915: Resetting chip after gpu hang

I was viewing a video stream using mpv when my system hung and wasn't responsive for a few seconds.
Please notify me if you need further information - I suppose the error file contains everything you'd need.
Comment 1 Elizabeth 2018-03-21 21:09:12 UTC
Hello Markus, is this still reproducible with latest kernel and mesa versions? Thank you.
Comment 2 GitLab Migration User 2019-09-25 19:00: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/mesa/mesa/issues/1571.


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.