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!