[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/53016: Clock not stable
The following reply was made to PR kern/53016; it has been noted by GNATS.
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)
Main Index |
Thread Index |