From owner-freebsd-bugs@FreeBSD.ORG Mon Feb 21 05:36:50 2011 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23772106566B; Mon, 21 Feb 2011 05:36:50 +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 3565E8FC16; Mon, 21 Feb 2011 05:36:48 +0000 (UTC) Received: from porto.topspin.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 HAA25668; Mon, 21 Feb 2011 07:22:41 +0200 (EET) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1PrOEL-000Bae-6q; Mon, 21 Feb 2011 07:22:41 +0200 Message-ID: <4D61F69F.2080708@freebsd.org> Date: Mon, 21 Feb 2011 07:22:39 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101211 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Bruce Cran References: <201102191520.p1JFK7PX094589@freefall.freebsd.org> <201102191551.46353.brucec@freebsd.org> In-Reply-To: <201102191551.46353.brucec@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@freebsd.org Subject: Re: kern/117607: [cpufreq] [amd64] dev.cpu.0.freq not showing up any longer on amd64 notebook [regression] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2011 05:36:50 -0000 on 19/02/2011 17:51 Bruce Cran said the following: > It seems the error is occuring because cf_get_method returns ENXIO > (kern_cpu.c:503). > > The only related checkin I can see recently was by avg (cc'd) with r210422. > It would be helpful to nail exact cause of this issue by using dtrace or printf? BTW, just in case, please note that the bug was originally reported against much earlier revision. -- Andriy Gapon