From owner-freebsd-questions@FreeBSD.ORG Mon Jan 21 17:44:22 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C221616A420 for ; Mon, 21 Jan 2008 17:44:22 +0000 (UTC) (envelope-from ghirai@ghirai.com) Received: from iota.fastbighost.com (iota.fastbighost.com [65.98.8.190]) by mx1.freebsd.org (Postfix) with ESMTP id 9479513C458 for ; Mon, 21 Jan 2008 17:44:22 +0000 (UTC) (envelope-from ghirai@ghirai.com) Received: from [89.123.34.240] (port=60880 helo=deimos.bsd.nix) by iota.fastbighost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JH0gw-00016i-4q; Mon, 21 Jan 2008 17:44:14 +0000 Date: Mon, 21 Jan 2008 19:43:19 +0200 From: Ghirai To: Andreas Davour Message-Id: <20080121194319.15a718ea.ghirai@ghirai.com> In-Reply-To: References: <47941E71.9070403@pacific.net.sg> <4794BAA9.7040609@pacific.net.sg> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.5; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PopBeforeSMTPSenders: ghirai@ghirai.com X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - iota.fastbighost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ghirai.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-questions@freebsd.org Subject: Re: Throttle the CPU when the system is idle X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 17:44:22 -0000 On Mon, 21 Jan 2008 16:41:41 +0100 (CET) Andreas Davour wrote: > > Hmmmm. This actually works, without any hangups. I wonder if I managed > to hit upon a odd bug yesterday? > > /andreas > I've been using it since 6.2 on 4 intel boxes (one of them a notebook) without any problems. You can check the available freq. steps with sysctl dev.cpu.0.freq_levels and see the current speed with sysctl dev.cpu.0.freq. Do make sure you set the debug.cpufreq.lowest to a sensible value, otherwise things will be somewhat sluggish. -- Regards, Ghirai.