From owner-freebsd-current@FreeBSD.ORG Tue Jun 5 21:48:41 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C10301065859 for ; Tue, 5 Jun 2012 21:48:41 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.bf1.yahoo.com (mrout2-b.corp.bf1.yahoo.com [98.139.253.105]) by mx1.freebsd.org (Postfix) with ESMTP id 7B4BF8FC14 for ; Tue, 5 Jun 2012 21:48:41 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout2-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q55LmVgl076552 for ; Tue, 5 Jun 2012 14:48:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1338932912; bh=riQzqMJAAaQbcv7On33ssbIl9wMyDYFwlZJ7EzSa8+s=; h=Subject:From:To:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=JgLtQr8/RwVS6m8VSOw5Tc6Jb1MHj28B522cIovFO8fevW+i0hCCKmDTn9jEhgdYC Yck11Kbuhpye+Bv39uA1ug1cuPSOYHfWebIUq8gxpGR3Gkw4EpIqg2ZoB3RIu7hoOg mAUcjdDFmTK9L3AXyNzHrSvN6ddsKv2UQPHsLQCY= From: Sean Bruno To: "freebsd-current@freebsd.org" In-Reply-To: <1338922510.10539.8.camel@powernoodle-l7.corp.yahoo.com> References: <1338922510.10539.8.camel@powernoodle-l7.corp.yahoo.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 05 Jun 2012 14:13:19 -0700 Message-ID: <1338930799.10539.12.camel@powernoodle-l7.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 932912000 Subject: Re: est man page X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 21:48:41 -0000 On Tue, 2012-06-05 at 11:55 -0700, Sean Bruno wrote: > I note that x86/cpufreq/est.c has some tuneables and I have processors > that seem to be not supported by est even though they appear to have > Speedstep features: > > p4tcc0: on cpu0 > est1: on cpu1 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 15 > device_attach: est1 attach returned 6 > *ACTUALLY* this was caused by the Dell r410 that I was using having its Power Managment control set to "Advanced Power Management" and not "OS Control". After I set that, the acpi methods in est attached correctly. Sean