Date: Fri, 18 Dec 1998 15:29:19 -0700 From: Nate Williams <nate@mt.sri.com> To: mab@alink.net Cc: Mike Smith <mike@smith.net.au>, mobile@FreeBSD.ORG Subject: Re: APM can suspend right after resume without updating clock Message-ID: <199812182229.PAA09703@mt.sri.com> In-Reply-To: <86btl1b11n.fsf@zildjian.hq.alink.net> References: <199812180216.SAA00613@dingo.cdrom.com> <86btl1b11n.fsf@zildjian.hq.alink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> would it be easy to update the clock before suspending? > > MS> Ah, I think I see what you mean; the loss of the resume > MS> message means that the clock hasn't been updated. > > exactly: this isn't just a theory; i verified that my clock was off by > around the amount of the first sleep (many hours); in other words when > it resumed the second time, the clock was set at what it was when i > suspended the first time. xntpd has a hard time recovering from > this. :-) > > MS> Probably a better approach would simply be to reload the > MS> system clock from the RTC. > > as nearly as i can tell, it does: I'll bet the new 'sleep' event is pre-empting the previous 'resume' event and the RTC stuff is getting lost before we have time to adjust the RTC. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812182229.PAA09703>