[Bug 105690] New: Xorg crash with «GPU HANG» message at dmesg

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 105690
           Summary: Xorg crash with «GPU HANG» message at 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: linux0iid at yandex.ru
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

Excerpt from dmesg:
----
[389887.717305] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [708], reason:
Hang on rcs0, action: reset
[389887.717310] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[389887.717312] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[389887.717313] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[389887.717315] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[389887.717317] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[389887.717327] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[389895.716971] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[389903.717059] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[389911.781048] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[389919.717182] i915 0000:00:02.0: Resetting rcs0 after gpu hang
----

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