Date: Fri, 18 Dec 1998 15:21:48 -0800 From: Mike Smith <mike@smith.net.au> To: Nate Williams <nate@mt.sri.com> Cc: Mike Smith <mike@smith.net.au>, mab@alink.net, mobile@FreeBSD.ORG Subject: Re: APM can suspend right after resume without updating clock Message-ID: <199812182321.PAA03369@dingo.cdrom.com> In-Reply-To: Your message of "Fri, 18 Dec 1998 15:33:49 MST." <199812182233.PAA09757@mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > The code in -current is more complex, but either way it looks as though > > all this is doing is processing the resume event from after the > > low-battery powerdown, ie. when the system was resumed the APM code > > returned the low-battery event *before* the resume event. This is > > really a bug in your BIOS, but we can probably work around it by always > > doing the resume processing when the suspend call returns. > > I don't think is a safe assumption to make. Read the APM docs for more > information. This is the "system may run on after suspend before actually suspending" case? Ok, an alternative then. apm_default_suspend sets a "resume_pending" flag, and won't set suspend_time if that flag is set. Likewise, resumes won't do anything if they're not marked pending. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199812182321.PAA03369>