proxmox v7.4.15 weird dmesg errors with 'clocksource: timekeeping watchdog...' and 'clocksource: wd-tsc-wd ... clock-skew test skipped!'

[Szymons]

Hello,

How can I fix weird dmesg errors :

[Thu Jul 27 10:51:09 2023] clocksource: timekeeping watchdog on CPU72: hpet wd-wd read-back delay of 114190ns
[Thu Jul 27 10:51:09 2023] clocksource: wd-tsc-wd read-back delay of 118311ns, clock-skew test skipped!
[Thu Jul 27 10:56:04 2023] clocksource: timekeeping watchdog on CPU73: hpet wd-wd read-back delay of 118590ns
[Thu Jul 27 10:56:04 2023] clocksource: wd-tsc-wd read-back delay of 125644ns, clock-skew test skipped!
[Thu Jul 27 11:01:15 2023] clocksource: timekeeping watchdog on CPU74: hpet wd-wd read-back delay of 113003ns
[Thu Jul 27 11:01:15 2023] clocksource: wd-tsc-wd read-back delay of 128577ns, clock-skew test skipped!
[Thu Jul 27 11:06:10 2023] clocksource: timekeeping watchdog on CPU75: hpet wd-wd read-back delay of 108812ns
[Thu Jul 27 11:06:10 2023] clocksource: wd-tsc-wd read-back delay of 110000ns, clock-skew test skipped!
[Thu Jul 27 11:11:05 2023] clocksource: timekeeping watchdog on CPU76: hpet wd-wd read-back delay of 108114ns
[Thu Jul 27 11:11:05 2023] clocksource: wd-tsc-wd read-back delay of 107695ns, clock-skew test skipped!
[Thu Jul 27 11:16:16 2023] clocksource: timekeeping watchdog on CPU77: hpet wd-wd read-back delay of 118800ns
[Thu Jul 27 11:16:16 2023] clocksource: wd-tsc-wd read-back delay of 119568ns, clock-skew test skipped!
[Thu Jul 27 11:21:11 2023] clocksource: timekeeping watchdog on CPU78: hpet wd-wd read-back delay of 118590ns
[Thu Jul 27 11:21:11 2023] clocksource: wd-tsc-wd read-back delay of 134933ns, clock-skew test skipped!
[Thu Jul 27 11:26:06 2023] clocksource: timekeeping watchdog on CPU79: hpet wd-wd read-back delay of 115517ns
[Thu Jul 27 11:26:06 2023] clocksource: wd-tsc-wd read-back delay of 121733ns, clock-skew test skipped!
[Thu Jul 27 11:31:17 2023] clocksource: timekeeping watchdog on CPU80: hpet wd-wd read-back delay of 114958ns
[Thu Jul 27 11:31:17 2023] clocksource: wd-tsc-wd read-back delay of 109022ns, clock-skew test skipped!

proxmox version :

proxmox-ve: 7.4-1 (running kernel: 5.15.108-1-pve)
pve-manager: 7.4-15 (running version: 7.4-15/a5d2a31e)
pve-kernel-5.15: 7.4-4
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.15.107-2-pve: 5.15.107-2
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-4
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

processor

AMD EPYC 7713 64-Core Processor

 

[Szymons]

I just found some fix with changing clock source :
from

cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc

into

bash -c 'echo hpet > /sys/devices/system/clocksource/clocksource0/current_clocksource'

but I am first time in my life troubling this issue anyone knows what was wrong here ?