Bug 109101 - [snb] GPU HANG: ecode 6:0:0x85fffffc in bomberman
Summary: [snb] GPU HANG: ecode 6:0:0x85fffffc in bomberman
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
Whiteboard: Triaged
Depends on:
Reported: 2018-12-19 13:14 UTC by jimmublasko
Modified: 2019-09-25 19:15 UTC (History)
1 user (show)

See Also:
i915 platform: SNB
i915 features: GPU hang

/sys/class/drm/card0/error (30.47 KB, text/plain)
2018-12-19 13:14 UTC, jimmublasko

Description jimmublasko 2018-12-19 13:14:05 UTC
Created attachment 142854 [details]

[20299.560221] [drm] GPU HANG: ecode 6:0:0x85fffffc, in bomberman [2219], reason: hang on rcs0, action: reset
[20299.560223] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[20299.560223] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[20299.560224] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[20299.560224] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[20299.560225] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Comment 1 Lakshmi 2018-12-20 06:26:06 UTC
Reporter, can you say what was the use case here or any particular pattern where GPU hangs? How often it occurs?

Can you also attach full dmesg with set kernel parameters drm.debug=0x1e log_buf_len=4M?
Comment 2 GitLab Migration User 2019-09-25 19:15:27 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/1776.

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.