linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-pm@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: [REGRESSION] fdo bug 86565 - black screen after resume from hibernation since linux kernel 3.18
Date: Wed, 18 Feb 2015 09:13:32 +0100	[thread overview]
Message-ID: <2578139.MpDzvyvMS0@merkaba> (raw)

Hi!

I reported this with fdo for intel drivers back then as

https://bugs.freedesktop.org/86565

as I thought it to likely be an intel driver bug.


As it still happens and I am not sure of that anymore, I report here as 
well. I still CC intel gfx list as well, as I didn´t get a comment on the 
debug log I attached to the bug report till now.


Since linux kernel 3.18-rc2 I sometimes get a black screen after resuming 
from hibernation via in-kernel-suspend. With 3.17 I didn't have this 
issue. Additionally, sometimes on hibernation the machine after writing 
the image does not switch off, but stays on with the power LED blinking. I 
then usually switch it off manually by pressing power button longer and it 
usually resumes just fine after it.

The first issue is most annoying and it seems they are unrelated, cause as 
I found now, the first issue happens even if the second one didn´t happen 
before. When the screen is black it takes some minutes usually and then  
it displays the lock screen again. As it doesn´t happen on every resume 
from hibernation and it may work okay for five or more attempts, bisecting 
this likely would take ages.

This is with a ThinkPad T520 with BIOS Version: 8AET63WW (1.43 ), Release 
Date: 05/08/2013. The black screen happens with 3.18-rc2 upto 3.19-rc7. 
With Intel Sandybridge graphics (no nvidia optimus).


I think it may be more of a general PM management issue, as I now heard 
the the laptop was making the usual resume audio signal *after* the black 
screen delay. Thus I thought it may be stuck in general resume.


In comment #8 I attached a debug log with no_console_suspend drm.debug=0xe 
initcall_debug as being asked for:

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


I didn´t yet receive any comment on this.

Any further ideas?


If not I will test with 3.20-rc2 again and also try the patch Jani 
mentioned in comment #7 in case its not in there.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

             reply	other threads:[~2015-02-18  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  8:13 Martin Steigerwald [this message]
2015-02-18 13:34 ` [Intel-gfx] [REGRESSION] fdo bug 86565 - black screen after resume from hibernation since linux kernel 3.18 Jani Nikula

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2578139.MpDzvyvMS0@merkaba \
    --to=martin@lichtvoll.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-pm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).