Strange behavior on XY-movement after update

This is indeed strange, as the error basically pops up immediately. Never seen this before.
I know of no reports that updating Klipper might be causing this.

Generally, see Timer too close

  • Your graphs would not indicate something amiss, although the frequency graph looks a bit strange indeed
  • I’d try to simplify the system as much as possible and see if the error continues
    • Remove additional USB hardware
    • Remove non printing essential stuff like neo pixel
    • Remove displays
    • etc