From owner-freebsd-current@FreeBSD.ORG Fri Apr 16 09:45:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6667516A4CF for ; Fri, 16 Apr 2004 09:45:47 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 0A74843D2F for ; Fri, 16 Apr 2004 09:45:47 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 97978 invoked by uid 1000); 16 Apr 2004 16:45:47 -0000 Date: Fri, 16 Apr 2004 09:45:47 -0700 (PDT) From: Nate Lawson To: Mark Santcroos In-Reply-To: <20040416061250.GA792@laptop.6bone.nl> Message-ID: <20040416094342.W97966@root.org> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040413222717.O80191@root.org><20040414092553.F83452@root.org> <20040415133527.G92275@root.org> <20040416061250.GA792@laptop.6bone.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: Experiences with new PCI code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2004 16:45:47 -0000 On Fri, 16 Apr 2004, Mark Santcroos wrote: > On Thu, Apr 15, 2004 at 01:36:49PM -0700, Nate Lawson wrote: > > So you're saying your system doesn't stay in S3 but immediately wakes up > > even with the latest -current? > > Yes. I had this problem on my second suspend with the new dist and just committed a workaround to disable the new GPE tweaking. However, if you've always had this problem, it's not likely it will fix your issue. > > Try commenting out all callers to acpi_enable_wake*(), including in > > acpi_lid, etc. Perhaps a premature wake event is being triggered. > > Had tried that before, just to be sure, I did it again now. > There are actually only two instances: acpi_lid and acpi_button. > > I disabled the calls to acpi_device_enable_wake_event() from the _suspend() > functions. > > No luck ... You forgot the power and sleep buttons in acpi.c also. Note that killing those means you won't be able to wake via a button. But it would be interesting if your laptop stays asleep. Unmount critical drives before trying this because if you succeed, you'll have to remove the battery to power back on. -Nate