From owner-freebsd-mobile Fri Dec 18 14:34:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11358 for freebsd-mobile-outgoing; Fri, 18 Dec 1998 14:34:19 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11351 for ; Fri, 18 Dec 1998 14:34:12 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id PAA28073; Fri, 18 Dec 1998 15:33:49 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA09757; Fri, 18 Dec 1998 15:33:49 -0700 Date: Fri, 18 Dec 1998 15:33:49 -0700 Message-Id: <199812182233.PAA09757@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: mab@alink.net, mobile@FreeBSD.ORG Subject: Re: APM can suspend right after resume without updating clock In-Reply-To: <199812182212.OAA03014@dingo.cdrom.com> References: <86btl1b11n.fsf@zildjian.hq.alink.net> <199812182212.OAA03014@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message