Date: Sun, 27 Jun 2021 03:32:52 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 256781] EC2 Nitro: TSC-low timecounter lags Message-ID: <bug-256781-27103-qchUZ1Qq1K@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256781-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-256781-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256781 --- Comment #8 from martin.stoyanov@vertalo.com --- (In reply to Colin Percival from comment #6) Yes, it is positive, the instance isn't very loaded, and also the same thing happens even if I just let it sit after it starts up. By the time I am able= to ssh in when the instance starts the clock is already too far behind to fetch SSM parameters for example... On the other hand if I use configinit to chan= ge the timecounter to any of the other options, the time is accurate enough. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256781-27103-qchUZ1Qq1K>