From owner-freebsd-current@FreeBSD.ORG Fri Sep 16 05:39:27 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6A6C106564A for ; Fri, 16 Sep 2011 05:39:27 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1FF3F8FC12 for ; Fri, 16 Sep 2011 05:39:26 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA23732; Fri, 16 Sep 2011 08:39:24 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1R4R91-0007U6-RN; Fri, 16 Sep 2011 08:39:23 +0300 Message-ID: <4E72E109.6000705@FreeBSD.org> Date: Fri, 16 Sep 2011 08:39:21 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.2) Gecko/20110907 Thunderbird/6.0.2 MIME-Version: 1.0 To: Arnaud Lacombe References: In-Reply-To: X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: 9.0-BETA2 do not support SpeedStep on E5420 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: Fri, 16 Sep 2011 05:39:27 -0000 on 16/09/2011 00:19 Arnaud Lacombe said the following: > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 616082506000825 > device_attach: est0 attach returned 6 This is a far more common issue. The output implies that acpi_perf driver hasn't been able to attach, presumably because it couldn't evaluate _PSS method. We usually discuss problems like this one on acpi@ and you can find some information in the archives of that mailing list. Diagnosing an issue like this requires examining DSDT and SSDT(s), if present, to see the logic there and what capabilities the firmware/BIOS expects from the OS. It's a tedious process and I am currently short on time. -- Andriy Gapon