Forums

Resolved
0 votes
After recent updates to the kernel and reboot of a ClearOS machine, I noticed the following filling /var/log/messages like crazy:

Feb 17 04:34:07 mgtserver kernel: Clocksource tsc unstable (delta = 333297569 ns). Enable clocksource failover by adding clocksource_failover kernel parameter
Feb 17 04:34:07 mgtserver kernel: Clocksource tsc unstable (delta = 333235032 ns). Enable clocksource failover by adding clocksource_failover kernel parameter.
Feb 17 04:34:08 mgtserver kernel: Clocksource tsc unstable (delta = 333321526 ns). Enable clocksource failover by adding clocksource_failover kernel parameter.
Feb 17 04:34:08 mgtserver kernel: Clocksource tsc unstable (delta = 334601362 ns). Enable clocksource failover by adding clocksource_failover kernel parameter


Yes, twice per second!
echo kvm-clock > /sys/devices/system/clocksource/clocksource0/current_clocksource
should have solved that, but didn't. Maybe deactivating ntp could have been a solution, but since it was maintainance time anyway, I applied the kernel parameter to grub and rebooted. This solved the problem. The question is, will this remain effective after the enxt kernel update?

Just wanted to drop that here, since others might run into the same issue.

See this for more information: https://blog.johncheng.com/?p=2203
Tuesday, February 19 2013, 01:36 AM
Share this post:
Responses (1)
  • Accepted Answer

    Tuesday, February 19 2013, 04:53 PM - #Permalink
    Resolved
    1 votes
    Stefan Garthe wrote:
    ... I applied the kernel parameter to grub and rebooted. This solved the problem. The question is, will this remain effective after the enxt kernel update?

    Yup. The kernel upgrade uses the current grub entry as a template -- any custom parameters will be copied on an upgrade.
    The reply is currently minimized Show
Your Reply