On 25/10/2022 00:17, Kalabic S. wrote:
On 24/10/2022 21:31, Scott Cheloha wrote:
On Mon, Oct 24, 2022 at 08:26:30AM -0500, Scott Cheloha wrote:
On Sun, Oct 23, 2022 at 02:07:12PM +0200, Kalabic S. wrote:
[...]
machdep.cpuvendor=GenuineIntel
machdep.cpuid=0x306a9
machdep.cpufeature=0x1fbbfbff
machdep.tscfreq=745206414
machdep.invarianttsc=1
And yeah, your TSC frequency is astoundingly high. Way higher than
anything I have ever seen.
Sorry, what I should have said was: that TSC frequency is too *low*
for your machine. I miscounted the number of decimal digits.
To be clear: the measured TSC frequency of 745 MHz seems too low.
There is something probably relevant that I noticed while setting up a
new VM guest to try to compile the kernel as advised.
So, ISO used was a current snapshot (sha256: 29d320ae1a...), and as
always in "VM Options" under "General Options", "Guest OS Version" was
set to "FreeBSD (32-bit)". Issue with clock running forward is again
reproduced.
Being curious what would happen if that same option was set to "FreeBSD
(64-bit)" I tried it and the clock issue is gone!
(but ESXi now shows a warning in web GUI: 'The configured guest OS
(FreeBSD (64-bit)) for this virtual machine does not match the guest
that is currently running (FreeBSD (32-bit)). ...')
Attached are dmesg, sysctl hw and sysctl machdep outputs from this new
VM running with both 32 and 64 bit settings. *Nothing* else was changed,
virtual machine was untouched after installation.
Notable difference is machdep.tscfreq=3392313140 (64-bit) vs 744231460
for 32-bit setting.
Hope this helps for now.
Just noticed hw.sensors.vmt0.timedelta0 and hw.cpuspeed are also
different depending on Guest OS Version option!
For 32-bit option (reproducible clock issue):
hw.sensors.vmt0.timedelta0=738.817611 secs
hw.cpuspeed=744
For 64-bit option (no clock issue):
hw.sensors.vmt0.timedelta0=941.876986 secs
hw.cpuspeed=3392
