From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 21 01:22:51 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 A005F106564A for ; Sun, 21 Dec 2008 01:22:51 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 745D98FC19 for ; Sun, 21 Dec 2008 01:22:51 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2902460rvf.43 for ; Sat, 20 Dec 2008 17:22:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Bpq8uJ/mc4+ZbkrzPSErucgxOuSie8Gnn4oFeza+Sdk=; b=RZeWJoruKVd7o3YQYduitdAsbLJzn0uMOF9mEg+7B9rEC5t323mhLI8DEuL7HZuSwf zwExARlhFqJEPl9d2aTCPGrGEo6uvYxKssI5ROuqAHmX2L908U42cFcM1GROjJ4GKwHS BfKRhW3HdjdPzsVavv0MbvURXwcAZh2TX9Uuo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=pM2czxfOSyjPLj9NmdgATcu3ohTnpRVrxpQIajbiHregmf6eJRvrmT8YgTAW8D6YcD dWNtqGCMnf9U6NqtAhmXUTevqJmakfOa4Z7U3usETsLEVoFf8nb50uRhXuQDm5kXBNZW mqUXOMw4h0WXLm/hkk7Eed1+7QYUaom85B9Vg= Received: by 10.140.166.21 with SMTP id o21mr2438699rve.14.1229822570090; Sat, 20 Dec 2008 17:22:50 -0800 (PST) Received: by 10.140.135.2 with HTTP; Sat, 20 Dec 2008 17:22:50 -0800 (PST) Message-ID: <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> Date: Sat, 20 Dec 2008 17:22:50 -0800 From: "Garrett Cooper" To: "Nate Lawson" In-Reply-To: <494D50F6.70303@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <494C22EA.5010408@bigfoot.com> <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> <494D50F6.70303@root.org> Cc: acpi@freebsd.org 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: Sun, 21 Dec 2008 01:22:51 -0000 Err... yes, that indeed would be a problem ><. I didn't realize he was looking for S4 (I thought he was looking for S2, S3). -Garrett On 12/20/08, Nate Lawson wrote: > Garrett Cooper wrote: >> On 12/19/08, David van Kuijk wrote: >>> I try to put my machine in sleep state but get the message that this is >>> not supported. >>> >>> command and result: >>> $ acpiconf -s 4 >>> acpiconf: request sleep type (4) failed: Operation not supported >>> >>> I get the same message for other sleep states 1,2,3. >>> >>> My machine is a HP Proliant ML115 AMD64 running FreeBSD 7.0-RELEASE >>> >>> Result from sysctl hw.acpi is >>> hw.acpi.supported_sleep_state: S4 S5 > > Only S4 (suspend to disk) or S5 (power off) are supported by your BIOS. > >>> Anyone suggestions to a solution or is this a bug? >> >> ACPI support doesn't work on mainline FreeBSD. There is a testing >> patch available via this thread though: >> >> http://www.mavetju.org/mail/view_message.php?list=freebsd-acpi&id=2850196 > > The patch won't help fix this. Someone needs to implement > suspend-to-disk since we don't yet support it. It's a pretty big project. > > -- > Nate > From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 21 04:36:39 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 718EC1065676 for ; Sun, 21 Dec 2008 04:36:39 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 2C3808FC18 for ; Sun, 21 Dec 2008 04:36:38 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.21.166] (helo=devil.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LEFTe-0001iI-DG; Sun, 21 Dec 2008 11:59:38 +0800 Message-ID: <494DBF33.7040301@micom.mng.net> Date: Sun, 21 Dec 2008 11:59:47 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.17 (X11/20081020) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org, njl@freebsd.org X-Enigmail-Version: 0.95.7 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: ACPI error, No pointer back to NS node in buffer obj 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: Sun, 21 Dec 2008 04:36:39 -0000 Hi, These messages are appearing on CURRENT. ... cpu0: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0x854857c0 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0x85477c00 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL est1: on cpu1 ... Are above messages harmful? Additional infos at: http://people.freebsd.org/~ganbold/acpi.txt thanks, Ganbold -- Being popular is important. Otherwise people might not like you. From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 21 21:50:09 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 DD4461065670 for ; Sun, 21 Dec 2008 21:50:09 +0000 (UTC) (envelope-from dynasore@bigfoot.com) Received: from viefep18-int.chello.at (viefep33-int.chello.at [62.179.121.51]) by mx1.freebsd.org (Postfix) with ESMTP id 2B0458FC17 for ; Sun, 21 Dec 2008 21:50:08 +0000 (UTC) (envelope-from dynasore@bigfoot.com) Received: from edge04.upc.biz ([192.168.13.239]) by viefep15-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20081221213106.FUCJ1325.viefep15-int.chello.at@edge04.upc.biz>; Sun, 21 Dec 2008 22:31:06 +0100 Received: from [192.168.1.201] ([77.250.255.124]) by edge04.upc.biz with edge id txX41a02G2hp1p104xX564; Sun, 21 Dec 2008 22:31:06 +0100 X-SourceIP: 77.250.255.124 Message-ID: <494EB598.4020708@bigfoot.com> Date: Sun, 21 Dec 2008 22:31:04 +0100 From: David van Kuijk User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Garrett Cooper References: <494C22EA.5010408@bigfoot.com> <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> <494D50F6.70303@root.org> <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> In-Reply-To: <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org 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: Sun, 21 Dec 2008 21:50:09 -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??? David Garrett Cooper wrote: > Err... yes, that indeed would be a problem ><. I didn't realize he was > looking for S4 (I thought he was looking for S2, S3). > -Garrett > > On 12/20/08, Nate Lawson wrote: >> Garrett Cooper wrote: >>> On 12/19/08, David van Kuijk wrote: >>>> I try to put my machine in sleep state but get the message that this is >>>> not supported. >>>> >>>> command and result: >>>> $ acpiconf -s 4 >>>> acpiconf: request sleep type (4) failed: Operation not supported >>>> >>>> I get the same message for other sleep states 1,2,3. >>>> >>>> My machine is a HP Proliant ML115 AMD64 running FreeBSD 7.0-RELEASE >>>> >>>> Result from sysctl hw.acpi is >>>> hw.acpi.supported_sleep_state: S4 S5 >> Only S4 (suspend to disk) or S5 (power off) are supported by your BIOS. >> >>>> Anyone suggestions to a solution or is this a bug? >>> ACPI support doesn't work on mainline FreeBSD. There is a testing >>> patch available via this thread though: >>> >>> http://www.mavetju.org/mail/view_message.php?list=freebsd-acpi&id=2850196 >> The patch won't help fix this. Someone needs to implement >> suspend-to-disk since we don't yet support it. It's a pretty big project. >> >> -- >> Nate >> > From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 21 23:49:15 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 10B1E106567D for ; Sun, 21 Dec 2008 23:49:15 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.freebsd.org (Postfix) with ESMTP id DE5888FC17 for ; Sun, 21 Dec 2008 23:49:14 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net by postal1.es.net (Postal Node 1) with ESMTP (SSL) id BJH27122; Sun, 21 Dec 2008 15:38:22 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 7E92545020; Sun, 21 Dec 2008 15:38:22 -0800 (PST) To: David van Kuijk In-Reply-To: Your message of "Sun, 21 Dec 2008 22:31:04 +0100." <494EB598.4020708@bigfoot.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1229902702_55132P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 21 Dec 2008 15:38:22 -0800 From: "Kevin Oberman" Message-Id: <20081221233822.7E92545020@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;;; X-Sender: X-To_Name: David van Kuijk X-To_Domain: bigfoot.com X-To: David van Kuijk X-To_Email: dynasore@bigfoot.com X-To_Alias: dynasore Cc: acpi@freebsd.org 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: Sun, 21 Dec 2008 23:49:15 -0000 --==_Exmh_1229902702_55132P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Sun, 21 Dec 2008 22:31:04 +0100 > From: David van Kuijk > Sender: owner-freebsd-acpi@freebsd.org > > 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. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1229902702_55132P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFJTtNukn3rs5h7N1ERAqSlAJ4pvXcJCJAlFmiMhDvLiQTOkdXy6ACfRgpy zaHspvD2s473ArteB03whoE= =Fi7y -----END PGP SIGNATURE----- --==_Exmh_1229902702_55132P-- From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 21 23:52:40 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 57763106564A for ; Sun, 21 Dec 2008 23:52:40 +0000 (UTC) (envelope-from nate@root.org) Received: from nlpi025.prodigy.net (nlpi025.sbcis.sbc.com [207.115.36.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2AE638FC17 for ; Sun, 21 Dec 2008 23:52:39 +0000 (UTC) (envelope-from nate@root.org) Received: from [10.0.5.18] (ppp-71-139-14-199.dsl.snfc21.pacbell.net [71.139.14.199]) (authenticated bits=0) by nlpi025.prodigy.net (8.13.8 smtpauth/dk/map_regex/8.13.8) with ESMTP id mBLNkHgp017797; Sun, 21 Dec 2008 17:46:18 -0600 Message-ID: <494ED54B.2060508@root.org> Date: Sun, 21 Dec 2008 15:46:19 -0800 From: Nate Lawson User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: David van Kuijk References: <494C22EA.5010408@bigfoot.com> <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> <494D50F6.70303@root.org> <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> <494EB598.4020708@bigfoot.com> In-Reply-To: <494EB598.4020708@bigfoot.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org 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: Sun, 21 Dec 2008 23:52:40 -0000 David van Kuijk wrote: > 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??? Those are just the defaults for standby and suspend, respectively. Your BIOS only supports S4 (as is common for a lot of desktops). -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 22 11:06:46 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6D021065675 for ; Mon, 22 Dec 2008 11:06:46 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 946D78FC16 for ; Mon, 22 Dec 2008 11:06:46 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mBMB6k7r060473 for ; Mon, 22 Dec 2008 11:06:46 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mBMB6k9R060469 for freebsd-acpi@FreeBSD.org; Mon, 22 Dec 2008 11:06:46 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Dec 2008 11:06:46 GMT Message-Id: <200812221106.mBMB6k9R060469@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org 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, 22 Dec 2008 11:06:46 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [ACPI] sleep broken on IBM/Lenovo T61 [amd64] o kern/128639 acpi [PATCH] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 45 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 22 13:24:43 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 857EE1065690 for ; Mon, 22 Dec 2008 13:24:43 +0000 (UTC) (envelope-from bekktekk@techno01.bek.jp) Received: from techno01.bek.jp (techno01.bek.jp [202.210.130.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5EBBB8FC08 for ; Mon, 22 Dec 2008 13:24:43 +0000 (UTC) (envelope-from bekktekk@techno01.bek.jp) Received: by techno01.bek.jp (Postfix, from userid 1001) id 503634507F; Mon, 22 Dec 2008 21:37:04 +0900 (JST) To: freebsd-acpi@freebsd.org From: received@postcard.org Message-Id: <20081222123704.503634507F@techno01.bek.jp> Date: Mon, 22 Dec 2008 21:37:04 +0900 (JST) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: You have just received a virtual postcard from a friend ! 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, 22 Dec 2008 13:24:43 -0000 You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http://www.loaps.com/postcard.gif.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://www.loaps.com/postcard.gif.exe From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 22 16:27:08 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C6FD1065670 for ; Mon, 22 Dec 2008 16:27:08 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 8FD188FC13 for ; Mon, 22 Dec 2008 16:27:07 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so304880nfh.33 for ; Mon, 22 Dec 2008 08:27:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=LlkWELlOMADSQWz763trt6ymu6ogY4Fg2eMMVAImLKc=; b=SVCGCTChGP0Yfgm2F/z5+JjtE5DkMYaRJSjvc32HogJBmmlYI4/Kh/pmqLJXD7g2Ih 791WvO5+a6RJzCE6EGl+SK0WxVIAwRLcCymKfweEe9pf13fTSp7yr0arTLCBBbJsA/DA IQP/1hBkRot0uWfxbOJNlWZ1bXCfl/xdxb5GA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=S9Q73WzTb0UEMKDjS8y/zs+TByMp5NZRqgGyJK1wM6i6MSJS8Lgl6IKfg4iSNYq8Wp Y/oO5jRx2ZCkFi2DUM8VMvtTkKGGfueQgdqI+3xBNt0C0T8U+OMsZ16C/ahkfS1hSB08 iMJ6QvAtytLUuy9AILEUnIgW3NpevcgmgKBDw= Received: by 10.210.10.1 with SMTP id 1mr199096ebj.163.1229963226260; Mon, 22 Dec 2008 08:27:06 -0800 (PST) Received: from ?192.168.2.101? ([92.50.244.160]) by mx.google.com with ESMTPS id 7sm1339839eyg.42.2008.12.22.08.27.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 22 Dec 2008 08:27:05 -0800 (PST) From: Dmitry Kolosov To: freebsd-acpi@freebsd.org Date: Mon, 22 Dec 2008 19:27:00 +0300 User-Agent: KMail/1.9.10 References: <20081221233822.7E92545020@ptavv.es.net> In-Reply-To: <20081221233822.7E92545020@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812221927.00568.ivakras1@gmail.com> 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: Mon, 22 Dec 2008 16:27:08 -0000 On Monday 22 December 2008 02:38:22 Kevin Oberman wrote: > > Date: Sun, 21 Dec 2008 22:31:04 +0100 > > From: David van Kuijk > > Sender: owner-freebsd-acpi@freebsd.org > > > > 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. Could you give to us some links about powersaving with EST? For now, i'm using powerd: powerd_enable="YES" powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal in both cases and something about 50 minutes, so i think powerd is not so powerfull for me. From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 22 17:49:33 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AB1A1065676 for ; Mon, 22 Dec 2008 17:49:33 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.freebsd.org (Postfix) with ESMTP id 3F2BC8FC19 for ; Mon, 22 Dec 2008 17:49:33 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net by postal1.es.net (Postal Node 1) with ESMTP (SSL) id CDT74732; Mon, 22 Dec 2008 09:49:32 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 93BC44500F; Mon, 22 Dec 2008 09:49:32 -0800 (PST) To: Dmitry Kolosov In-Reply-To: Your message of "Mon, 22 Dec 2008 19:27:00 +0300." <200812221927.00568.ivakras1@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1229968172_95967P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 22 Dec 2008 09:49:32 -0800 From: "Kevin Oberman" Message-Id: <20081222174932.93BC44500F@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: Dmitry Kolosov X-To_Domain: gmail.com X-To: Dmitry Kolosov X-To_Email: ivakras1@gmail.com X-To_Alias: ivakras1 Cc: freebsd-acpi@freebsd.org 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: Mon, 22 Dec 2008 17:49:33 -0000 --==_Exmh_1229968172_95967P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: Dmitry Kolosov > Date: Mon, 22 Dec 2008 19:27:00 +0300 > Sender: owner-freebsd-acpi@freebsd.org > > On Monday 22 December 2008 02:38:22 Kevin Oberman wrote: > > > Date: Sun, 21 Dec 2008 22:31:04 +0100 > > > From: David van Kuijk > > > Sender: owner-freebsd-acpi@freebsd.org > > > > > > 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. > > Could you give to us some links about powersaving with EST? For now, > i'm using > powerd: > powerd_enable="YES" > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me > (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal > in both cases and something about 50 minutes, so i think powerd is not > so powerfull for me. I thought that this was a desktop, so I assumed it was always on AC. Sorry. One things that can help is "deep sleep" using the Cx states in ACPI. Unfortunately, USB will prevent these from being effective. Work is underway to fix this in HEAD with the new USB stack, so this may take care of itself in time. Until then, I build my kernel without USB support and load it at boot time when I know I'll be needing it. (Interrupt the boot and drop to the loader prompt and "load umass" or whatever USB device(s) you might need. This can be a really big win for an idle or near idle system. I'd supply some added hints for power tuning, but I am running on my cell phone modem and I can only use it with Windows, so I can't look at my tuning parameters on FreeBSD right now. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1229968172_95967P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFJT9Mskn3rs5h7N1ERAv2CAJsHym0EAlMG3tQdf4C9AWa4Y0dvCQCePkA0 +1ErU4fREM3KkhPJRzWGerU= =+2y+ -----END PGP SIGNATURE----- --==_Exmh_1229968172_95967P-- From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 22 19:45:57 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36E67106564A for ; Mon, 22 Dec 2008 19:45:57 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id B206C8FC1B for ; Mon, 22 Dec 2008 19:45:56 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 230357514; Mon, 22 Dec 2008 21:45:55 +0200 Message-ID: <494FEE73.906@FreeBSD.org> Date: Mon, 22 Dec 2008 21:45:55 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.17 (X11/20081029) MIME-Version: 1.0 To: Dmitry Kolosov References: <20081221233822.7E92545020@ptavv.es.net> <1229973789.00051301.1229963402@10.7.7.3> In-Reply-To: <1229973789.00051301.1229963402@10.7.7.3> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org 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: Mon, 22 Dec 2008 19:45:57 -0000 Dmitry Kolosov wrote: > Could you give to us some links about powersaving with EST? For now, i'm using > powerd: > powerd_enable="YES" > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me (125 MHz > on battery and 2.16GHz on AC), BUT battery life time is equal in both cases and > something about 50 minutes, so i think powerd is not so powerfull for me. powerd uses any frequency control features provided by kernel. On P4 and above kernel may provide both EST and P4TCC frequencies. You can see them by `sysctl -a | grep freq`. P4TCC usually gives very small power benefit on idle CPU. I have seen benefit only on old P4 without or later with disabled C1E mode support. For CPUs with C1E support P4TCC is not effective as CPU anyway completely disables it's frequency on C1 state (HALT instruction). EST instead is much more effective as it also controls CPU voltage. Check your boot messages and sysctls for EST support. -- Alexander Motin From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 22 21:03:13 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 2E40C1065675 for ; Mon, 22 Dec 2008 21:03:13 +0000 (UTC) (envelope-from dynasore@bigfoot.com) Received: from viefep18-int.chello.at (viefep16-int.chello.at [62.179.121.36]) by mx1.freebsd.org (Postfix) with ESMTP id 589F98FC0C for ; Mon, 22 Dec 2008 21:03:11 +0000 (UTC) (envelope-from dynasore@bigfoot.com) Received: from edge01.upc.biz ([192.168.13.236]) by viefep16-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20081222210310.FDVS1339.viefep16-int.chello.at@edge01.upc.biz>; Mon, 22 Dec 2008 22:03:10 +0100 Received: from [192.168.1.201] ([77.250.255.124]) by edge01.upc.biz with edge id uM361a01a2hp1p101M37FH; Mon, 22 Dec 2008 22:03:10 +0100 X-SourceIP: 77.250.255.124 Message-ID: <49500088.2080609@bigfoot.com> Date: Mon, 22 Dec 2008 22:03:04 +0100 From: David van Kuijk User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Kevin Oberman References: <20081221233822.7E92545020@ptavv.es.net> In-Reply-To: <20081221233822.7E92545020@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org 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: Mon, 22 Dec 2008 21:03:13 -0000 OK, thanks again. I didn't know those tools. est is not supported om AMD64, but I will start experimenting with powerd. The main thing I want to accomplish is to lower my energy bill after I found out my server is costing me 50 cents a day of electricity. So any other ideas (besides powering off ;-) are welcome... Regards, David Kevin Oberman wrote: >> Date: Sun, 21 Dec 2008 22:31:04 +0100 >> From: David van Kuijk >> Sender: owner-freebsd-acpi@freebsd.org >> >> 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. From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 22 21:15:52 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 0DF431065673 for ; Mon, 22 Dec 2008 21:15:52 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id D34A58FC1A for ; Mon, 22 Dec 2008 21:15:51 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by rv-out-0506.google.com with SMTP id f9so3200302rvb.5 for ; Mon, 22 Dec 2008 13:15:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=MJvXEf9axgdin5OEGFXUsl7lbd8hzprBaCpms90xEIo=; b=wDiLCURzheShmqc6A4wsw0/hJPV4OECOp8mTIa7j7nkOej4OkLi/f3M7O1XsSHIhmh 77TuMFLMvCJduUt0BKAaLXH2hA6o4krf8YiWknhZXGFkApd1BwQEXFRvZLK9HDLolbuu fyXB4tPkSR692epolxcI5ZvilZ31qjdurKyRc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=boZvlrF7ASp6SUQSOR+L2HiivUovx87NtksCwmcxxKS9pGjcIDexiY6f+7WPcM+XoK GDSfKx40QMrWZMvL9M2ecoefUc53A8qErukEDOsMlsTvth8n5AeMYtrsCuKE3KLQsOOI oVnsp3sEV6QLjlk8O23uMR4pNF9EqqpNVW8dA= Received: by 10.141.97.5 with SMTP id z5mr3348588rvl.269.1229980551514; Mon, 22 Dec 2008 13:15:51 -0800 (PST) Received: by 10.140.135.2 with HTTP; Mon, 22 Dec 2008 13:15:51 -0800 (PST) Message-ID: <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> Date: Mon, 22 Dec 2008 13:15:51 -0800 From: "Garrett Cooper" To: "David van Kuijk" In-Reply-To: <49500088.2080609@bigfoot.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> 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: Mon, 22 Dec 2008 21:15:52 -0000 On 12/22/08, David van Kuijk wrote: > OK, thanks again. I didn't know those tools. est is not supported om > AMD64, but I will start experimenting with powerd. > > The main thing I want to accomplish is to lower my energy bill after I > found out my server is costing me 50 cents a day of electricity. So any > other ideas (besides powering off ;-) are welcome... > > Regards, > David > > Kevin Oberman wrote: >>> Date: Sun, 21 Dec 2008 22:31:04 +0100 >>> From: David van Kuijk >>> Sender: owner-freebsd-acpi@freebsd.org >>> >>> 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 Unfortunately [for you] est and PT4CC are completely Intel specific power regulation interfaces. AMD had something to offer on Linux, but I forget what that was... Cheers, -Garrett From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 23 03:40:53 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6E031065670 for ; Tue, 23 Dec 2008 03:40:53 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 385288FC08 for ; Tue, 23 Dec 2008 03:40:52 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id mBN3eoZV046122; Tue, 23 Dec 2008 14:40:51 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 23 Dec 2008 14:40:50 +1100 (EST) From: Ian Smith To: Dmitry Kolosov In-Reply-To: <200812221927.00568.ivakras1@gmail.com> Message-ID: <20081223140958.I29108@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <200812221927.00568.ivakras1@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org 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: Tue, 23 Dec 2008 03:40:53 -0000 On Mon, 22 Dec 2008, Dmitry Kolosov wrote: [..] > Could you give to us some links about powersaving with EST? For now, i'm using > powerd: > powerd_enable="YES" > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me (125 MHz > on battery and 2.16GHz on AC), BUT battery life time is equal in both cases and > something about 50 minutes, so i think powerd is not so powerfull for me. -i percent Specifies the CPU idle percent level when adaptive mode should begin to degrade performance to save power. The default is 90% or higher. -r percent Specifies the CPU idle percent level where adaptive mode should consider the CPU running and increase performance. The default is 65% or lower. I don't think your powerd running and idle percentages are likely to work too well; too close together, and too close to the 'busy' end. Try stopping powerd (/etc/rc.d/powerd stop) then running powerd manually in verbose mode in its own console (powerd -v [flags]) to watch how it behaves under varying loads. I suspect that you will find it 'flapping' between some frequencies too often at constant load, as there's insufficient hysteresis between the idle/running marks. Compare it with using the default -i and -r and if those aren't suitable, try rather smaller variations from the defaults. If it lacks responsiveness, try decreasing the polling interval. cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 23 16:43:02 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EF041065673 for ; Tue, 23 Dec 2008 16:43:02 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id DF5288FC1F for ; Tue, 23 Dec 2008 16:43:01 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so685709ugs.39 for ; Tue, 23 Dec 2008 08:43:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=tRaxj/Gp/2V2kmmx2tDzMp9ffirHw1Hi+L0Di4KTUao=; b=sf/6taxMkC1vArCywOFXe3mL/AOJzKNcUGBQ6ihPMjWx9K4OEnim+19Ff+8BoWOSjH r9yGghA1iSbZvXbEeVRETMb4Hab/2L+eiTJkz1DEZSgWQFpU9hzSXugZFE9crdnF/3dw N4FYaxwO/Va7cnB+n29kPKMCpTQbzctGS2plM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=hODpT+X9gNqrUP587cAQ7xKsGZX6my8T23OQwmiKCXH7blS+5Q/sMdmza/FGPBdLas 1PFRTfzAopewPFoZT7CyXOgF6K9awo492neOB2uV4UEOPeB0BQlJRA8tnwAyb1oLynGx kpabjG33bztWtoEwwgOnHE9FUNhufoiXjBX6g= Received: by 10.67.115.15 with SMTP id s15mr6903137ugm.56.1230050580368; Tue, 23 Dec 2008 08:43:00 -0800 (PST) Received: from ?192.168.2.101? ([92.50.244.160]) by mx.google.com with ESMTPS id j4sm8870729ugf.16.2008.12.23.08.41.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 23 Dec 2008 08:41:19 -0800 (PST) From: Dmitry Kolosov To: freebsd-acpi@freebsd.org Date: Tue, 23 Dec 2008 19:41:11 +0300 User-Agent: KMail/1.9.10 References: <20081221233822.7E92545020@ptavv.es.net> <200812221927.00568.ivakras1@gmail.com> <20081223140958.I29108@sola.nimnet.asn.au> In-Reply-To: <20081223140958.I29108@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812231941.11998.ivakras1@gmail.com> 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: Tue, 23 Dec 2008 16:43:02 -0000 On Tuesday 23 December 2008 06:40:50 Ian Smith wrote: > On Mon, 22 Dec 2008, Dmitry Kolosov wrote: > [..] > > > Could you give to us some links about powersaving with EST? For now, i'm > > using powerd: > > powerd_enable="YES" > > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me > > (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal > > in both cases and something about 50 minutes, so i think powerd is not > > so powerfull for me. > > -i percent Specifies the CPU idle percent level when adaptive mode > should begin to degrade performance to save power. The > default is 90% or higher. > > -r percent Specifies the CPU idle percent level where adaptive mode > should consider the CPU running and increase performance. > The default is 65% or lower. > > I don't think your powerd running and idle percentages are likely to > work too well; too close together, and too close to the 'busy' end. > > Try stopping powerd (/etc/rc.d/powerd stop) then running powerd manually > in verbose mode in its own console (powerd -v [flags]) to watch how it > behaves under varying loads. > > I suspect that you will find it 'flapping' between some frequencies too > often at constant load, as there's insufficient hysteresis between the > idle/running marks. Compare it with using the default -i and -r and if > those aren't suitable, try rather smaller variations from the defaults. > > If it lacks responsiveness, try decreasing the polling interval. > > cheers, Ian Thanks Ian, -i and -r values was selected (3 month ago) by long playing with `powerd -v [flags]` in foreground, as you advice to me. The behavior of powerd is correct, and parameters was selected correctly to my environment. Also, debug.cpufreq.lowest was set to 500, and it starts to increase with 30% of CPU load, and decrease (to 500) with 35%. It's just good to me and it perfectly works. I'm realy think it's all about my hdd (WD), its toooooo hot, even when no file activity, even when lid is closed, on battery or on AC, no matter. It's about 60-65C. How to decrease the polling interval? Thanks again! From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 24 02:01:54 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 072051065675 for ; Wed, 24 Dec 2008 02:01:54 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 629188FC1F for ; Wed, 24 Dec 2008 02:01:53 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id mBO21p6s089821; Wed, 24 Dec 2008 13:01:51 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 24 Dec 2008 13:01:50 +1100 (EST) From: Ian Smith To: Dmitry Kolosov In-Reply-To: <200812231941.11998.ivakras1@gmail.com> Message-ID: <20081224122702.C29108@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <200812221927.00568.ivakras1@gmail.com> <20081223140958.I29108@sola.nimnet.asn.au> <200812231941.11998.ivakras1@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org 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: Wed, 24 Dec 2008 02:01:54 -0000 On Tue, 23 Dec 2008, Dmitry Kolosov wrote: > On Tuesday 23 December 2008 06:40:50 Ian Smith wrote: > > On Mon, 22 Dec 2008, Dmitry Kolosov wrote: > > [..] > > > > > Could you give to us some links about powersaving with EST? For now, i'm > > > using powerd: > > > powerd_enable="YES" > > > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > > > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me > > > (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal > > > in both cases and something about 50 minutes, so i think powerd is not > > > so powerfull for me. > > > > -i percent Specifies the CPU idle percent level when adaptive mode > > should begin to degrade performance to save power. The > > default is 90% or higher. > > > > -r percent Specifies the CPU idle percent level where adaptive mode > > should consider the CPU running and increase performance. > > The default is 65% or lower. > > > > I don't think your powerd running and idle percentages are likely to > > work too well; too close together, and too close to the 'busy' end. > > > > Try stopping powerd (/etc/rc.d/powerd stop) then running powerd manually > > in verbose mode in its own console (powerd -v [flags]) to watch how it > > behaves under varying loads. > > > > I suspect that you will find it 'flapping' between some frequencies too > > often at constant load, as there's insufficient hysteresis between the > > idle/running marks. Compare it with using the default -i and -r and if > > those aren't suitable, try rather smaller variations from the defaults. > > > > If it lacks responsiveness, try decreasing the polling interval. > > > > cheers, Ian > > Thanks Ian, > -i and -r values was selected (3 month ago) by long playing with `powerd -v > [flags]` in foreground, as you advice to me. The behavior of powerd is correct, > and parameters was selected correctly to my environment. Also, > debug.cpufreq.lowest was set to 500, and it starts to increase with 30% of CPU > load, and decrease (to 500) with 35%. It's just good to me and it perfectly > works. Fine if it works for you. However your settings are 30% idle (70% busy) and 35% idle (65% busy), not percent loaded as you've expressed it here. > I'm realy think it's all about my hdd (WD), its toooooo hot, even when no file > activity, even when lid is closed, on battery or on AC, no matter. It's about > 60-65C. I agree, 60C is too hot for a HDD. I'd get nervous over ~50C myself. Have you tried cleaning out the dust from the air passages and fan/s? > How to decrease the polling interval? -p ival Specifies a different polling interval (in milliseconds) for AC line state and system idle levels. The default is 500 ms. With a shorter interval, say 250ms, you may find that a lower value of debug.cpufreq.lowest will be responsive enough, which might save power. cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 24 08:15:07 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA2721065688; Wed, 24 Dec 2008 08:15:07 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 646ED8FC28; Wed, 24 Dec 2008 08:15:07 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LFOtI-000PGs-5u; Wed, 24 Dec 2008 16:14:52 +0800 Message-ID: <4951EF85.9030406@micom.mng.net> Date: Wed, 24 Dec 2008 16:15:01 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.12 (X11/20080415) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: mav@freebsd.org, Jung-uk Kim Subject: suspend/resume on T400 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: Wed, 24 Dec 2008 08:15:07 -0000 Hi all, May I know the current status of suspend/resume state on i386 SMP system? I'm using CURRENT so if there are any patches I'm more than willing to try. Any links, tips and tricks are much appreciated. thanks in advance, Ganbold -- Q: What do little WASPs want to be when they grow up? A: The very best person they can possibly be. From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 24 08:23:55 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 288EB106567D for ; Wed, 24 Dec 2008 08:23:55 +0000 (UTC) (envelope-from takawata@init-main.com) Received: from sana.init-main.com (unknown [IPv6:2001:240:28::1]) by mx1.freebsd.org (Postfix) with ESMTP id BCC218FC1A for ; Wed, 24 Dec 2008 08:23:54 +0000 (UTC) (envelope-from takawata@init-main.com) Received: from ns.init-main.com (localhost [127.0.0.1]) by sana.init-main.com (8.14.3/8.14.3) with ESMTP id mBO8Jxlt039089; Wed, 24 Dec 2008 17:19:59 +0900 (JST) (envelope-from takawata@ns.init-main.com) Message-Id: <200812240819.mBO8Jxlt039089@sana.init-main.com> To: Ganbold In-reply-to: Your message of "Wed, 24 Dec 2008 16:15:01 +0800." <4951EF85.9030406@micom.mng.net> Date: Wed, 24 Dec 2008 17:19:59 +0900 From: Takanori Watanabe Cc: freebsd-acpi@freebsd.org Subject: Re: suspend/resume on T400 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: Wed, 24 Dec 2008 08:23:55 -0000 In message <4951EF85.9030406@micom.mng.net>, Ganbold wrote: >Hi all, > >May I know the current status of suspend/resume state on i386 SMP system? >I'm using CURRENT so if there are any patches I'm more than willing to try. >Any links, tips and tricks are much appreciated. > >thanks in advance, I wrote a patch for it ageinst current at MAY 2008 -CURRENT, but I don't update it then. http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 24 16:01:49 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64E671065673 for ; Wed, 24 Dec 2008 16:01:49 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id E4A378FC08 for ; Wed, 24 Dec 2008 16:01:48 +0000 (UTC) (envelope-from ivakras1@gmail.com) Received: by ey-out-2122.google.com with SMTP id d26so353241eyd.7 for ; Wed, 24 Dec 2008 08:01:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=os3Nsz9u4GgTbxbzQwFRpRyWwD6UrpYV8kJo/8Fdda4=; b=JKZHPdiOrXiyGhmTBTSiQ+gpdq/yCJf3GMxdjI4MSvY5DT8sinwrJgR/1tb6kfrSyt oonu8uk0H7NKy/AUVuO2o44EmpR2VQz5VTc9HuoykkTMqpd+swH1jY6rX4xwlz7FS1Qw Yekay9MzCo396QL4JnH6ldLwyqAH8EEgVLg6U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=Dm0/K6B7OSwCMjdkX2qbftu7Pje0T6zdHaPKmh9/jY27MY5CWeEajluJVEbxK5uukw GxjFJuk6KUiVD47DO7OsL5BEgGUdd6+OYfMK/n57NAmvkF2Rsse+8nOddgQrYu4tQ1sG hUElh4ni5+VKWwcUoUd6jI3ByDQLqkaRnpfaI= Received: by 10.210.126.18 with SMTP id y18mr3053485ebc.72.1230134507683; Wed, 24 Dec 2008 08:01:47 -0800 (PST) Received: from ?192.168.2.101? ([92.50.244.160]) by mx.google.com with ESMTPS id 28sm1522018eye.30.2008.12.24.08.01.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 24 Dec 2008 08:01:46 -0800 (PST) From: Dmitry Kolosov To: freebsd-acpi@freebsd.org Date: Wed, 24 Dec 2008 19:01:33 +0300 User-Agent: KMail/1.9.10 References: <20081221233822.7E92545020@ptavv.es.net> <200812231941.11998.ivakras1@gmail.com> <20081224122702.C29108@sola.nimnet.asn.au> In-Reply-To: <20081224122702.C29108@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812241901.33857.ivakras1@gmail.com> 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: Wed, 24 Dec 2008 16:01:49 -0000 On Wednesday 24 December 2008 05:01:50 Ian Smith wrote: > On Tue, 23 Dec 2008, Dmitry Kolosov wrote: > > On Tuesday 23 December 2008 06:40:50 Ian Smith wrote: > > > On Mon, 22 Dec 2008, Dmitry Kolosov wrote: > > > [..] > > > > > > > Could you give to us some links about powersaving with EST? For > > > > now, i'm using powerd: > > > > powerd_enable="YES" > > > > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > > > > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to > > > > me (125 MHz on battery and 2.16GHz on AC), BUT battery life time is > > > > equal in both cases and something about 50 minutes, so i think > > > > powerd is not so powerfull for me. > > > > > > -i percent Specifies the CPU idle percent level when adaptive > > > mode should begin to degrade performance to save power. The default > > > is 90% or higher. > > > > > > -r percent Specifies the CPU idle percent level where adaptive > > > mode should consider the CPU running and increase performance. The > > > default is 65% or lower. > > > > > > I don't think your powerd running and idle percentages are likely to > > > work too well; too close together, and too close to the 'busy' end. > > > > > > Try stopping powerd (/etc/rc.d/powerd stop) then running powerd > > > manually in verbose mode in its own console (powerd -v [flags]) to > > > watch how it behaves under varying loads. > > > > > > I suspect that you will find it 'flapping' between some frequencies > > > too often at constant load, as there's insufficient hysteresis between > > > the idle/running marks. Compare it with using the default -i and -r > > > and if those aren't suitable, try rather smaller variations from the > > > defaults. > > > > > > If it lacks responsiveness, try decreasing the polling interval. > > > > > > cheers, Ian > > > > Thanks Ian, > > -i and -r values was selected (3 month ago) by long playing with > > `powerd -v [flags]` in foreground, as you advice to me. The behavior of > > powerd is correct, and parameters was selected correctly to my > > environment. Also, > > debug.cpufreq.lowest was set to 500, and it starts to increase with 30% > > of CPU load, and decrease (to 500) with 35%. It's just good to me and it > > perfectly works. > > Fine if it works for you. However your settings are 30% idle (70% busy) > and 35% idle (65% busy), not percent loaded as you've expressed it here. > > > I'm realy think it's all about my hdd (WD), its toooooo hot, even when > > no file activity, even when lid is closed, on battery or on AC, no > > matter. It's about 60-65C. > > I agree, 60C is too hot for a HDD. I'd get nervous over ~50C myself. > Have you tried cleaning out the dust from the air passages and fan/s? > > > How to decrease the polling interval? > > -p ival Specifies a different polling interval (in milliseconds) > for AC line state and system idle levels. The default is 500 ms. > > With a shorter interval, say 250ms, you may find that a lower value of > debug.cpufreq.lowest will be responsive enough, which might save power. > > cheers, Ian Oh,thanks Ian! I'll review my powerd settings. About the dust-its clean, laptop is 3 month old, and i'm checking fans and air ways for dust regulary. Thanks for advice! From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 25 01:19:21 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBE0C106564A for ; Thu, 25 Dec 2008 01:19:21 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id 729D68FC13 for ; Thu, 25 Dec 2008 01:19:21 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=daemon.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LFesT-0004v2-GY; Thu, 25 Dec 2008 09:19:05 +0800 Message-ID: <4952DF94.8000700@micom.mng.net> Date: Thu, 25 Dec 2008 09:19:16 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.12 (X11/20080415) MIME-Version: 1.0 To: Takanori Watanabe References: <200812240819.mBO8Jxlt039089@sana.init-main.com> In-Reply-To: <200812240819.mBO8Jxlt039089@sana.init-main.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: suspend/resume on T400 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 01:19:21 -0000 Takanori Watanabe wrote: > In message <4951EF85.9030406@micom.mng.net>, Ganbold wrote: > >> Hi all, >> >> May I know the current status of suspend/resume state on i386 SMP system? >> I'm using CURRENT so if there are any patches I'm more than willing to try. >> Any links, tips and tricks are much appreciated. >> >> thanks in advance, >> > > I wrote a patch for it ageinst current at MAY 2008 -CURRENT, > but I don't update it then. > > http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html > Do you have a list of drivers that are known to work with this patch or at least the drivers that you have no problem on your system? Please let me know. I will try experiment your patch on weekend. thanks a lot, Ganbold -- With reasonable men I will reason; with humane men I will plead; but to tyrants I will give no quarter. -- William Lloyd Garrison 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 From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 27 03:12:27 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 F1D801065670 for ; Sat, 27 Dec 2008 03:12:26 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id C73188FC08 for ; Sat, 27 Dec 2008 03:12:26 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so5224613rvf.43 for ; Fri, 26 Dec 2008 19:12:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=lJAawFZd3tNnbiJ4t+1DSu9Q0739iJH/k3ykGeMB5Zw=; b=SW7BOeHIoCPBafB2crz+dDmFs7xshAdFtn+Z9SYaMMC5AeW/N0gtwAnfoVS0rSs57+ 8iC+TplQCePYLfxE7JqFyzeOoah8Ui0O8UnFPD5Jwu2cGwVoX14b3x/FD3waUciLdUgr kEsVh52ENjdE+VOcNBil3bwDSZCJ1na570oSg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XBwnqaFYLPP2ZKL1uE9H+d7OV0BtHrlDn066x0NTFa7XgbJcfSMSZGmL0hj0pbuddB KO4PHOAPN/0gPdnG0GoVZS2sQmDFP6iDLVoNePH7/q6uB2LHsFVXMrAoIQ2dxjhUkk+T k3hy206lZ26jW+7SCiyslHgsaavpMx2w/MGHs= Received: by 10.141.176.13 with SMTP id d13mr5536267rvp.231.1230347546587; Fri, 26 Dec 2008 19:12:26 -0800 (PST) Received: by 10.140.135.2 with HTTP; Fri, 26 Dec 2008 19:12:26 -0800 (PST) Message-ID: <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> Date: Fri, 26 Dec 2008 19:12:26 -0800 From: "Garrett Cooper" To: "David van Kuijk" In-Reply-To: <49534F10.7040305@bigfoot.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> 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: Sat, 27 Dec 2008 03:12:27 -0000 On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: > > > >>>>> >>>>> 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 Dog gone it I've been typo'ing that for a long time (see http://lists.freebsd.org/pipermail/cvs-all/2003-November/036370.html). Try: hw.acpi.cpu.cx.lowest hw.acpi.cpu.cx.highest Note that the underscores were in fact periods. Cheers, -Garrett From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 27 06:39:28 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 20CCD106564A for ; Sat, 27 Dec 2008 06:39:28 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 69F3F8FC18 for ; Sat, 27 Dec 2008 06:39:26 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id mBR6Dwpi037893; Sat, 27 Dec 2008 17:13:58 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 27 Dec 2008 17:13:58 +1100 (EST) From: Ian Smith To: Garrett Cooper In-Reply-To: <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> Message-ID: <20081227160941.I29108@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Sat, 27 Dec 2008 06:39:28 -0000 On Fri, 26 Dec 2008, Garrett Cooper wrote: > On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: [..] > >> 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. I don't think it exists; C1 state is always available AFAIK. > > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > > should set it to C2 or C3??? Give it a try. Setting it to C3 won't hurt, whether it's used or not. First check dev.cpu.%d.cx_supported which shows the supported states. There's also dev.cpu.%d.cx_lowest (showing the lowest state used) and dev.cpu.%d.cx_usage, showing percentage time spent in various states. If it winds up helping, set performance_cx_lowest=C3 (or C2 or just 'LOW') in /etc/rc.conf .. see /etc/rc.d/power_profile for how it's used. > > 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)? Show us 'sysctl dev.cpu' .. and check dmesg for which if any of acpi cpufreq drivers are being used. Maybe it's powernow for the Opteron? 'sysctl dev | grep settings' may show something about the drivers used. > > Cheers, > > David > > Dog gone it I've been typo'ing that for a long time (see > http://lists.freebsd.org/pipermail/cvs-all/2003-November/036370.html). > > Try: > > hw.acpi.cpu.cx.lowest > hw.acpi.cpu.cx.highest > > Note that the underscores were in fact periods. I don't think that suggestion was ever implemented .. there have been quite some changes with all this, in fact I'm not sure the acpi(4) man is up to date (looking at 7-STABLE manuals online) .. it still talks about hw.acpi.cpu.{cx_supported,cx_lowest,cx_usage} where cx_supported and cx_usage have moved to dev.cpu.%d .. all a bit confusing. cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 27 12:57:05 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2618F106564A; Sat, 27 Dec 2008 12:57:05 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id C9AEC8FC0C; Sat, 27 Dec 2008 12:57:04 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from [202.179.21.165] (helo=devil.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LGYio-0000RJ-4E; Sat, 27 Dec 2008 20:56:50 +0800 Message-ID: <4956261D.9050305@micom.mng.net> Date: Sat, 27 Dec 2008 20:57:01 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.17 (X11/20081020) MIME-Version: 1.0 To: Jung-uk Kim References: <1224616985.00027652.1224606603@10.7.7.3> <200812102120.03788.jkim@FreeBSD.org> <49419BB9.8030408@FreeBSD.org> <200812111817.32334.jkim@FreeBSD.org> In-Reply-To: <200812111817.32334.jkim@FreeBSD.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-acpi@FreeBSD.org, Alexander Motin Subject: Re: Semi-working patch for amd64 suspend/resume 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: Sat, 27 Dec 2008 12:57:05 -0000 Jung-uk Kim wrote: > On Thursday 11 December 2008 06:01 pm, Alexander Motin wrote: > >> Jung-uk Kim wrote: >> >>> FYI, I uploaded a new patch with some fixes (against today's >>> CURRENT): >>> >>> http://people.freebsd.org/~jkim/amd64_suspend.diff >>> Jung-uk, Do you have a patch for i386? What does require to make suspend/resume work on i386 (based on your patch)? I'm willing to test. I tried the patch (http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html) however system panics when I try to suspend. thanks, Ganbold >> It is still working for me. >> > > Good. > > >>> This patch should be feature complete but I'd say it is still >>> considered experimental as it is not properly reviewed. >>> >> This comment looks stale: >> /* Restore PAT and MTRRdefType. */ >> > > Corrected. > > Thanks for the feedback! > > Jung-uk Kim > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > > > -- The one charm of marriage is that it makes a life of deception a necessity. -- Oscar Wilde From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 27 15:04:18 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 3B1B71065677 for ; Sat, 27 Dec 2008 15:04:18 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.186]) by mx1.freebsd.org (Postfix) with ESMTP id E23018FC1D for ; Sat, 27 Dec 2008 15:04:17 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so2885003rne.12 for ; Sat, 27 Dec 2008 07:04:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=fZN6uRUrbrvmXXbZ2QQjHvLHpCoIwmL9ZWsjm/p+1bY=; b=Ghb1FSDPcdb799MFQbunMIgdF4t1aZEYPnCiS+K9NYVpTGI0AcCSfUNAHwttueNRXO v/Ym3GXKwK548PXqOUxBy7cFBPEZfBYVmyd2P7sEhcIdnwJyKhJJIHYVZUzfVL7QQJTO G/QMdlXQ+Ra/vV70cUdSbwFgHUEaRaIZoMIIY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=JMNaY7Al0SycgjeQY9e7hayDlrwxWQTJ49fgK7ybXjQq2Vyj8ZfnkSKpUg9jLHDmAn pCwZzeeILzFdejw3JKeadZREJpICdvBnEXLxiQxaKTPgV54WxUHesazolKhte/iULCG+ MWXIrDgsMLcOPcp2uXt7dh1l9D+1mRcjmY8qQ= Received: by 10.100.119.17 with SMTP id r17mr6789266anc.130.1230388540512; Sat, 27 Dec 2008 06:35:40 -0800 (PST) Received: from ?10.0.3.231? ([70.111.173.38]) by mx.google.com with ESMTPS id c1sm20891658ana.16.2008.12.27.06.35.38 (version=SSLv3 cipher=RC4-MD5); Sat, 27 Dec 2008 06:35:39 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: Ian Smith In-Reply-To: <20081227160941.I29108@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> <20081227160941.I29108@sola.nimnet.asn.au> Content-Type: text/plain; charset=utf-8 Date: Sat, 27 Dec 2008 09:35:19 -0500 Message-Id: <1230388519.1270.1.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit 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: Sat, 27 Dec 2008 15:04:18 -0000 On Sat, 2008-12-27 at 17:13 +1100, Ian Smith wrote: > On Fri, 26 Dec 2008, Garrett Cooper wrote: > > On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: > [..] > > >> 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. > > I don't think it exists; C1 state is always available AFAIK. > > > > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > > > should set it to C2 or C3??? > > Give it a try. Setting it to C3 won't hurt, whether it's used or not. Actually it just might (hurt that is). See below for the discussion. http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+2482 +/usr/local/www/db/text/2008/freebsd-acpi/20081109.freebsd-acpi -- Alexandre "Sunny" Kovalenko (Олександр Коваленко)