33 ms·
Not a network code issue but my favorite anecdote for this type of thing. There was a Xen hypervisor bug for YEARS that would cause the clock to jump 20(?) minu
by Rapzid 10y ago
Not a network code issue but my favorite anecdote for this type of thing. There was a Xen hypervisor bug for YEARS that would cause the clock to jump 20(?) minutes occasionally. The root cause was found in inline assembly due to a compiler oddity. It was found during some bug day/week thing by somebody with the assembly knowledge who just happened to look at that code and see an issue. He had no idea of the significance of what he found :D
- simcop2387 10y agoI'd love to read more about that. Got a link or anything more to google on?
- Rapzid 10y agoIt was actually 50 minutes. Here is what I could turn up: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599161 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599161 https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=599161;filename=x86-time-scale-asm.patch;msg=234 https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=5991... I remember it was patched and out by debian right around Christmas; quite the present. This bug made me feel very helpless. I recall there being more information around the circumstances of its discovery on the Xen mailing list.