Bug 159700 - kernel reports a bug when performing software suspend, and hungs
Summary: kernel reports a bug when performing software suspend, and hungs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-07 08:38 UTC by yuval aviel
Modified: 2015-01-04 22:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-09 02:02:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description yuval aviel 2005-06-07 08:38:11 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux 2.6.11-1.14_FC3.root_cubbi1_swsusp2; X11; i686; en_US, he) (KHTML, like Gecko)

Description of problem:
In an attempt to test hibernation in FC4,  
I installed the latest kernel-2.6.11-1.1369_FC4.src.rpm and enabled *only* the 
software suspend option. 
 
after building and installing the new kernel, I started the hibernation 
process with "echo 4 >> /proc/acpi/sleep". This used to work in FC1 and 2. 
Here it report a kernel BUG and hangs. 
Due to the freezing, I cant save the output. 
 

Version-Release number of selected component (if applicable):
kernel-2.6.11-1.1369_FC4

How reproducible:
Always

Steps to Reproduce:
1. build and install swsusp enabled kernel 
2. echo 4 >> /proc/acpi/sleep 
3. 
   

Additional info:

Comment 1 Warren Togami 2005-06-07 10:07:08 UTC
Does echo 3 have any better luck?


Comment 2 yuval aviel 2005-06-07 10:13:08 UTC
Forgot to mention: The machine is HP nx9000 (Laptop). 
On this machine suspend to RAM (sleep mode 3) never worked. I.e. it never 
succeeded to fully resume. I think it got to do with the BIOS, but i'm not 
sure. 

Comment 3 Dave Jones 2005-06-09 02:02:06 UTC
swsusp isn't enabled in our builds for precisely reasons like this, it just
isn't ready for production.



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