Bug 107118 - [kbl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
Summary: [kbl] GPU HANG: ecode 9:0:0x85dffffb, 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-07-05 07:25 UTC by shaleen.jain95
Modified: 2019-09-25 19:12 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features:


Attachments
/sys/class/drm/card0/error (51.76 KB, text/plain)
2018-07-05 07:25 UTC, shaleen.jain95
Details

Description shaleen.jain95 2018-07-05 07:25:50 UTC
Created attachment 140470 [details]
/sys/class/drm/card0/error
Comment 1 shaleen.jain95 2018-07-05 07:39:50 UTC
$ uname -m
x86_64

$ uname -r
4.17.2-1-ARCH

Linux distribution: Arch Linux
Mesa:  18.1.3-1

dmesg:
[555412.082471] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [4360], reason: Hang on rcs0, action: reset
[555412.082473] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[555412.082473] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[555412.082474] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[555412.082474] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[555412.082475] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[555412.082486] i915 0000:00:02.0: Resetting rcs0 after gpu hang
Comment 2 GitLab Migration User 2019-09-25 19:12:05 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/1736.


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.