From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 25 09:15:04 2008 Return-Path: Delivered-To: acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B21651065670 for ; Thu, 25 Dec 2008 09:15:04 +0000 (UTC) (envelope-from dynasore@bigfoot.com) Received: from viefep18-int.chello.at (viefep17-int.chello.at [62.179.121.37]) by mx1.freebsd.org (Postfix) with ESMTP id 0128E8FC1F for ; Thu, 25 Dec 2008 09:15:03 +0000 (UTC) (envelope-from dynasore@bigfoot.com) Received: from edge05.upc.biz ([192.168.13.212]) by viefep17-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20081225091501.WJHX13616.viefep17-int.chello.at@edge05.upc.biz>; Thu, 25 Dec 2008 10:15:01 +0100 Received: from [192.168.1.202] ([77.250.255.124]) by edge05.upc.biz with edge id vMF01a03p2hp1p105MF1BD; Thu, 25 Dec 2008 10:15:01 +0100 X-SourceIP: 77.250.255.124 Message-ID: <49534F10.7040305@bigfoot.com> Date: Thu, 25 Dec 2008 10:14:56 +0100 From: David van Kuijk User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Garrett Cooper References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> In-Reply-To: <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi Subject: Re: Problem on AMD64 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: Thu, 25 Dec 2008 09:15:04 -0000 >>>> >>>> Thanks for the responses so far. >>>> >>>> I would be happy with S3. I am however a little confused about the >>>> abilities of my server as reported by sysctl hw.acpi. >>>> >>>> As commented below this line suggests that no other states than S4/S5 >>>> are supported: >>>> hw.acpi.supported_sleep_state: S4 S5 >>>> >>>> But this is also listed: >>>> hw.acpi.standby_state: S1 >>>> hw.acpi.suspend_state: S3 >>>> >>>> Are these last two overridden by the first, meaning that S3 is not >>>> available from my BIOS??? >>> Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because >>> almost all BIOSes support these states. Yours is the first BIOS I have >>> seen that does not do S1. That is really odd. >>> >>> In any case, you have no available ways to cut power when your system is >>> really idle other than powering off. Of course, you may be able to do >>> some power saving with powerd and EST if your BIOS and CPU support those. > > Look into the following sysctls: > > hw.acpi.cpu.cx_lowest > hw.acpi.cpu.cx_highest > I tried to find out what I can do with those sysctls. hw.acpi.cpu.cx_highest is not available on my system. hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I should set it to C2 or C3??? A second question; When I use powerd it switches between clock-frequencies of 1800 and 1000 correctly. Is it possible to set a sysctl so that even lower frequencies are supported, or are the supported frequencies simply dictated by the processors in my server (in my case Opteron 1.8 GHz)? Cheers, David