-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Unstable clocksource #244
Comments
Please try disable only "Disable C1E Support mode on motherboard" option |
Ok, I have disabled the C1E Support mode option on the motherboard. I'll test and see if the problem goes away. Of the types of clocksource, which is the most recommended of these three for the main system? tsc |
The clocksource error still appears even after disabling C1E Support mode, but the hrtimer: interrupt took error seems to have disappeared. kernel: [ 315.595573] clocksource: timekeeping watchdog: Marking clocksource 'tsc' as unstable because the skew is too large: After carrying out several tests and I understand how each one works, I believe that the best clocksource value is tsc, can anyone confirm what I am saying? |
Hello, I don't know which one is better, but if this 'tsc' worked well, use it. |
For several versions I have suffered this error, and I notice small freezes in the system, how could I solve it?
Disable C1E Support mode on motherboard? Disable or modify in the boot options of the main system has clocksource=acpi_pm?
Model: DS-3622xs+
DSM: DSM 7.1.1-42962
ARPL: v0.5-alpha1, with all modules activated
System: UBUNTU SERVER, with VMware
Copy error output from Kern.log file
hrtimer: interrupt took 11082175 ns
kernel: [ 384.258940] clocksource: timekeeping watchdog: Marking clocksource 'tsc' as unstable because the skew is too large:
kernel: [ 384.261201] clocksource: 'acpi_pm' wd_now: 8d5199 wd_last: 60e92e mask: ffffff
kernel: [ 384.263168] clocksource: 'tsc' cs_now: 1981c973dc9 cs_last: 1940283c820 mask: ffffffffffffffff
The text was updated successfully, but these errors were encountered: