Re: kern/53016: Clock not stable

[coypu%sdf.org@localhost]

The following reply was made to PR kern/53016; it has been noted by GNATS.

From: coypu%sdf.org@localhost
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/53016: Clock not stable
Date: Tue, 6 Mar 2018 18:33:34 +0000

 I have two machines, one that was drifting so badly I could notice it
 without logs to compare, and another that claims a zero drift from NTP.
 
 A difference is that the drifting first machine's dmesg says:
 timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
 ERROR: 4316413966 cycle TSC drift observed
 
 As for this inducing panics, someone mentioned we have some non-ideal
 behaviour if a clock interrupt is missed (something like: we try to
 catch up on missed clock interrupts? I wonder if this blows up with very
 many missed clock interrupts)