Bug 475502

Summary: [LTC 5.4 FEAT] ACPI C3/C4 Support [201240]
Product: Red Hat Enterprise Linux 5 Reporter: IBM Bug Proxy <bugproxy>
Component: kernelAssignee: Peter Martuccelli <peterm>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 5.4CC: jjarvis, jlarrew, peterm
Target Milestone: alphaKeywords: FutureFeature, OtherQA
Target Release: 5.4   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-26 12:46:01 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:
Bug Depends On:    
Bug Blocks: 445204, 483701, 483784, 488642, 488646    

Description IBM Bug Proxy 2008-12-09 15:30:57 UTC
=Comment: #0=================================================
Emily J. Ratliff <ratliff.com> - 
1. Feature Overview:
Feature Id:	[201240]
a. Name of Feature:	ACPI C3/C4 Support
b. Feature Description
Power savings is quickly becoming one of the main focus areas for system x.  We need to ensure
additional ACPI power states (c-states), particularly c3/c4 deep sleep modes, are supported in Linux
so they are ready to be used at the enterprise level, and in support of IBM's power management strategy.

Additional Comments:	Once we get C3/C4 enabled hardware we will be validating this feature in 5.4. 
One bug fix that we are looking for is bugzilla 474091 (TSC keeps running in C3+).

2. Feature Details:
Sponsor:	xSeries
Architectures:
x86
x86_64

Arch Specificity: Both
Affects Core Kernel: Yes
Affects Kernel Modules: Yes
Delivery Mechanism: Direct from community
Category:	Kernel
Request Type:	Kernel - Enhancement from IBM
d. Upstream Acceptance:	Accepted
Sponsor Priority	1
f. Severity: High
IBM Confidential:	no
Code Contribution:	no
g. Component Version Target:	Some of this may just work, because laptops already support this. For
Servers, it must be tested. However, until we have servers that support C3/C4, it's difficult to
guess which upstream kernel any code (if needed) will be targeted for.

3. Business Case
IBM Active Energy Manager will require ACPI C3/C4 Support

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Monte Knutson, mknutson.com, 877-894-1495

Technical contact(s):
Kevin Stansell, kstansel.com
Chris McDermott, mcdermoc.com

IBM Manager:
Julio Alvarez, julioa.com

Comment 1 John Jarvis 2008-12-23 21:18:43 UTC
IBM is signed up to test and provide feedback.

Comment 2 John Jarvis 2009-01-15 14:16:54 UTC
What is the status of the C3/C4 enabled hardware?  Has this been tested with the latest 5.3 code?

Comment 3 IBM Bug Proxy 2009-01-15 16:10:58 UTC
We have verified C3/C4 support on an iDataPlex dx340. We now have C3/C4 enabled on x3550 M2 and x3650 M2. We will confirm RHEL5.3 works correctly on those platforms and report the results here. If all goes well this can be closed.

Comment 4 RHEL Program Management 2009-02-16 15:19:09 UTC
Updating PM score.

Comment 5 John Jarvis 2009-03-24 19:19:45 UTC
Any update on the testing mentioned in this bug?  Did this work correctly with RHEL 5.3?

Comment 6 IBM Bug Proxy 2009-03-26 00:00:26 UTC
------- Comment From djwong.com 2009-03-25 19:51 EDT-------
Seems to work fine with the RHEL 5.3 RC2 kernel (2.6.18-128.el5), thanks. :)

Comment 7 John Jarvis 2009-03-26 12:46:01 UTC
Closing CURRENTRELEASE based on comment 6

Comment 8 IBM Bug Proxy 2011-02-22 09:41:58 UTC
------- Comment From  2011-02-22 04:38 EDT-------
We are reviewing this as a part of backlog bug clean up activity.
Please feel free to reopen once you have any valid update.

Thanks
Muni

------- Comment From  2011-02-22 04:40 EDT-------
(In reply to comment #12)
> We are reviewing this as a part of backlog bug clean up activity.
> Please feel free to reopen once you have any valid update.
>
> Thanks
> Muni

Closed this bug as per Redhat's comment.