Maybe some laymen explanation:
- Typically you have NTP installed which should make sure that the time in your system stay synchornized with a atom clock time server
- If the clock should, for whatever reason, be dramatically wrong, the NTP does usually not jump to the correct time but incrementally works to correct the time bit by bit
- Klipper alyways compares the RPi clock with the MCU timing to stay in sync and schedule all necessary actions
- Now if NTP is currently working to correct the clock, Klipper has no basis anymore to compare as the clock is different whenever Klipper checks it.
Make sure you have a proper setup NTP on your host and this error should not happen anymore. An initial clock correction can be done with the ntpdate command which also “jumps” the time.
Depending on the used distribution the more lightweight timesyncd can be used.
For all these tools and abundance of guides are available in the internet, e.g.