**florian** @florian · Jan 24, 2018, 06:55

**florian** @florian · Jan 24, 2018, 06:55

florian @florian

ouch, looks like after the recent #linode migration I'm hit by the emulated APIC problem. https://marc.info/?t=151430936500001&r=1&w=2
#exoscale here I come I guess... *sigh*

**florian** @florian · Jan 24, 2018, 10:58

**florian** @florian · Jan 24, 2018, 10:58

Now I can't reproduce. Directly after reboot the clock was synced. About 30 minutes later it was behind bei 30 seconds and now it's in sync again. Weird.

**florian** @florian · 2018-01-25T17:14:49Z

florian @florian

still can't reproduce the clock issue on my #linode VM. It keeps perfect time now.

Jan 25, 2018, 17:14 · Web · 0 · 0

**Mike Belopuhov** @mike@x0r.be · Jan 25, 2018, 17:55

**Mike Belopuhov** @mike@x0r.be · Jan 25, 2018, 17:55

@florian Pssst... They're listening!

jj @jj · Jan 26, 2018, 11:26

jj @jj · Jan 26, 2018, 11:26

@florian perhaps it was 30% fast and now they patched for spectre and meltdown and compiled with retpoline and your clock is good again?