Bug 93868 - Render issue after Sleep
Summary: Render issue after Sleep
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-26 10:09 UTC by Alle Meije Wink
Modified: 2017-07-24 22:43 UTC (History)
1 user (show)

See Also:
i915 platform: BDW
i915 features: GPU hang


Attachments
file /sys/class/drm/card0/error, GZipped (417.90 KB, text/plain)
2016-01-26 10:09 UTC, Alle Meije Wink
no flags Details
dmesg output (66.93 KB, text/plain)
2016-01-26 10:12 UTC, Alle Meije Wink
no flags Details

Description Alle Meije Wink 2016-01-26 10:09:38 UTC
Created attachment 121297 [details]
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
Comment 1 Alle Meije Wink 2016-01-26 10:12:07 UTC
Created attachment 121298 [details]
dmesg output
Comment 2 Jari Tahvanainen 2017-03-10 10:11:58 UTC
a.m.wink@gmail.com - I'm really sorry about this looong delay until getting back to you. Do still see this problem, preferable on newer kernel (compiled from drm-tip) ?
Comment 3 Chris Wilson 2017-03-10 10:16:07 UTC
It did not reload the aliasing-ppgtt after resume.
Comment 4 Alle Meije Wink 2017-03-10 12:32:20 UTC
I still have the result that if the screen goes black, eg. when the battery is about to die, and if I rescue it by plugging it in, mouse and keyboard are unresponsive as before.

Have not looked at the error messages but still using kernel 
3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u1 (2017-02-22)

Could you please direct me to that update and how to make sure that it's installed? Really happy to help solve this.
Comment 5 Chris Wilson 2017-03-10 13:50:14 UTC
You need to jump forward about 3 years of kernel/driver development to v4.9+
Comment 6 Alle Meije Wink 2017-03-10 14:04:44 UTC
Well my post was from last year -- the problem was definitely there then.

RE versions, this is what I have

server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.0.3
OpenGL core profile shading language version string: 4.30
OpenGL version string: 3.0 Mesa 12.0.3
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.0.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

and I do a regular apt-get upgrade.
Comment 7 Jani Nikula 2017-03-10 14:44:43 UTC
Please look into upgrading to the kernel, and preferrably other graphics stack components, from jessie-backports. The kernel version on jessie-backports is v4.9.

Closing the bug. Please reopen if the problem persists on v4.9. Thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.