Bug 240944

Summary: /proc/cpuinfo shows wrong clock speed (60GHz)
Product: Red Hat Enterprise Linux 3 Reporter: Bob Gautier <rgautier>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED WONTFIX QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: dhoward
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 18:36:33 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:
Attachments:
Description Flags
Full cpuinfo report
none
/var/log/dmesg from the affected machine none

Description Bob Gautier 2007-05-23 09:15:06 UTC 
Description of problem:

In a machine equipped with two 2.6Ghz Xeon processors, /proc/cpuinfo reports 
both processors running at 60Ghz.

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

2.4.21-27.0.2.ELsmp

How reproducible:

Uncertain (production machine, can't be rebooted at will)

Steps to Reproduce:

cat /proc/cpuinfo | grep MHz

Actual results:

cpu MHz      : 61146.158
cpu MHz      : 61146.158

Expected results:

cpu MHz      : 2600.00 (or thereabouts)
cpu MHz      : 2600.00 (or thereabouts)

Additional info:

The machine is an IBM HS20 blade and is running fine but this is causing our 
monitoring people some concern.
Comment 1 Bob Gautier 2007-05-23 09:15:06 UTC 
Created attachment 155224 [details]
Full cpuinfo report
Comment 2 Bob Gautier 2007-05-23 09:22:11 UTC 
Created attachment 155225 [details]
/var/log/dmesg from the affected machine
Comment 3 RHEL Program Management 2007-10-19 18:36:33 UTC 
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.