Bug 971055

Summary:	SAP 7.0: sblim-cmpi-base: incorrect max cpu frequency
Product:	Red Hat Enterprise Linux 7	Reporter:	Henning Sackewitz <henning.sackewitz>
Component:	sblim-cmpi-base	Assignee:	Vitezslav Crhonek <vcrhonek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Robin Hack <rhack>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0	CC:	amascari, fdanapfe, henning.sackewitz, jscotka, linux, lmiccini
Target Milestone:	rc	Keywords:	FutureFeature, HardwareEnablement
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	sblim-cmpi-base-1.6.2-3.fc19	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	971053	Environment:
Last Closed:	2014-06-13 10:10:55 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, 971056
Bug Blocks:	1018952, 1050219

Description Henning Sackewitz 2013-06-05 14:54:49 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 2 Frank Danapfel 2014-01-08 07:41:24 UTC

Removed RFE from title since this is really a bugfix and not a feature request

Comment 4 Ludek Smid 2014-06-13 10:10:55 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.