Bug 104037 - [skl] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688], reason: Hang on rcs0, action: reset using kicad
Summary: [skl] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688], reason: Hang on rcs0, a...
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
Depends on:
Reported: 2017-12-02 13:55 UTC by philip.kiehnle
Modified: 2019-09-25 19:06 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Content of /sys/class/drm/card0/error (30.12 KB, application/x-bzip)
2017-12-02 13:55 UTC, philip.kiehnle
Content of /sys/class/drm/card0/error (30.12 KB, application/x-bzip)
2018-03-14 02:09 UTC, shane

Description philip.kiehnle 2017-12-02 13:55:18 UTC
Created attachment 135878 [details]
Content of /sys/class/drm/card0/error

When using KiCad's Pcbnew program, after a while the screen freezes for a few seconds, then the window manager restarts.

Ubuntu 16.04 with kernel 4.14.

$ dmesg
[ 2245.773240] [drm] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688], reason: Hang on rcs0, action: reset
[ 2245.773241] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 2245.773241] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 2245.773242] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 2245.773242] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 2245.773242] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2245.773247] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2246.883491] asynchronous wait on fence i915:gnome-shell[1994]/1:a0fd timed out
[ 2253.763721] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2261.763886] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2269.924050] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2277.828202] i915 0000:00:02.0: Resetting rcs0 after gpu hang

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 17.2.4

The same problem occurs with Mesa 17.0.7 and kernel 4.13.

Please let me know what other information I can provide to help with this.
Comment 1 shane 2018-03-14 02:09:12 UTC
Created attachment 138087 [details]
Content of /sys/class/drm/card0/error

I'm also getting this exact error. I was running XScreensaver at the time. I think the `rubikblocks` GL hack was running.

Ubuntu 17.10 4.13.0-36-generic
OpenGL version string: 3.0 Mesa 17.2.8
Lenovo ThinkPad X1 Carbon 4th Gen
Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
eDP-1 connected primary 2560x1440+0+1440
HDMI-2 connected 2560x1440+0+0

filename:       /lib/modules/4.13.0-36-generic/kernel/drivers/gpu/drm/i915/i915.ko
license:        GPL and additional rights
description:    Intel Graphics
author:         Intel Corporation
author:         Tungsten Graphics, Inc.
firmware:       i915/bxt_dmc_ver1_07.bin
firmware:       i915/skl_dmc_ver1_26.bin
firmware:       i915/kbl_dmc_ver1_01.bin
firmware:       i915/skl_guc_ver6_1.bin
firmware:       i915/kbl_huc_ver02_00_1810.bin
firmware:       i915/bxt_huc_ver01_07_1398.bin
firmware:       i915/skl_huc_ver01_07_1398.bin
srcversion:     F27B28CF28ECAE28997AF44
Comment 2 Elizabeth 2018-03-26 14:57:27 UTC
Hello, sorry for the delay. Philip, is this still happening with mesa 17.3.6? This could be a dup of https://bugs.freedesktop.org/show_bug.cgi?id=103555.

Shane, your hang seems to be a different issue. If still reproducible could  you open a new bug for this case. Thank you.
Comment 3 Elizabeth 2018-03-26 14:59:46 UTC
Moving to i965 since is skl.
Comment 4 GitLab Migration User 2019-09-25 19:06:12 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/1660.

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.