Does anyone hit this on 6.7-current? Martin
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, July 30, 2020 11:18 PM, Martin <martin...@protonmail.com> wrote: > I tried kern.timecounter.hardware=tsc, no effect. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Thursday, July 30, 2020 10:46 PM, Brian Brombacher br...@planetunix.net > wrote: > > > Are you using: kern.timercounter.hardware=tsc ? > > I’m on 6.7 release and no issue with collectd. > > > > > On Jul 30, 2020, at 4:53 PM, Martin martin...@protonmail.com wrote: > > > I can test it on 6.7-current only, and I haven't tested collectd on 6.6 - > > > 6.7 -stable. TSC looks synchronized, ntpd corrects small amount of time > > > skew ~1s or less. > > > VM time looks stable, but not enougth for time-series measurements. > > > Do you know any command to check TSC is "synchronized"? > > > Martin > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > > > > > On Thursday, July 30, 2020 8:40 PM, Chris Cappuccio ch...@nmedia.net > > > > wrote: > > > > Martin [martin...@protonmail.com] wrote: > > > > > > > > > VM using NTP protocol to fine tune clock from the OpenBSD 6.7-current > > > > > host, but collectd complain about clock skew in the past. > > > > > Any ideas? > > > > > > > > Does this happen with 6.6 or 6.7 as well? 6.7-current uses the TSC > > > > directly > > > > to gather timestamps, but it should only do this if the TSC are > > > > "synchronized".
