[Bug 86565] black screen after resume from hibernation since linux kernel 3.18

[bugzilla-daemon at freedesktop.org]

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

--- Comment #6 from Martin Steigerwald <Martin at Lichtvoll.de> ---
Created attachment 112050
  --> https://bugs.freedesktop.org/attachment.cgi?id=112050&action=edit
debug log of a hibernation cycles with longer delay with black screen on resume

This still happens with 3.19-rc3. Now with debug enabled as in:

martin at merkaba:~> cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-3.19.0-rc3-tp520-trim-all-bgroups+
root=/dev/mapper/sata-debian ro rootflags=subvol=debian
resume=/dev/mapper/sata-swap init=/bin/systemd no_console_suspend
no_console_suspend initcall_debug

Hmmm, I see, there is still something missing. The drm debug drm.debug=0xe, and
I accidentally added no_console_suspend twice, I will adapt this for the next
cycles.

Anyway, I attach a syslog with above kernel command line and the black screen
delay happening. I don´t see any noticable delays in the initcall debug
statements. I have another one from a few days before available as well.

To more observations:

1. It seems that if I wait long enough after resume, the box, I can actually
get the Plasma/KDE 4.14 screen locker, instead of the black screen.

2. it seems that the other issue of the delay on hibernating, with the blinking
power LED of the laptop instead of the laptop shutting down after saving the
image, seems related. Everytime I have this issue, on the next resume, I have
the black screen delay as well.

Okay, next round with drm.debug=0xe reenabled as well. This is really annoying
and I don´t like something breaks my user experience that way.

I also thought to try without systemd and using sysvinit again, but let me
first catch a DRM debug log as well.

-- 
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/20150110/ea0f2343/attachment.html>