[Bug 102512] New: GPU hang and was reset

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 102512
           Summary: GPU hang and was reset
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: de_mox at zoho.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 133931
  --> https://bugs.freedesktop.org/attachment.cgi?id=133931&action=edit
GPU crash dump from /sys/class/drm/card0/error

I tried to open a video in Palemoon/Firefox, then the computer did not respond
to anything for a couple of seconds, recovered and when I looked into the logs,
I found this:

Sep 01 21:47:03 Denkbrett kernel: [drm] GPU HANG: ecode 7:0:0x54fffbfc, in
systemd-logind [335], reason: Hang on rcs, action: reset
Sep 01 21:47:03 Denkbrett kernel: [drm] GPU hangs can indicate a bug anywhere
in the entire gfx stack, including userspace.
Sep 01 21:47:03 Denkbrett kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Sep 01 21:47:03 Denkbrett kernel: [drm] drm/i915 developers can then reassign
to the right component if it's not a kernel issue.
Sep 01 21:47:03 Denkbrett kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
Sep 01 21:47:03 Denkbrett kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Sep 01 21:47:03 Denkbrett kernel: drm/i915: Resetting chip after gpu hang

So, here is a bug report,

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170901/346378bf/attachment-0001.html>