https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #25 from Colin Percival ---
Martin: Can you try the latest 14-CURRENT AMI, and confirm that setting
kern.timecounter.hardware=kvmclock fixes it?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #26 from martin.stoya...@vertalo.com ---
(In reply to Colin Percival from comment #25)
You mean ami-0c69868f578f6cc8a with this description - "FreeBSD/amd64
main@58a7bf124cc"?(In reply to Colin Percival from comment #25)
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #27 from Colin Percival ---
Yep, that's the one.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #28 from martin.stoya...@vertalo.com ---
Created attachment 227814
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=227814&action=edit
dmesg.boot - 14.0-CURRENT
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #29 from martin.stoya...@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 ->
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #30 from Colin Percival ---
(In reply to martin.stoyanov from comment #29)
Thanks for testing -- indeed, reproducing the original issue seems difficult (I
was never able to reproduce it myself). But my contacts at Amazon say th
