Bug 726039

Summary: Machine Locks when put to sleep
Product: [Fedora] Fedora Reporter: Jerry LeVan <jerry.levan>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-01 16:27:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jerry LeVan 2011-07-27 11:47:41 UTC 
Description of problem:
Kernel 2.6.38.8-35 locks machine when 'sleep' action takes place

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

How reproducible:
Select sleep or shut lid 


Steps to Reproduce:
1.Select Sleep by any means
2.
3.
  
Actual results:
Machine become totally unresponsive immediately, can't change console
or ssh into machine. Hard reboot is the only way to recover.

Expected results:
The machine should enter sleep gracefully and awake gracefully

Additional info:
No problem with previous kernel ( which i am running now...)
Machine is a HP i7 laptop running an up to date fedora 15
Comment 1 Jerry LeVan 2011-07-27 12:23:35 UTC 
Sigh,

I think that my last yum update is what did the damage...
I was running 2.6.38.7-32.fc15.i686.PAE after finding
out that sleep was buggered in 2.6.38.7-35.fc15.i686.PAE 
and when I did the yum update this morning, sleep changed so now it locks the
machine.

I have dropped back to 2.6.38.7-30.fc15.i686.PAE. It still sleeps
ok.

so 2.6.38.7-35.fc15.i686.PAE and 2.6.38.7-32.fc15.i686.PAE are
now buggered. 

It appears that something is being clobbered
by recent yum updates.

Jerry
Comment 2 Jerry LeVan 2011-07-27 13:54:46 UTC 
I stand corrected...

VirtualBox version 4.1 kernel modules are the problem

If present, sleep locks the machine.
If I rmmod the rascal the machine can sleep and recover.

Jerry
Comment 3 Dave Jones 2011-09-01 16:27:50 UTC 
ah, that's something you'll need to bring up with the vbox maintainers.

that stuff causes us no end of problems.