I am running 5.14.21-150400.24.33-default for 11d now without the bug. But the old bug happened only after 35d without me doing anything, so there will always be a newer kernel already when it happens that rarely. Could it be related to my chronyd interacting with the clock more often, because it is part of pool.ntp.org? # cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc # cat /sys/devices/system/clocksource/clocksource0/available_clocksource tsc hpet acpi_pm