From owner-freebsd-stable@FreeBSD.ORG Thu Jul 21 16:07:50 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id E4594106564A; Thu, 21 Jul 2011 16:07:49 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Thu, 21 Jul 2011 12:07:38 -0400 User-Agent: KMail/1.6.2 References: <20110719112033.GA51765@omma.gibson.athome> <201107201928.54079.jkim@FreeBSD.org> <20110721022818.GA17771@omma.gibson.athome> In-Reply-To: <20110721022818.GA17771@omma.gibson.athome> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107211207.41663.jkim@FreeBSD.org> Cc: Callum Gibson , freebsd-amd64@freebsd.org Subject: Re: powernow regression in 8-STABLE 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: Thu, 21 Jul 2011 16:07:50 -0000 On Wednesday 20 July 2011 10:28 pm, Callum Gibson wrote: > On 20Jul11 19:28, Jung-uk Kim wrote: > }From your dmesg output, I see that the processor speed was not > }calibrated properly. ML-40's max. core freq. is 2,200 MHz > according }to its specification but it was probed at 2,282 MHz, > which is too }high. I think that's the problem. Can you please > try the attached }patch? > > Yes, I have seen core freq wobble around for most of the time I've > owned it, but usually close to 2200. This morning (with my reverted > powernow.c) I had: dev.cpu.0.freq_levels: 3080/35000 2800/29000 > 2520/24000 2240/20000 1120/9000 which I don't believe I've seen > before. Anyway... > > With your new patch applied (and powernow.c changed back to > r222148) I get exact freq levels: > > dev.cpu.0.freq_levels: 2200/35000 2000/29000 1800/24000 1600/20000 > 800/9000 That's better. :-) > However, dev.cpu.0.freq OID is still missing from sysctl output. > > As another data point, with your new patch applied, but the old > powernow.c, (which I booted into mistakenly first time), I did have > dev.cpu.0.freq, but the freq levels weren't exact. > > Here is a new verbose boot output with a cleaned and built kernel, > 8-STABLE as at time=1311028656 and your patch applied: > > http://members.optusnet.com.au/callumgibson/verboseboot2.out Can you please do "set debug.cpufreq.verbose=1" from loader prompt and show me the dmesg output? I want to see intial settings. You can reset it from command line with "sysctl debug.cpufreq.verbose=0" later. Thanks, Jung-uk Kim