From owner-cvs-src@FreeBSD.ORG Mon Sep 19 23:28:39 2005 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BC5A16A41F; Mon, 19 Sep 2005 23:28:39 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8C0143D45; Mon, 19 Sep 2005 23:28:38 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j8JNSNo5031686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Sep 2005 16:28:26 -0700 Message-ID: <432F4990.9060007@root.org> Date: Mon, 19 Sep 2005 16:28:16 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200509111928.j8BJSWci066427@repoman.freebsd.org> <70e8236f0509180715406f1f31@mail.gmail.com> <432D9F4B.9080902@root.org> <20050918.134518.31977329.imp@bsdimp.com> In-Reply-To: <20050918.134518.31977329.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@freebsd.org, joao.barros@gmail.com, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/pci pci.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2005 23:28:39 -0000 M. Warner Losh wrote: > In message: <432D9F4B.9080902@root.org> > Nate Lawson writes: > : Joao Barros wrote: > : > I was reading the Release Notes for 6.0 on > : > http://www.freebsd.org/relnotes/6-STABLE/relnotes/i386/article.html > : > and noticed: > : > > : > 2.2.2 Hardware Support > : > > : > The acpi(4) driver now turns the ACPI and PCI devices off or to a > : > lower power state when suspending, and back on again when resuming. > : > This behavior can be disabled by setting the debug.acpi.do_powerstate > : > and hw.pci.do_powerstate sysctls to 0. > : > > : > Given this is the same tunable you changed back to 0 by default, does > : > that "when resuming" has anything to do with this last commit? If so, > : > it could still be mentioned the other way around, allowing people > : > wanting to, to enable the tunable :) > : > : You bring up a different point also, which is that ACPI should probably > : be set to match this same default for release. > > Actually, all that the do_powerstate stuff in pci land does is turn > off the devices when no driver is attached. We always turn them back > on on resume. That's not how the acpi powerstate support works. It turns off devices not allowed in a given Sx state while suspending and turns them on again in resume. For instance, if _S3D says a given device must be in D1 while we sleep in S3, we power down that device to D1 in the suspend path and back up to D0 (running) in the resume path. I haven't heard of any problems, but for consistency I was asking if this should be disabled also in the release. -- Nate