Bug 109510

Summary: [skl] GPU HANG: ecode 9:0:0x86dffffd, in Xorg
Product: Mesa Reporter: single34
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED MOVED QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
i915 platform: i915 features:
Attachments: This is /sys/class/drm/card0/error

Description single34 2019-01-31 01:15:11 UTC
Created attachment 143258 [details]
This is /sys/class/drm/card0/error

I was using Xilinx ISE 10.1 SP3 (x86_64) on my Arch Linux machine. I was drawing a wire while the user interface suddenly froze. I tried switching tabs (I'm using i3 as windows manager) but nothing happened. Then after a few seconds everything is back to normal. I checked the kernel log by typing dmesg, and discovered the following message. I thought it might be good to file a bug report. 

[24917.579505] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [669], reason: hang on rcs0, action: reset
[24917.579506] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[24917.579507] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[24917.579507] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[24917.579508] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[24917.579508] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Comment 1 GitLab Migration User 2019-09-25 20:29:26 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/1784.

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.