> On Jul 5, 2022, at 23:02, Mohamed Aslan <mas...@sce.carleton.ca> wrote: > > Hi, > > Apologies. My bad, I applied the latest patch but booted into another > kernel with an earlier patch! > > Here's what I got with your latest patch: > > $ dmesg | grep 'tsc' > tsc: cpu0/cpu1: sync test round 1/2 failed > tsc: cpu0/cpu1: cpu0: 40162 lags 5112675666 cycles > tsc: cpu0/cpu2: sync test round 1/2 failed > tsc: cpu0/cpu2: cpu0: 18995 lags 5112675645 cycles > tsc: cpu0/cpu3: sync test round 1/2 failed > tsc: cpu0/cpu3: cpu0: 19136 lags 5112675645 cycles > tsc: cpu0/cpu4: sync test round 1/2 failed > tsc: cpu0/cpu4: cpu0: 19451 lags 5112675645 cycles > tsc: cpu0/cpu5: sync test round 1/2 failed > tsc: cpu0/cpu5: cpu0: 18625 lags 5112675645 cycles > tsc: cpu0/cpu6: sync test round 1/2 failed > tsc: cpu0/cpu6: cpu0: 18208 lags 5112675645 cycles > tsc: cpu0/cpu7: sync test round 1/2 failed > tsc: cpu0/cpu7: cpu0: 17739 lags 5112675645 cycles > > $ sysctl kern.timecounter > kern.timecounter.tick=1 > kern.timecounter.timestepwarnings=0 > kern.timecounter.hardware=i8254 > kern.timecounter.choice=i8254(0) tsc(-1000) acpihpet0(1000) acpitimer0(1000)
This is expected behavior with the patch. cpu0's TSC is way out of sync with every other CPU's TSC, so the TSC is marked as a bad timecounter and a different one is chosen. Are you running the latest BIOS available for your machine?
