From owner-freebsd-acpi@FreeBSD.ORG Mon May 23 10:36:03 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 49C1116A41C for ; Mon, 23 May 2005 10:36:03 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2AF143D1D for ; Mon, 23 May 2005 10:36:02 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1DaAEu-0004gh-00; Mon, 23 May 2005 12:32:52 +0200 Date: Mon, 23 May 2005 12:32:52 +0200 To: Alexandre Sunny Kovalenko Message-ID: <20050523103252.GX21800@poupinou.org> References: <1116811842.671.22.camel@RabbitsDen> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1116811842.671.22.camel@RabbitsDen> User-Agent: Mutt/1.5.6+20040907i From: Bruno Ducrot 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 10:36:03 -0000 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. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.