dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset
Date: Thu, 01 Feb 2018 03:49:44 +0000	[thread overview]
Message-ID: <bug-104520-502-DCEd9XIZSm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104520-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1274 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104520

--- Comment #8 from xman <20830326@qq.com> ---
I am also hitting the same issue.
[ 1516.880515] [drm] GPU HANG: ecode 9:0:0x85dffffb, reason: Hang on rcs0,
action: reset
[ 1516.880517] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 1516.880517] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 1516.880518] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 1516.880518] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 1516.880518] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1516.880526] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1531.801142] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1539.837207] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1547.801180] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1555.801205] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 1559.001148] asynchronous wait on fence i915:compiz[1607]/1:243a timed out
[ 1563.801234] i915 0000:00:02.0: Resetting rcs0 after gpu hang

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2162 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-02-01  3:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07  8:16 [Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset bugzilla-daemon
2018-01-07  8:17 ` bugzilla-daemon
2018-01-07  8:24 ` bugzilla-daemon
2018-01-07  8:24 ` bugzilla-daemon
2018-01-15  6:51 ` bugzilla-daemon
2018-01-30 18:01 ` bugzilla-daemon
2018-01-30 18:02 ` bugzilla-daemon
2018-01-31 14:05 ` bugzilla-daemon
2018-01-31 14:06 ` bugzilla-daemon
2018-02-01  3:49 ` bugzilla-daemon [this message]
2018-02-18 21:39 ` bugzilla-daemon
2018-02-18 21:40 ` bugzilla-daemon
2018-02-18 21:43 ` bugzilla-daemon
2018-02-25 23:07 ` bugzilla-daemon
2018-02-27  8:34 ` bugzilla-daemon
2018-02-27  8:41 ` bugzilla-daemon
2018-02-27  8:41 ` bugzilla-daemon
2018-02-27  8:51 ` bugzilla-daemon
2018-03-28 22:47 ` bugzilla-daemon
2018-03-28 22:57 ` bugzilla-daemon
2018-03-28 23:00 ` bugzilla-daemon
2018-03-28 23:04 ` bugzilla-daemon
2018-04-18 10:28 ` bugzilla-daemon
2018-04-18 10:29 ` bugzilla-daemon
2018-06-11 21:26 ` bugzilla-daemon
2018-12-06 10:00 ` bugzilla-daemon
2019-01-28  7:05 ` bugzilla-daemon
2019-09-18 19:40 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-104520-502-DCEd9XIZSm@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox