Skip to content
This repository has been archived by the owner on May 8, 2024. It is now read-only.

Unstable clocksource #244

Open
cvc90 opened this issue Oct 12, 2022 · 4 comments
Open

Unstable clocksource #244

cvc90 opened this issue Oct 12, 2022 · 4 comments

Comments

@cvc90
Copy link

cvc90 commented Oct 12, 2022

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

@fbelavenuto
Copy link
Owner

Please try disable only "Disable C1E Support mode on motherboard" option

@cvc90
Copy link
Author

cvc90 commented Oct 14, 2022

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
hpet
acpi_pm

@cvc90
Copy link
Author

cvc90 commented Oct 14, 2022

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:
kernel: [ 315.602346] clocksource: 'acpi_pm' wd_now: e2a660 wd_last: b3549b mask: ffffff
kernel: [ 315.614281] clocksource: 'tsc' cs_now: 10242dfe3b3 cs_last: fe1e9f0a6e mask: ffffffffffffffff

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?

@fbelavenuto
Copy link
Owner

Hello, I don't know which one is better, but if this 'tsc' worked well, use it.

@fbelavenuto fbelavenuto pinned this issue Nov 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants