[Bug 105219] New: [drm] GPU HANG: ecode 6:0:0x85fffffc, in gnome-shell [1514], reason: Hang on rcs0, action: reset

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 105219
           Summary: [drm] GPU HANG: ecode 6:0:0x85fffffc, in gnome-shell
                    [1514], reason: Hang on rcs0, action: reset
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: mikhail.v.gavrilov at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 137547
  --> https://bugs.freedesktop.org/attachment.cgi?id=137547&action=edit
dmesg

[ 4264.490623] [drm] GPU HANG: ecode 6:0:0x85fffffc, in gnome-shell [1514],
reason: Hang on rcs0, action: reset
[ 4264.490625] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 4264.490626] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 4264.490626] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 4264.490626] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 4264.490627] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 4264.490693] i915 0000:00:02.0: Resetting chip after gpu hang
[ 5202.670808] perf: interrupt took too long (6361 > 6315), lowering
kernel.perf_event_max_sample_rate to 31000
[ 9323.092160] perf: interrupt took too long (8025 > 7951), lowering
kernel.perf_event_max_sample_rate to 24000

-- 
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180222/94f97207/attachment.html>