From owner-freebsd-current Fri Aug 6 23:41: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2768114E6C for ; Fri, 6 Aug 1999 23:40:58 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04186; Sat, 7 Aug 1999 00:40:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA07992; Sat, 7 Aug 1999 00:40:39 -0600 (MDT) Message-Id: <199908070640.AAA07992@harmony.village.org> To: Eric Hodel Subject: Re: recent apm changes Cc: Peter Mutsaers , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 05 Aug 1999 13:55:15 PDT." <37A9FA33.426D35FC@seattleu.edu> References: <37A9FA33.426D35FC@seattleu.edu> <87n1w6hk62.fsf@muon.xs4all.nl> Date: Sat, 07 Aug 1999 00:40:38 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37A9FA33.426D35FC@seattleu.edu> Eric Hodel writes: : I've got a -current machine (no cvsups in a few months) that wakes up : immediately after suspending. (sleeps 0 seconds) Hmmm, some laptops will wakeup on a keyboard interrupt. The interrupt that is waking you up may be the key up from the return you hit to make the event happen. PAO has a small sleep in the apm driver, while -current didn't the last time I looked. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message