Bug 87529
Summary: | Wrong CPU clock speed calculated for 3.06 GHz CPUs | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ernst-Heinrich Klaas <ernst-heinrich.klaas> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-24 16:56:24 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
Ernst-Heinrich Klaas
2003-03-28 14:56:31 UTC
... or it measures real performace ;) actually this is just something cosmetic. rdtsc might not be reliable in overheated situations for example. I can't replicate this bug, all of the Xeon systems that I've tested show a cpu MHz field that's within 5% (typically much closer) of the clock speed advertised in the model string. State hasn't changed in the ~90 days, closing. |