Bug 103745 - [snb] GPU HANG: ecode 6:0:0x85fffffc, in Xwayland
Summary: [snb] GPU HANG: ecode 6:0:0x85fffffc, in Xwayland
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2017-11-14 19:23 UTC by Alexandre
Modified: 2019-09-25 19:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

gpu crash dump (46.63 KB, text/plain)
2017-11-14 19:23 UTC, Alexandre

Description Alexandre 2017-11-14 19:23:36 UTC
Created attachment 135474 [details]
gpu crash dump

Ubuntu 17.10 with it's stock kernel 4.13.0-16-generic

klog reports:

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

I'll attach the dumps.
Comment 1 Elizabeth 2017-12-04 23:29:51 UTC
Hello Alexandre, is this reproducible? What Mesa version do you have? Any steps that trigger this issue?? Thank you.
Comment 2 GitLab Migration User 2019-09-25 19:05:44 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/1652.

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.