Bug 93719 - [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22
Summary: [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI 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-14 20:57 UTC by Jerome
Modified: 2017-07-24 22:43 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg log covering boot/suspend/resume with drm.debug=0x04 (32.12 KB, text/plain)
2016-01-14 20:57 UTC, Jerome 		no flags Details
View All

Description Jerome 2016-01-14 20:57:19 UTC 
Created attachment 121048 [details]
dmesg log covering boot/suspend/resume with drm.debug=0x04

Resume from suspend fails, systematic over 5 tests. The screen stays black, VT switching doesn't work. The machine is still functional and can be accessed with SSH, dmesg log covering a boot/suspend/resume cycle with drm.debug=0x04 is attached.

Intel DRM nightly kernel 4.4.0:
  commit fdbeff6c26904cedc81e0b3383d3174802230a60
  2016y-01m-12d-18h-13m-13s UTC integration manifest

PC is a Thinkpad X1 3rd gen, i5-5200U, 2560x1440 internal screen. No peripheral attached, this happens only with the internal display.

This is somewhat related to bug #91585: once this bug is fixed, I'll be able to check whether Intel kernel 4.4.0 fixes #91585 or not.

Thanks
Comment 1 Jerome 2016-02-01 19:00:57 UTC 
The issue doesn't happen anymore with the following nightly kernel 4.5.0-rc1:
  commit 29cc50da24351521b481482cb64043304cafbba9
  2016y-01m-29d-20h-37m-33s UTC integration manifest

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.