Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
What Do I Do If "Clocksource tsc unstable" Is Displayed After a dmesg Command Is Executed When RHEL 6.7 Has Been Running for a While?
Symptom
When Red Hat Enterprise Linux (RHEL) 6.7 has been running for a while, the message "Clocksource tsc unstable" is displayed after the dmesg | grep -i fail command is executed. The specific error messages are similar to the following:
2013-07-16T05:00:05.181538-04:00 xxxxxx kernel: Clocksource tsc unstable (delta = -95170507948 ns). Enable clocksource failover by adding clocksource_failover kernel parameter.
2013-07-16T05:00:05.181555-04:00 xxxxxx kernel: Clocksource tsc unstable (delta = -51539542975 ns). Enable clocksource failover by adding clocksource_failover kernel parameter.
Cause Analysis
In a multicore system, multiple cores or threads may be in hibernating or another state. Therefore, time stamp synchronization between the cores is not accurate.
Solution
Change the clock source to High Precision Event Timer (HPET) or another available one on the system. However, system performance deteriorates after the clock source change. Select the clock source based on the impact. For details, see the knowledge base on the Red Hat website at the following link:
