Created attachment 136659 [details] dump /sys/class/drm/card0/error My notebook Laptop ThinkPad T570 (Type 20JW, 20JX) (20JW0004US) Xserver is periodically rebooted. Into kern.log: Jan 11 10:31:10 osipov kernel: [ 716.920056] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [517], reason: Hang on rcs0, action: reset Jan 11 10:31:10 osipov kernel: [ 716.920057] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 11 10:31:10 osipov kernel: [ 716.920058] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 11 10:31:10 osipov kernel: [ 716.920058] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 11 10:31:10 osipov kernel: [ 716.920058] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jan 11 10:31:10 osipov kernel: [ 716.920059] [drm] GPU crash dump saved to /sys/class/drm/card0/error Jan 11 10:31:10 osipov kernel: [ 716.920063] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 10:31:18 osipov kernel: [ 724.909575] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 10:31:26 osipov kernel: [ 732.909530] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 10:31:34 osipov kernel: [ 740.909505] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 10:31:42 osipov kernel: [ 748.909481] i915 0000:00:02.0: Resetting rcs0 after gpu hang
kern.log Jan 11 15:20:21 osipov kernel: [15200.920749] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 15:20:29 osipov kernel: [15208.952658] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 15:20:37 osipov kernel: [15216.952616] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 15:20:45 osipov kernel: [15224.952634] i915 0000:00:02.0: Resetting rcs0 after gpu hang Jan 11 15:20:53 osipov kernel: [15232.952586] i915 0000:00:02.0: Resetting rcs0 after gpu hang
Hello Vitaly, Is there a way to trigger this easily? Which distro and desktop environment are your using? Thank you.
Hello! My distro debian(unstable) - Linux 4.14.0-3-amd64 #1 SMP Debian 4.14.12-2 (2018-01-06) x86_64 GNU/Linux WM: awesome v4.2 (Human after all) # Compiled against Lua 5.3.3 (running with Lua 5.3) # D-Bus support: # # execinfo support: # # xcb-randr version: 1.5 # LGI version: 0.9.2 It noted that this occurs at the speed dial on the keyboard. Because I work in emacs, it often happens when working with it.
Hello again Vitaly, Could you try to find a way to reliable reproduce this, like with a heavy text filled emacs document or the kind? Thanks.
Hello Elizabeth! On the size of the file does not depend, they are not large less than 1 Kb, the texts are simple - the program code. After updating the kernel to: Linux 4.14.0-3-amd64 # 1 SMP Debian 4.14.13-1 (2018-01-14) x86_64 GNU / Linux a couple of days everything was fine, but then again it was 3-4 times. Now I try not to press the keys quickly :( I'm using emacs25 with GTK +. Thanks.
Replaced emacs25 with GTK+ by emacs25-lucid. So far so good, if there are problems, I'll let you know. Thanks.
(In reply to Vitaly from comment #6) > Replaced emacs25 with GTK+ by emacs25-lucid. > So far so good, if there are problems, I'll let you know. > Thanks. Error is present :(
Mesa devs have resolved a class of GPU hangs with this series: https://patchwork.freedesktop.org/series/37023/ If you can compile mesa with patches, please test the series for your use case. Otherwise we can wait until the patch is merged.
Those patches have been merged. Can you try Mesa master? You'll need to be sure that X picks up the new Mesa, which usually means replacing your system mesa and restarting X.
What is a Mesa master
(In reply to Vitaly from comment #10) > What is a Mesa master https://cgit.freedesktop.org/mesa/mesa/ master branch.
If you are not familiar with building Mesa for your system, it's probably best to wait for the Mesa 18.0 release and test with that.
OK I will be wait ver. 18. Now i have ver. 17.3.3
Created attachment 137228 [details] /sys/class/drm/card0/error I install packages from debian(experimental): libgl1-mesa-dri_18.0.0_rc2-1_amd64.deb libglapi-mesa_18.0.0_rc2-1_amd64.deb libglx-mesa0_18.0.0_rc2-1_amd64.deb glxinfo: OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.0-rc2 OpenGL version string: 3.0 Mesa 18.0.0-rc2 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.0-rc2 dump from /sys/class/drm/card0/error in attachment
Feb 8 11:12:31 osipov kernel: [37267.631978] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [561], reason: Hang on rcs0, action: reset Feb 8 11:12:31 osipov kernel: [37267.631981] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Feb 8 11:12:31 osipov kernel: [37267.631983] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Feb 8 11:12:31 osipov kernel: [37267.631984] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Feb 8 11:12:31 osipov kernel: [37267.631985] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Feb 8 11:12:31 osipov kernel: [37267.631987] [drm] GPU crash dump saved to /sys/class/drm/card0/error
My card: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
The known hang is fixed in mesa 18.0rc3 Unfortunately, this is not available in debian experimental yet :(
On Monday I install packages from debian(experimental): libdrm-intel1_2.4.89-1_amd64.deb libegl-mesa0_18.0.0_rc4-1_amd64.deb libgbm1_18.0.0_rc4-1_amd64.deb libgl1-mesa-dri_18.0.0_rc4-1_amd64.deb libglapi-mesa_18.0.0_rc4-1_amd64.deb libglx-mesa0_18.0.0_rc4-1_amd64.deb libxcb-dri2-0_1.12-1_amd64.deb libxcb-glx0_1.12-1_amd64.deb mesa-va-drivers_18.0.0_rc4-1_amd64.deb mesa-vdpau-drivers_18.0.0_rc4-1_amd64.deb While there are no errors
-- 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/1672.
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.