[Bug 93668] New: kernel: [drm] GPU HANG message after waking from hibernation

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 11 08:11:08 PST 2016


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

            Bug ID: 93668
           Summary: kernel: [drm] GPU HANG message after waking from
                    hibernation
           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: morfikov at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

I'm getting the following log each time the machine is waking up from
hibernation:

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

It says to send the message here, so there it is.

I'm using debian sid, and I have the following options set in the i915 module:

options i915 lvds_downclock=1 fastboot=1

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


More information about the intel-gfx-bugs mailing list