[Bug 93930] New: Filing "GPU HANG" Bug (as requested by dmesg)

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 93930
           Summary: Filing "GPU HANG" Bug (as requested by dmesg)
           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: kenny at panix.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 121396
  --> https://bugs.freedesktop.org/attachment.cgi?id=121396&action=edit
/sys/class/drm/card0/error

Per dmesg:

----
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.086615] [drm] stuck on render ring
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087510] [drm] GPU HANG: ecode
7:0:0xa8603fff, in chrome [8147], reason: Ring hung, action: reset
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087511] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087512] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087512] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087513] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087513] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.089638] drm/i915: Resetting chip after
gpu hang
----

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