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 100101] [i915] GPU HANG: ecode 6:0:0x85deffbc, in gnome-shell [3664], reason: Hang on render ring, action: reset
Date: Sat, 11 Mar 2017 05:10:24 +0000	[thread overview]
Message-ID: <bug-100101-502-ddMZkd5HMV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100101-502@http.bugs.freedesktop.org/>


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

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

Eric Blau <eblau@eblau.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Drivers/DRI/i965            |Drivers/DRI/i915
         QA Contact|intel-3d-bugs@lists.freedes |dri-devel@lists.freedesktop
                   |ktop.org                    |.org
           Assignee|intel-3d-bugs@lists.freedes |dri-devel@lists.freedesktop
                   |ktop.org                    |.org

--- Comment #3 from Eric Blau <eblau@eblau.com> ---
I hit a very similar hang while using Chromium and watching HTML5 video. My
video hung and journalctl shows the following logs:

Mar 10 20:08:26 eric-macbookpro kernel: [drm] GPU HANG: ecode 8:0:0x6e51c723,
in chromium [5089], reason: Hang on ren
Mar 10 20:08:26 eric-macbookpro kernel: [drm] GPU hangs can indicate a bug
anywhere in the entire gfx stack, includin
Mar 10 20:08:26 eric-macbookpro kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> D
Mar 10 20:08:26 eric-macbookpro kernel: [drm] drm/i915 developers can then
reassign to the right component if it's no
Mar 10 20:08:26 eric-macbookpro kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always a
Mar 10 20:08:26 eric-macbookpro kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Mar 10 20:08:26 eric-macbookpro kernel: drm/i915: Resetting chip after gpu hang
Mar 10 20:08:34 eric-macbookpro kernel: drm/i915: Resetting chip after gpu hang
Mar 10 20:08:42 eric-macbookpro kernel: drm/i915: Resetting chip after gpu hang
Mar 10 20:08:52 eric-macbookpro kernel: drm/i915: Resetting chip after gpu hang


I did not have a way to capture the GPU crash dump unfortunately. I'm running
the same kernel version:

Linux eric-macbookpro 4.9.11-1-ARCH #1 SMP PREEMPT Sun Feb 19 13:45:52 UTC 2017
x86_64 GNU/Linux

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

[-- Attachment #1.2: Type: text/html, Size: 3741 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

       reply	other threads:[~2017-03-11  5:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-100101-502@http.bugs.freedesktop.org/>
2017-03-11  5:10 ` bugzilla-daemon [this message]
2017-03-11 17:22 ` [Bug 100101] [SNB GT1] GPU HANG: ecode 6:0:0x85deffbc, in gnome-shell [3664], reason: Hang on render ring, action: reset bugzilla-daemon
2017-03-16 13:30 ` bugzilla-daemon
2017-03-16 13:32 ` bugzilla-daemon
2017-06-03  2:58 ` 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-100101-502-ddMZkd5HMV@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