From owner-freebsd-acpi@FreeBSD.ORG  Mon Nov  1 10:16:13 2010
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
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 504FD106566C
	for <freebsd-acpi@freebsd.org>; Mon,  1 Nov 2010 10:16:13 +0000 (UTC)
	(envelope-from jt@xoasis.de)
Received: from pluto.xoasis.de (pluto.xoasis.de [85.159.14.10])
	by mx1.freebsd.org (Postfix) with ESMTP id D94C68FC0A
	for <freebsd-acpi@freebsd.org>; Mon,  1 Nov 2010 10:16:12 +0000 (UTC)
Received: from pad (rh2.xoasis.de [194.77.193.180]) (authenticated bits=0)
	by pluto.xoasis.de (8.13.8/8.13.6) with ESMTP id oA19qBOX022087
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <freebsd-acpi@freebsd.org>; Mon, 1 Nov 2010 10:52:14 +0100 (CET)
	(envelope-from jt@xoasis.de)
To: freebsd-acpi@freebsd.org
Content-Disposition: inline
From: Joerg Traeger <jt@xoasis.de>
Date: Mon, 1 Nov 2010 11:52:10 +0200
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201011011052.11084.jt@xoasis.de>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-3.0 (pluto.xoasis.de [85.159.14.10]);
	Mon, 01 Nov 2010 10:52:14 +0100 (CET)
X-XOASIS-EmailScanner-Information: 
X-XOASIS-EmailScanner: Found to be clean
X-XOASIS-EmailScanner-From: jt@xoasis.de
Subject: est CPU support
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jt@xoasis.de
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2010 10:16:13 -0000

Hi,

I have got several mainboards with CPUs which appear not to be
supportet by est. An error exists: 

(examle of somewhat older Intel DG45FC with DualCore E5200 and latest BIOS)

est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 61a4c1f06004c1f
device_attach: est0 attach returned 6      <----------
p4tcc0: <CPU Frequency Thermal Control> on cpu0
[...]
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 61a4c1f06004c1f
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1

Searching the net I found several hints this CPU (Intel DualCore E5200) _is_ 
supported by EST and the voltage is being reduced in idle states like 
intended.
So it looks like there are more things which might break success using est for 
me. Can you explain what may be a reason for this problem? In the past it was 
about hardcoding cpu data about voltages into the source but as I know this 
is not the case anymore but ACPI is involved.
Is the BIOS likely to be the reason or is it an ignored CPU stepping or...?

Same happens with the new CPU Intel Atom N550 on a Jetway board called 
NC9c-550-LF. est does not attach and some watts are wasted.

Thank you!