From owner-freebsd-acpi@FreeBSD.ORG Thu May 6 10:58:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39AB316A4CE for ; Thu, 6 May 2004 10:58:50 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B66A143D39 for ; Thu, 6 May 2004 10:58:49 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 42605 invoked by uid 1000); 6 May 2004 17:58:50 -0000 Date: Thu, 6 May 2004 10:58:50 -0700 (PDT) From: Nate Lawson To: Jeffrey Katcher In-Reply-To: <20040506165526.41572.qmail@web41103.mail.yahoo.com> Message-ID: <20040506105607.J42462@root.org> References: <20040506165526.41572.qmail@web41103.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: power savings and usb X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2004 17:58:50 -0000 On Thu, 6 May 2004, Jeffrey Katcher wrote: > On my T40, I see: > hw.acpi.cpu.cx_lowest: 0 > hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 > hw.acpi.cpu.cx_history: 197586/0 0/0 0/0 > and the current power_profile script maintains cx_lowest as 0 > (i.e. not changing it on plug/unplug). The 1st number in history is the only > one to increment. This means you're only using C1. The value for cx_lowest is an index into cx_supported. (I'm changing this very soon to be more intuitive). The reason it doesn't change on AC power transition is probably that you don't have devd enabled. Enable it in /etc/rc.conf. > I can manually set cx_lowest to 2, not 3, then history changes to: > hw.acpi.cx_history: 0/0 2335/0 1710/30 > with the latter two incrementing. > > What does this mean? This means your C3 is working and you have manually selected it. Idling demotes to C2 or C1 when your machine is active to prevent performance degradation. -Nate