From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset Date: Tue, 30 Jan 2018 18:01:54 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1744435120==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id F35EB6E4F3 for ; Tue, 30 Jan 2018 18:01:53 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1744435120== Content-Type: multipart/alternative; boundary="15173353131.FA5cc.28967" Content-Transfer-Encoding: 7bit --15173353131.FA5cc.28967 Date: Tue, 30 Jan 2018 18:01:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D104520 --- Comment #4 from Michael Weitzel --- I had the same crash (for the first time) - also on KabyLake, ArchLinux, Ke= rnel 4.14.15-1-ARCH. I'll attach my crash dump. [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [636], reason: Hang on rcs0, action: reset [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, includ= ing userspace. [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's = not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [drm] GPU crash dump saved to /sys/class/drm/card0/error i915 0000:00:02.0: Resetting rcs0 after gpu hang i915 0000:00:02.0: Resetting rcs0 after gpu hang asynchronous wait on fence i915:kwin_x11[820]/1:23321 timed out i915 0000:00:02.0: Resetting rcs0 after gpu hang i915 0000:00:02.0: Resetting rcs0 after gpu hang i915 0000:00:02.0: Resetting rcs0 after gpu hang --=20 You are receiving this mail because: You are the assignee for the bug.= --15173353131.FA5cc.28967 Date: Tue, 30 Jan 2018 18:01:53 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 4 on bug 10452= 0 from Michael Weitzel 
I had the same crash (for the first time) - also on KabyLake, =
ArchLinux, Kernel
4.14.15-1-ARCH. I'll attach my crash dump.

[drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [636], reason: Hang on rcs0,
action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, includ=
ing
userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -&=
gt;
DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's =
not
a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always
attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
i915 0000:00:02.0: Resetting rcs0 after gpu hang
i915 0000:00:02.0: Resetting rcs0 after gpu hang
asynchronous wait on fence i915:kwin_x11[820]/1:23321 timed out
i915 0000:00:02.0: Resetting rcs0 after gpu hang
i915 0000:00:02.0: Resetting rcs0 after gpu hang
i915 0000:00:02.0: Resetting rcs0 after gpu hang

You are receiving this mail because:
  • You are the assignee for the bug.
= --15173353131.FA5cc.28967-- --===============1744435120== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1744435120==--