Bug 98303

Summary: Blank screen after resume
Product: DRI Reporter: nutrinfnon
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: SNB i915 features: power/suspend-resume
Attachments:
Description Flags
logs of none

Description nutrinfnon 2016-10-18 04:36:54 UTC 
Created attachment 127372 [details]
logs of

(copy of https://bugzilla.kernel.org/show_bug.cgi?id=176351)

When resuming from hibernate state, kernel linux 4.8.0, the screen is blank(acpi off) and it does not resume. Previous version 4.6.0 works fine, resuming screen is blank (acpi off), pressing a key screen it switch on, all right.

I done two test, first resume worked (restart after few seconds), second failed (restart after a while). In attach logs of both cases.

In the attached file I can see following:
Oct  5 06:57:46 abox gdm-Xorg-:0[1013]: (II) AIGLX: Resuming AIGLX clients after VT switch
Oct  5 06:57:46 abox gdm-Xorg-:0[1013]: (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (0, 0), rotation normal, reflection none
Oct  5 06:57:46 abox gdm-Xorg-:0[1013]: (EE) intel(0): failed to set mode: Invalid argument [22]
Oct  5 06:57:46 abox gdm-Xorg-:0[1013]: (WW) intel(0): failed to restore desired modes on VT switch
Oct  5 06:57:46 abox gdm-Xorg-:0[1013]: (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 0, disabling CRTC:26
...
Oct  5 06:58:05 abox kernel: [  919.079396] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc ffff880196939000 when fb was deleted
Oct  5 06:58:05 abox kernel: [  919.079460] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable plane with busy fb
Comment 1 nutrinfnon 2016-11-22 08:30:06 UTC 
Same hardware, using uefi boot, the issue diseappears.
Comment 2 yann 2016-11-22 10:23:18 UTC 
(In reply to nutrinfnon from comment #1)
> Same hardware, using uefi boot, the issue diseappears.

It looks like a BIOS issue then.
Comment 3 nutrinfnon 2016-11-23 06:08:22 UTC 
I'm not sure (because, until up 4.6.0, I always used BIOS CSM). For me, now,  it works, so I change this bug in "resolved as WORKSFORME".

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.