Post #1230612
2026-04-16 10:30 UTC
Today's fun headline: Kubernetes keeps breaking my 3D prints.
I've been debugging weird, apparently random times where Klipper would shutdown due to "Timer too close". The helpful error message says this happens when the host (PC) cpu is overloaded.
So I started watching btop closely, and found out that the process smashing the cpu from time to time was... clang?
The only thing using clang on this machine is cilium, to compile bpf programs that make networking happens. Why is cilium recompiling bpf programs randomly?
Welp, it's not random. It correlates perfectly with wlan assoc/disassoc to/from the different wifi bands.
Welp, I didn't see this one coming.
Replies (1)
-
@nadia@raru.re 2026-04-16 10:36
Granted, the node where I run klipper is a very shitty, dual-core machine. Easy to overwhelm. How band roaming ends up causing clang to peg the CPU is, in hindsight, somewhat easy to see, but still fun nonetheless.