From owner-freebsd-acpi@FreeBSD.ORG Mon May 23 17:35:46 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 EA2C316A41C for ; Mon, 23 May 2005 17:35:46 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id A37C643D48 for ; Mon, 23 May 2005 17:35:46 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j4NHZkvl028124; Mon, 23 May 2005 13:35:46 -0400 Message-ID: <42921446.2000405@root.org> Date: Mon, 23 May 2005 10:35:02 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050416) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Ducrot References: <1116811842.671.22.camel@RabbitsDen> <20050523103252.GX21800@poupinou.org> In-Reply-To: <20050523103252.GX21800@poupinou.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: S3 state handled in BIOS? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2005 17:35:47 -0000 Bruno Ducrot wrote: > On Sun, May 22, 2005 at 09:30:42PM -0400, Alexandre Sunny Kovalenko wrote: > >>Good people, >> >>after much pocking around my laptop (Averatec >>3150H), /usr/src/sys/i386/acpica/acpi_wakeup.c >>and /usr/src/sys/contrib/dev/acpica/hwsleep.c, I came to conclusion that >>S3 state in my case causes BIOS to suspend machine at the point when >>SLP_TYP and SLP_EN are set and resume it from that same point, >>completely ignoring wakeup vector. >> >>This would cause FreeBSD to hit infinite loop in acpi_sleep_machdep >>(acpi_wakeup.c) and never come back. Replacing that loop with >>AcpiOsSleep(5000) lets system resume properly. >> >>This kind of sleep (pseudo S3?) about doubles battery life, which is not >>much to write home about, but matches what Windows does on the same >>hardware, so, I guess, it is best I am going to get. >> >>Question that I have to the list is whether somebody who knows ACPI >>thinks that it is common enough situation to warrant tunable along the >>lines of 'hw.acpi.s3bios', which would eliminate infinite loop if set? >> >>I have unconditionally eliminated the loop for now and have been testing >>it here for awhile without any bad side effects. >> >>If your system appears to hang after resume from S3 while turning power >>on, you might want to try attached very simplistic patch. >> > > > I think your machine actually perform S1, not S3, likely because the > values associated to _S3 (a package in the asl) are for _S1. In that case, it would be interesting to see the acpidump -t -d and compare values for the _S1 and _S3 nodes. -- Nate