Bug 971056

Summary: SAP 5.10: sblim-cmpi-base: incorrect max cpu frequency
Product: Red Hat Enterprise Linux 5 Reporter: Henning Sackewitz <henning.sackewitz>
Component: sblimAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: high    
Version: 5.10CC: amahdal, amascari, fdanapfe, henning.sackewitz, linux, lmiccini, lmiksik, psklenar, vcrhonek
Target Milestone: rc   
Target Release: 5.10   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: sblim-1-50.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 971053 Environment:
Last Closed: 2014-09-16 00:31:04 UTC Type: Bug
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: 971053    
Bug Blocks: 971055    

Description Henning Sackewitz 2013-06-05 14:58:15 UTC
+++ This bug was initially created as a clone of Bug #971053 +++

Description of problem:

While enumerating the Linux_Processor class instances on systems with dynamic CPU frequencies, the MaxClockSpeed property is determined incorrectly as CurrentClockSpeed = /proc/cpuinfo: cpu MHz.

See http://sourceforge.net/p/sblim/bugs/2634/ for upstream bug fix.

Version-Release number of selected component (if applicable):
sblim-cmpi-base-1.6.1-1.el6.x86_64

Comment 1 RHEL Program Management 2013-06-06 14:27:48 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 2 RHEL Program Management 2013-06-23 23:37:39 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2013-06-23 23:57:40 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Frank Danapfel 2014-01-08 07:39:42 UTC
Removed RFE from title since this is really a bugfix and not a feature request

Comment 5 Luca Miccini 2014-01-28 15:34:43 UTC
On behalf of SAP LinuxLab I confirm that there will be the necessary commitment to test the new packages.  
Luca Miccini
Red Hat partner TAM @ SAP LinuxLAB

Comment 8 RHEL Program Management 2014-01-29 12:08:54 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 13 Alois Mahdal 2014-06-06 16:54:25 UTC
Verified on x86_64 (this is arch against which the bug has been reported).

On other archs the dynamic speed setting is not supported.

Comment 15 errata-xmlrpc 2014-09-16 00:31:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1201.html