Randomly got timer too close

General Discussion
1

Basic Information:

Printer Model: KP5L
MCU / Printerboard: Host: Intel 10th i3, Printerboard: Kingroon KP3S v1.3
klippy.log timer_too_close.log (38.2 KB)

Describe your issue:

Hi folks, today I saw twice times: “timer too close” issue. I used to get 1 before, weeks ago. It happens to me randomly. And I don’t see anything related in the log. I am using a 10th i3 as host and almost no load at that time. Any idea what is wrong?

2 
Transition to shutdown state: MCU 'mcu' shutdown: Timer too close
This often indicates the host computer is overloaded. Check
for other processes consuming excessive CPU time, high swap
usage, disk errors, overheating, unstable voltage, or
similar system problems on the host computer.

Typically the reasons are as stated in the error message.

Is the host a dedicated box or is Klipper running in a virtualized environment?

3

Running in wsl - ubuntu

4

Running Klipper in a virtualized environment is not supported since it can lead to exactly such issues.
Klipper is very sensitive to timing issues and needs direct hardware access without any virtual layers in between.