From owner-freebsd-current@FreeBSD.ORG Fri Jun 19 08:35:45 2009 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 8637C1065670; Fri, 19 Jun 2009 08:35:45 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 15BE68FC0C; Fri, 19 Jun 2009 08:35:45 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=oPNrfb8M5IHQA7GiIgFSg+v3BpIVsNWWFUkwURomE8rYu4AAm03IP8nPaRaDmOJMyMNlM66KCxDeQTyncxuebA2OAHU+GxLgDPAJ/4iQaBtuRyeEV32XsZC1pJofBdi1iwXX9MrpCYxhAEc8oFULXpvtuuac4DgW6Hah28gDqvU=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1MHZZX-0000I1-6h; Fri, 19 Jun 2009 12:35:43 +0400 Date: Fri, 19 Jun 2009 12:35:41 +0400 From: Eygene Ryabinkin To: pluknet Message-ID: References: <200906180909.33511.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: rea-fbsd@codelabs.ru Cc: freebsd-current@freebsd.org Subject: Re: estX still not attaching properly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rea-fbsd@codelabs.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2009 08:35:45 -0000 Good day. Thu, Jun 18, 2009 at 06:17:19PM +0400, pluknet wrote: > 2009/6/18 John Baldwin : > > On Wednesday 17 June 2009 2:29:25 pm Alexander Best wrote: > >> hi there, > >> > >> although i'm running a very recent current which has "ACPICA 20090521", estX > >> still isn't attaching properly on my machine: > >> > >> est0: on cpu0 > >> est: CPU supports Enhanced Speedstep, but is not recognized. > >> est: cpu_vendor GenuineIntel, msr 925092506000925 > >> device_attach: est0 attach returned 6 > >> est1: on cpu1 > >> est: CPU supports Enhanced Speedstep, but is not recognized. > >> est: cpu_vendor GenuineIntel, msr 925092506000925 > >> device_attach: est1 attach returned 6 > > > > That just means ACPI isn't providing info about the speed steppings your CPU > > provides. True. Probably update to the latest BIOS will help, but may be it won't: some vendors aren't putting the stuff to the ACPI tables. > > It is odd that cpu0 has freq_levels but cpu1 does not. > > While here let me also please share my own acpi/est data. > I hope it would not bother you too much. > est attaches to all cpu:s, but again freq_levels is only on cpu0. It is the proper behaviour of the ACPI's cpufreq driver: frequency levels for all CPUs are meant to be the same. See sys/kern/kern_cpu.c (cpufreq_attach(), line 172 or something like this), ----- /* * Only initialize one set of sysctls for all CPUs. In the future, * if multiple CPUs can have different settings, we can move these * sysctls to be under every CPU instead of just the first one. */ numdevs = devclass_get_count(cpufreq_dc); if (numdevs > 1) return (0); CF_DEBUG("initializing one-time data for %s\n", device_get_nameunit(dev)); SYSCTL_ADD_PROC(&sc->sysctl_ctx, SYSCTL_CHILDREN(device_get_sysctl_tree(parent)), OID_AUTO, "freq", CTLTYPE_INT | CTLFLAG_RW, sc, 0, cpufreq_curr_sysctl, "I", "Current CPU frequency"); SYSCTL_ADD_PROC(&sc->sysctl_ctx, SYSCTL_CHILDREN(device_get_sysctl_tree(parent)), OID_AUTO, "freq_levels", CTLTYPE_STRING | CTLFLAG_RD, sc, 0, cpufreq_levels_sysctl, "A", "CPU frequency levels"); ----- -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ #