From owner-freebsd-stable@FreeBSD.ORG Tue Jan 22 08:47:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B65916A417; Tue, 22 Jan 2008 08:47:43 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 8C75613C465; Tue, 22 Jan 2008 08:47:42 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.13.8/8.13.8) with ESMTP id m0M8lcAN021172; Tue, 22 Jan 2008 09:47:40 +0100 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 75F344F; Tue, 22 Jan 2008 09:47:38 +0100 (CET) Date: Tue, 22 Jan 2008 09:47:56 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Jeremy Chadwick Message-Id: <20080122094756.2d8f0bdf.gerrit@pmp.uni-hannover.de> In-Reply-To: <20080121170102.GA46419@eos.sc1.parodius.com> References: <20080121171606.8eb5f189.gerrit@pmp.uni-hannover.de> <20080121170102.GA46419@eos.sc1.parodius.com> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.3; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.0.320885 Cc: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: T7200 CPU not detected by est X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 08:47:43 -0000 On Mon, 21 Jan 2008 09:01:02 -0800 Jeremy Chadwick wrote about Re: T7200 CPU not detected by est: JC> > Jan 18 23:18:14 comet kernel: est1: > Control> on cpu1 Jan 18 23:18:14 comet kernel: est: CPU supports JC> > Control> Enhanced Speedstep, but is not recognized. JC> > Jan 18 23:18:14 comet kernel: est: cpu_vendor GenuineIntel, msr JC> > 6130c2906000c29 Jan 18 23:18:14 comet kernel: device_attach: est1 JC> > attach returned 6 JC> I see identical behaviour on our Supermicro PDSMI+ systems, using E6420 JC> CPUs, so I don't believe the problem is specific to your motherboard or JC> certain Intel CPU models: It is definitely not bound to certain mainboards, because I see it on several different ones. However, I have only T-series CPUs to test. JC> CPU: Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz (2128.01-MHz JC> 686-class CPU) acpi0: on motherboard JC> acpi0: [ITHREAD] JC> acpi0: Power Button (fixed) JC> cpu0: on acpi0 JC> est0: on cpu0 JC> est: CPU supports Enhanced Speedstep, but is not recognized. JC> est: cpu_vendor GenuineIntel, msr 82a082a0600082a JC> device_attach: est0 attach returned 6 JC> cpu1: on acpi0 JC> est1: on cpu1 JC> est: CPU supports Enhanced Speedstep, but is not recognized. JC> est: cpu_vendor GenuineIntel, msr 82a082a0600082a JC> device_attach: est1 attach returned 6 Ok, so it's probably neither specific for CPUs nor for the mainbaords; however, up to now all CPUs with this problem are Core2 CPUs. JC> In the case of our servers, we usually turn EIST off (this one JC> particular box has it enabled) because of the above problem -- but I'd JC> much rather have it turned on to help save power. For a laptop or JC> workstation, however, I can see this being an incredibly important JC> feature. I run low power workstations here which are intended to be used in a lab environment, and I would very much like to have working power-saving features (otherwise the whole setup is quite useless). Can I somehow help debugging this, should I file a PR or are there any further recommended things to do? cu Gerrit