From owner-freebsd-acpi@FreeBSD.ORG Mon May 31 21:06:46 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2F5816A4CF for ; Mon, 31 May 2004 21:06:46 -0700 (PDT) Received: from mail.corrupt.co.nz (222-152-28-228.jetstream.xtra.co.nz [222.152.28.228]) by mx1.FreeBSD.org (Postfix) with SMTP id 2AC2B43D3F for ; Mon, 31 May 2004 21:06:45 -0700 (PDT) (envelope-from drew@corrupt.co.nz) Received: (qmail 29670 invoked by uid 1011); 1 Jun 2004 04:06:46 -0000 Received: from drew@corrupt.co.nz by tweety.lan.corrupt.co.nz by uid 1009 with qmail-scanner-1.22 Clear:RC:0(192.100.53.164):SA:0(0.0/3.8):. Processed in 5.321627 secs); 01 Jun 2004 04:06:46 -0000 X-Spam-Status: No, hits=0.0 required=3.8 Received: from 192.100.53.164.dts.net.nz (HELO corrupt.co.nz) (drew@corrupt.co.nz@192.100.53.164) by mail.corrupt.co.nz with SMTP; 1 Jun 2004 04:06:40 -0000 Message-ID: <40BC00AD.6010106@corrupt.co.nz> Date: Tue, 01 Jun 2004 16:06:05 +1200 From: Drew Broadley User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040505 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <20040531213045.6E8BE5D0A@ptavv.es.net> In-Reply-To: <20040531213045.6E8BE5D0A@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: ACPI event testing needed X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 04:06:46 -0000 Kevin Oberman wrote: >>Date: Fri, 28 May 2004 00:38:32 -0700 (PDT) >>From: Nate Lawson >>Sender: owner-freebsd-current@freebsd.org >> >>I've just finished a lot of work on acpi events (GPEs). These drive >>things like the lid switch and device wake capabilities. If your system >>works for suspend/resume, please make sure it still behaves correctly over >>multiple suspend/resume cycles. If you're feeling adventurous, try the >>new wake sysctls: >> >>sysctl dev | grep wake >> >>By setting them to 0 or 1, you can enable/disable a device waking the >>system. Note that non-ACPI devices are still not properly hooked in here >>so they won't work (i.e. sio or modems). But you can change the lid >>independently of the sleep button, for example. >> >>Also, please be sure that your system still powers off correctly when >>shutdown. I may have fixed some systems that didn't power off correctly >>as well. >> >> I did a cvsup and buildworld earlier today and I cannot shutdown -p my machine anymore. It just hangs on "Uptime: xh xm xs". (I used to be able to shutdown -p) I also cannot go into standby, nor suspend/resume. But these were not working prior What extra info do you need ? - Drew