Red Hat Bugzilla – Bug 475374
Make clock source functions consistent between x86_64 & i386 arches
Last modified: 2010-10-23 02:25:23 EDT
Created attachment 326225 [details]
RHEL5 initial patch for this issue
Description of problem:
x86_64 uses nopmtimer, nohpet, and notsc to control which clock is used for
the GTOD clock. i386 uses "clock=[hpet|pmtmr|tsc]" to control which clock
is used for both the wall and the GTOD clock.
Make them consistent between arches.
Version-Release number of selected component (if applicable): -125.el5
Additional info: Attached patch tested on an xw9400 with HPET enabled in BIOS on both x86_64 and i386 arches.
Quick note on the patch, disable_pmtmr() is not upstream -- I have just pushed a patch to add it upstream.
Created attachment 326307 [details]
RHEL5 fix for this issue
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Updating PM score.
You can download this test kernel from http://people.redhat.com/dzickus/el5
Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so. However feel free
to provide a comment indicating that this fix has been verified.
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.