Bug 244705
| Summary: | /usr/src/sys/x86/x86/tsc.c: System Clock is 0.3% slow since r352684 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Theron Tarigo <theron.tarigo> | ||||
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
| Status: | Closed Feedback Timeout | ||||||
| Severity: | Affects Only Me | CC: | markj, raf, theron.tarigo, val | ||||
| Priority: | --- | Keywords: | regression | ||||
| Version: | CURRENT | ||||||
| Hardware: | amd64 | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
On my Ryzen system, r352684 (or something.. but nothing else TSC related happened recently) caused the TSC to go completely nuts, time is quickly becoming off by many minutes, I looked at the clock yesterday and it was 3 hours behind :D kern.timecounter.hardware=HPET seems to be better (-14 sec desync from NTP in an hour without an NTP daemon, that's not crazy and should be manageable by NTP) Does the problem persist after r359997? Please re-open if the problem indeed persists on head after r359997. |
Created attachment 212294 [details] reverts the breaking change After switching from 12.1-RELEASE to CURRENT I noticed audio driver appeared to be consuming samples too fast by about 0.3%. However after verifying audio devices are working properly I discovered that system clock is actually slow by 0.3% (confirmed by using ntpdate to compare with time server). This is not a hardware fault since I can reliably get correct clock by booting 12.1-RELEASE or CURRENT r352683 but slow clock with CURRENT since r352684 unless reverting that change. hw.model: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz.