I know, I have NetBSD on a Cobalt Raq2, but I hate the system as it’s impractical en badly sorted to install packages.
I prefer the APT system.
For me BSD is a mess to work with, sorry.
But it’s not the Linux kernel that goes wrong, it’s the Intel CPU that is a mess.
They try to fix it via the Kernel but that doesn’t work.
And the last year, around the time Ask moved the pool to Packet they decided to use the change the clock-source.
NTP has become a victim of bad tickers because the kernel time-source changes ran into the Intel bug.
At the same time I changed my trusty old Celeron 847 for the J1900 and later the I5, both containing the bug.
From that moment I have been running circles trying to find the cause.
Who would expect that a time-stamper goes lunatic?
Also the monitor responses made things worse by declaring systems offline, but Ask is not to blame, he didn’t know.
I could have known, as my son-in-law complained his i5-4440 was slow and my AMD FX6350 was faster.
But he’s a musician and got into trouble with real-time filters etc, no wonder if the ticker can’t tick right. 
Anyway, the acpi_pm seems to work as should…fingers crossed.