Bug 108327 - [snb] random gpu hang in Xorg
Summary: [snb] random gpu hang in Xorg
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: 2018-10-11 12:26 UTC by komqinxit
Modified: 2019-09-25 19:14 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
GPU crash dump saved to /sys/class/drm/card0/error (61.22 KB, text/plain)
2018-10-11 12:26 UTC, komqinxit
Details

Note You need to log in before you can comment on or make changes to this bug.
Description komqinxit 2018-10-11 12:26:32 UTC
Created attachment 141993 [details]
GPU crash dump saved to /sys/class/drm/card0/error

system: ARCH Linux
cpu: Intel(R) Celeron(R) CPU G530 @ 2.40GHz

dmesg part

[ 1957.412477] [drm] GPU HANG: ecode 6:0:0x86fffffd, in Xorg [566], reason: hang on rcs0, action: reset
[ 1957.412480] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1957.412480] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1957.412481] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1957.412482] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1957.412482] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1957.412522] i915 0000:00:02.0: Resetting chip for hang on rcs0
Comment 1 GitLab Migration User 2019-09-25 19:14:15 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/1763.


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.