[Bug 256781] EC2 Nitro: TSC-low timecounter lags

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781

--- Comment #29 from martin.stoyanov@vertalo.com ---
(In reply to Colin Percival from comment #27)

Setting kvmclock seems to work as expected:

root@freebsd:~ # sysctl kern.timecounter.hardware=kvmclock
kern.timecounter.hardware: TSC-low -> kvmclock
root@freebsd:~ # date
Fri Sep 10 18:07:12 UTC 2021
root@freebsd:~ # sysctl kern.timecounter
kern.timecounter.tsc_shift: 1
kern.timecounter.smp_tsc_adjust: 0
kern.timecounter.smp_tsc: 1
kern.timecounter.invariant_tsc: 1
kern.timecounter.fast_gettime: 1
kern.timecounter.tick: 1
kern.timecounter.choice: i8254(0) ACPI-fast(900) HPET(950) kvmclock(975)
TSC-low(1000) dummy(-1000000)
kern.timecounter.hardware: kvmclock
kern.timecounter.alloweddeviation: 5
kern.timecounter.timehands_count: 2
kern.timecounter.stepwarnings: 0
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.counter: 25411
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.ACPI-fast.quality: 900
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.counter: 5485062
kern.timecounter.tc.ACPI-fast.mask: 16777215
kern.timecounter.tc.HPET.quality: 950
kern.timecounter.tc.HPET.frequency: 62500000
kern.timecounter.tc.HPET.counter: 3218406757
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.kvmclock.quality: 975
kern.timecounter.tc.kvmclock.frequency: 1000000000
kern.timecounter.tc.kvmclock.counter: 2954620152
kern.timecounter.tc.kvmclock.mask: 4294967295
kern.timecounter.tc.TSC-low.quality: 1000
kern.timecounter.tc.TSC-low.frequency: 1100021373
kern.timecounter.tc.TSC-low.counter: 2772787131
kern.timecounter.tc.TSC-low.mask: 4294967295
root@freebsd:~ # date
Fri Sep 10 18:08:06 UTC 2021

However I am not able to reproduce the original issue with this instance -
TSC-low seems to be working fine as well...

Please let me know if you need anything else or if I can run more tests...

-- 
You are receiving this mail because:
You are the assignee for the bug.