Clock not ticking during S3

Alexey Dokuchaev danfe at FreeBSD.org
Tue Oct 1 18:38:15 UTC 2013


On Tue, Oct 01, 2013 at 01:12:38PM +0200, Dominic Fandrey wrote:
> The system is sent to S3 at this point and woken 4 days later.
> 
> This is how it comes up:
> 
> 27 Sep 23:07:03 ntpd[3045]: no servers reachable
> 27 Sep 23:19:54 ntpd[3045]: synchronized to 83.170.1.225, stratum 2
> 27 Sep 23:19:54 ntpd[3045]: time correction of 306709 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
> 
> Roughly 3 and a half days of time missing. I've never seen anything like
> it before.
> 
> This is my system.
> FreeBSD [...] 9.2-PRERELEASE FreeBSD [...] amd64

Not sure about amd64, but at least on i386, "device pmtimer" is required
to be in kernel config for timekeeping while sleeping.

./danfe


More information about the freebsd-stable mailing list