Bug 724973 - Suspend doesn't work. Cursor is blinking on black screen and laptop hangs
Summary: Suspend doesn't work. Cursor is blinking on black screen and laptop hangs
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-22 13:18 UTC by ruby15
Modified: 2011-10-12 11:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-06 22:15:54 UTC
Type: ---


Attachments (Terms of Use)

Description ruby15 2011-07-22 13:18:07 UTC
Description of problem:
After last upgrade of the kernel I can't suspend my Fedore 15 on laptop Lenovo. Cursor is blinking in the up-left corner of the screen and capslock+suspend led are blinking.

Version-Release number of selected component (if applicable):
Fedora 15: 
2.6.38.8-35.fc15.i686.PAE #1 SMP Wed Jul 6 14:29:06 UTC 2011 i686 i686 i386 GNU/Linux

How reproducible:
Press suspend button or 'echo mem > /sys/power/state'

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
I have tried binary nvidia or nouveau drivers. Laptops hangs every time.

Comment 1 ruby15 2011-07-22 20:24:14 UTC
I have tried to trace the problem. I have set /sys/pm_test with values ( and test suspend):
freezer - OK
devices  - OK
platform  - OK
processors - Failed here 

I don't have idea how to trace it further.

Comment 2 ruby15 2011-07-25 10:02:37 UTC
I have solved this problem by command:
# yum remove VirtualBox-4.1.i686

or temporary solution  was: /etc/init.d/vboxdrv stop )

So the problem was not connected to the last Fedora upgrade but with switching from VirtualBox 4.0 to VirtualBox 4.1

So now I don't have problem with suspend, but event after removing Virutalbox I am not able to wake my laptop from the suspend.

Any idea how to trace it?
I have set 1 in /sys/power/pm_trace but I can't nothing interesting in demsg after restart.

Comment 3 ruby15 2011-07-25 20:35:47 UTC
This bug is reported on VirtualBox page http://www.virtualbox.org/ticket/9260

Comment 4 Dave Jones 2011-10-06 22:15:54 UTC
virtualbox's problem.

Comment 5 Frank Mehnert 2011-10-12 11:09:08 UTC
And fixed in VirtualBox 4.1.2.


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