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: Wed, 18 Apr 2018 10:28:55 +0000 [thread overview]
Message-ID: <bug-104520-502-G7kTh5wv8l@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104520-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1966 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104520
--- Comment #20 from hfekih@cannon.com ---
same problem here.
I am using Intel(R) Celeron(R) CPU N3160
reproduced on Linux (kernel) 4.16.2 and 4.14.34, (Mesa 17.3.8)
problem can be reproduced by starting any application using OPEN GL ES
root@ca-linux:/home/cannon$ glmark2-es2-drm
=======================================================
glmark2 2014.03
=======================================================
OpenGL Information
GL_VENDOR: Intel Open Source Technology Center
GL_RENDERER: Mesa DRI Intel(R) HD Graphics 400 (Braswell)
GL_VERSION: OpenGL ES 3.1 Mesa 17.3.8
=======================================================
[build] use-vbo=false:i965: Failed to submit batchbuffer: Input/output error
----------------------------------------------------------------------------
dmesg output:
[ 38.859784] [drm] GPU HANG: ecode 8:0:0xe757feff, in glmark2-es2-drm [346],
reason: Hang on rcs0, action: reset
[ 38.859788] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 38.859789] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 38.859791] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 38.859792] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 38.859794] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 38.859869] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 41.905511] i915 0000:00:02.0: Resetting chip after gpu hang
[ 41.952424] asynchronous wait on fence i915:glmark2-es2-drm[346]/2:2 timed
out
[ 47.072637] i915 0000:00:02.0: i915_reset_device timed out, cancelling all
in-flight rendering.
[ 51.372311] i915 0000:00:02.0: Failed to reset chip
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2847 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
next prev parent reply other threads:[~2018-04-18 10:28 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
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 [this message]
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-G7kTh5wv8l@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.