Bug 441632

Summary:	Can not hibernate in 5.2.
Product:	Red Hat Enterprise Linux 5	Reporter:	austin <austin.zhang>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
kernel sub component:	Power Management	QA Contact:	Kernel-QE - Hardware <kernel-qe-hw>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	low	CC:	jane.lv, jvillalo
Version:	5.2	Flags:	austin.zhang: needinfo-
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-02 13:16:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description austin 2008-04-09 08:02:10 UTC

Description of problem:
Hibernating failed in 5.2 beta in T61 (type id: 7661w1p)

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


How reproducible:
executing 'hibernate' by menu or command (pm-hibernate), the system can not 
enter into hibernating status.

Steps to Reproduce:
1.login
2.executing 'hibernate' by menu or command (pm-hibernate)
3.
  
Actual results:
can not enter into s4.

Expected results:
can enter into s4.

Additional info:

Comment 1 austin 2008-04-14 06:46:42 UTC

In the same box, install snapshot 4, the same steps for S4 testing, the S4 
works fine.

Comment 2 RHEL Program Management 2014-03-07 13:42:04 UTC

This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 3 RHEL Program Management 2014-06-02 13:16:37 UTC

Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).