[Bug 93868] New: Render issue after Sleep

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jan 26 02:09:38 PST 2016


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

            Bug ID: 93868
           Summary: Render issue after Sleep
           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: a.m.wink at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

Toshiba Portege laptop 
Hardware: i7 5500u
Graphics: Intel HD graphics 5500
Linux version: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17)

After sleep (because of inactivity, closing the lid or choosing 'leave ->
sleep' from the X session menu in KDE), The keyboard and mouse are unresponsive
in the session and the screen does not appear to build any more (a
semi-transparent start menu persists).

I can use the keys to go to a console session to do a dmesg, whose last lines
read:

[drm] stuck on render ring
[drm] GPU HANG: ecode 0:0x00dff888, in Xorg [751], reason: Ring hung, 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] Enabling RC6 states: RC6 on, RC6p off, RC6pp off

Not sure what else to send you but attached is the error file from /sys

bw
Alle Meije

-- 
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/20160126/d71e077f/attachment-0001.html>


More information about the intel-gfx-bugs mailing list