From owner-freebsd-current@FreeBSD.ORG  Fri Apr 16 00:01:53 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 5CEB316A4CE; Fri, 16 Apr 2004 00:01:53 -0700 (PDT)
Received: from postman.ripe.net (postman.ripe.net [193.0.0.199])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BAA7443D54; Fri, 16 Apr 2004 00:01:52 -0700 (PDT)
	(envelope-from marks@dell-laptop.6bone.nl)
Received: by postman.ripe.net (Postfix, from userid 8)
	id 265048DDB5; Fri, 16 Apr 2004 09:01:52 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id D7BE08DDAB; Fri, 16 Apr 2004 09:01:51 +0200 (CEST)
Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239])
	by birch.ripe.net (8.12.10/8.11.6) with SMTP id i3G71pc4002376;
	Fri, 16 Apr 2004 09:01:51 +0200
Received: (nullmailer pid 812 invoked by uid 1001);
	Fri, 16 Apr 2004 06:12:50 -0000
Date: Fri, 16 Apr 2004 08:12:50 +0200
From: Mark Santcroos <marks@ripe.net>
To: Nate Lawson <nate@root.org>
Message-ID: <20040416061250.GA792@laptop.6bone.nl>
References: <20040414051207.GK58667@pcwin002.win.tue.nl>
	<20040413222717.O80191@root.org> <20040414.001039.116586661.imp@bsdimp.com>
	<20040414092553.F83452@root.org> <20040415135755.GA925@laptop.6bone.nl>
	<20040415133527.G92275@root.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040415133527.G92275@root.org>
User-Agent: Mutt/1.4.2.1i
X-Handles: MS6-6BONE, MS18417-RIPE
X-RIPE-Spam-Level: 
X-RIPE-Spam-Status: U 0.252862 / 0.0 / 0.0 / disabled
X-RIPE-Signature: c3480b852bd58d4c331072819e2f68ef
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Apr 2004 07:01:53 -0000

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.

> 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 ...

Mark