[Bug 103290] New: [drm] GPU HANG: ecode 5:0:0xfe7dfe7f, in plasmashell [1624], reason: Hang on render ring, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 16 08:57:36 UTC 2017


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

            Bug ID: 103290
           Summary: [drm] GPU HANG: ecode 5:0:0xfe7dfe7f, in plasmashell
                    [1624], reason: Hang on render ring, action: reset
           Product: DRI
           Version: unspecified
          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: vkosharskiy at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 134860
  --> https://bugs.freedesktop.org/attachment.cgi?id=134860&action=edit
Saved GPU crash dump

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

IntelĀ® HD Graphics 

00:02.0 [8086:0046] VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 02)

CPU Intel(R) Core(TM) i3 CPU M 380

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


More information about the intel-gfx-bugs mailing list