Bug 1007227 - cant resume from suspend with kernel-3.11.0-x.fc20.x86_64 on Toshiba Satellite L75D-A7283
Summary: cant resume from suspend with kernel-3.11.0-x.fc20.x86_64 on Toshiba Satellit...
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-09-12 07:26 UTC by collura
Modified: 2014-04-09 13:30 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-04-09 13:30:56 UTC
Type: Bug

Attachments (Terms of Use)
power manager utils bugreport info report (3.32 KB, text/plain)
2013-09-12 09:42 UTC, collura
no flags Details

Description collura 2013-09-12 07:26:43 UTC
Description of problem:

no resume from an imposed suspend with kernel-3.11.0-x

if let screen time out (backlight remains on [gray] but) screen blanks and locks and can log back in after hitting key (then can see password prompt) and entering password.

if select toolbar menu and choose <alt>-suspend
or if you close the lid on laptop
then (backlight turns off [black] but) 
get NO response when try to resume from the suspend by:
  opening the lid or 
  by pressing a key or 
  by moving mouse or 
  by <ctl><alt><f#> or
  by <alt><f2>restart or
  by <ctl><alt><backspace> or
  by <ctl><alt><del>

Version-Release number of selected component (if applicable):

  fully updated fc19 system but running kernel-3.11.0.x.fc20.x86_64

How reproducible:


Steps to Reproduce:
1. suspend by closing lid or by menu selection
2. fail when try to use keysequence to light up screen so can unlock

Actual results:

  screen stays black 

Expected results:

  screen wakes up, enter password, get back to work

Additional info:

   aditional system information:

Comment 1 collura 2013-09-12 09:42:26 UTC
Created attachment 796719 [details]
power manager utils bugreport info report

Comment 2 collura 2013-09-12 10:11:44 UTC
uncommenting the lines of /etc/acpi/events/videoconf:

 "# Configuration to turn on DPMS again on video activity, needed for some
  # laptops. Disabled by default, uncomment if your laptop display stays blank
  # after you close and open the lid.

  #action=/usr/sbin/vbetool dpms on

didnt help

Comment 3 collura 2013-10-05 07:58:08 UTC
same with fedora20-alpha livecd:

   cant resume from a forced suspend but can from a screen time out.

still broken but suspend/resume process seems closer because changes to the status lights seem more sane.  before fc20alpha the power and wifi lights didnt seem to shutoff in a reliable orderly fashion when force a suspend but do now.

Comment 4 collura 2013-12-01 12:22:13 UTC
not sure about kernel-3.11.9-300.fc20.x86_64 
(because was not booting when was checking) so this bug stays open.

however, since about kernel-3.13.0-0.rc1.git3.1.fc21.x86_64 and kernel-3.13.0-0.rc2.git0.1.fc21.x86_64 (which boot but dont shutdown lol) 
the resume from forced suspend is much improved but still quirky. 

(the rc1.git3.1 before resume 'top' command showed about xorg=70%cpu, gnome-shell=10%cpu but after resume 'top' showed about xorg=40% and gnome-shell=180% for  4core idles of about {before suspend 20%/60%/20%/20%, after syspend 70%/70%/70%/70%} and rc2.git0.1 was better with about {before suspend 10%/10%/10%/10%, after resume 10%/10%/10%/10% } ).

Comment 5 collura 2013-12-17 11:59:33 UTC
still broken as of kernel-3.12.5-301.fc20.x86_64
(boots though after up seems to blackscreenfreeze for 30sec occasionally) 

(kernel-3.13.0-0.rc4.git0.1.fc21.x86_64 can wake up but gives fresh login screen not just password prompt and when login the running programs from the other session arent there anymore but that was another bug report)

Comment 6 Steven Marks 2014-02-16 19:21:10 UTC
I observed the same problems as reporter but it not related to being a laptop. I do this on my desktop and have the same problem.

Once stuck in this state still can SSH into the computer and I observed that Xorg is taking up all the processing power. It looks like it getting in to a dead lock state. 

Are there any logs or information I can provide that will help this problem?

Comment 7 collura 2014-02-17 05:39:49 UTC
still there as of kernel-3.13.2-200.fc20.x86_64

(as with comment#5, can now resume with kernel-3.13.x
 but you end up in a new session somehow so 
 you lose all previously running programs when resume.

 while suspended you press power button, 
 get fresh login screen [instead of password resume screen], 
 then it looks like its going to log you in but instead 
 screen goes black again, 
 hit escape then you get the password resume screen,
 enter password and get the desktop finally 
 but it doesnt have the programs that were running when you suspended. )

also is possibly duplicated by:


Comment 8 Marvin Clavey 2014-02-23 17:18:31 UTC
I have the same problem as you do ... exactly... 

same as Bug 1059502

HP laptop dv7  fedora 20 
gnome 3.10.3  
Gallium 0.4 on AMD RS880

It appears to me the video driver is not initialised properly.

Comment 9 Jay Kamat 2014-03-02 19:11:55 UTC
For me, kernel 3.13.5 does not fix the problem, I still get a black screen upon resuming

Comment 10 Jay Kamat 2014-04-03 07:13:19 UTC
The latest kernel (3.15) on fedora rawhide still leaves a black screen after a sleep. Is there any progress being made on this bug?

Comment 11 collura 2014-04-07 20:18:47 UTC
resume from suspend began working at some point recently 
(think was a change around 3.13.7-200 but didnt quite work if remember)
but havent tracked down when.

currently running


havent tried 3.14.x or 3.15.x yet 
but see issue from comment#10 above for 3.15.x 

leaving open for now to see if continues to work for me 
and if gets fixed for others.

Comment 12 Steven Marks 2014-04-08 05:38:18 UTC
I am still seeing the issue withkernel-3.13.8-200.fc20.x86_64 and dracut-037-10.git201404021. 

I am using nvidia driver 331.49.

Comment 13 Josh Boyer 2014-04-09 13:29:47 UTC
Steven, we don't support systems using proprietary drivers.

Comment 14 Josh Boyer 2014-04-09 13:30:56 UTC
Closing since the original reporter says it works now.  Everyone else still having issues please open a new bug with your relevant details.

Note You need to log in before you can comment on or make changes to this bug.