Why does a Cisco USC blade with RHEL 6 return 'Marking TSC unstable due to check_tsc_sync_source failed' errors ?

Solution Verified - Updated -

Issue

Below errors seen on Cisco UCS blade with RHEL 6 systems:

Aug  4 05:52:51 <host> kernel: TSC synchronization [CPU#0 -> CPU#24]:
Aug  4 05:52:51 <host> kernel: Measured 2 cycles TSC warp between CPUs, turning off TSC clock.  <<-----
Aug  4 05:52:51 <host> kernel: Marking TSC unstable due to check_tsc_sync_source failed  

Environment

  • Red Hat Enterprise Linux 6
  • Cisco USC blade
  • UCSB-EX-M4-1
  • Cisco M4 Systems

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content