We have two systems using SuperMicro X11DPH-i motherboards running on Alma Linux 8.6, stock kernel 4.18.0-372.32.1. Current BIOS version is 4.7.
We observe that after a few days, we see the following information in dmesg:
clocksource: timekeeping watchdog on CPU24: Marking clocksource 'tsc' as unstable because the skew is too large:
clocksource: 'hpet' wd_now: 602698cf wd_last: 5efaaaaa mask: ffffffff
clocksource: 'tsc' cs_now: 98e5b29df98 cs_last: 908699de0f6 mask: ffffffffffffffff
tsc: Marking TSC unstable due to clocksource watchdog
TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
sched_clock: Marking unstable (2751785016614, -304699205)<-(2752065155764, -577855072)
clocksource: Switched to clocksource hpet
Can you help us to determine why the clock source changes from TSC to HPET and what can be done to ensure that the clocksource remains TSC?
You can either add "tsc=unstable" in grub line to force kernel to use other clocksource (hpet, acpi_pm). If your application is critical and want to stick with tsc, try
add "intel_idle.max_cstate=1"in grub and rebuild the grub and see if it helps.
Print
Share