From owner-freebsd-mobile@freebsd.org Sat Oct 14 21:26:06 2017 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF350E2CFAD; Sat, 14 Oct 2017 21:26:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3F2980DB3; Sat, 14 Oct 2017 21:26:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5DC83205E8; Sat, 14 Oct 2017 17:26:05 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Sat, 14 Oct 2017 17:26:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=5k3X3KFtP6Oso7QvuFNVqEMsLblvmt8IZDZnQOVONM8=; b=nl5SWWoo 9yqnAeG5PTC1TzkljmkQM73TzOtZA4WevBIE6ZyzmaJ5nLv7yFP9VVcTIXbl1ZVV yxi+AJ4hqaxDK8uHfH/+aYk3QtUgUAeslZw41cSPKJgfuU/ebX35SzB3om9c6ol6 fUzWm4BV4MweAHQWBt0/vsoZ/PVNpTC5CAF7DKxMMxijZewAtj2D2RF3QvQfe/8p M5foBG1pAkEORXDZJSbhzeXYyJcwf1a3DMKzLsCGJwT8uto0wcrlEIA3BMOrD5fT xvEkmdoTKYwFUaKnfKYXO2MYX4ek/i1u/FfWbZj5vHroCSXesu4keTtvy3Ga1fgD p4PbiaUyulVHqw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=5k3X3KFtP6Oso7QvuFNVqEMsLblvm t8IZDZnQOVONM8=; b=miBt8iNpmVbA6nGDYaymkkm0W0cEKHmd12/WqG4M2Lpgp xmAWSfFgjiqZ5Yct6/hRYRoXOqL9ebVa2H2n0kTXSVjFVlMdH2+0DEUwxwcT3Att K8Hgy0suplsnXoAd9fI2p5NH5OFAG31Q10lIQVMzZZQ9VqApFe2hj4ruulMKy9Sn PxBCtJhov6xSfPTq5yXM3aPICVVvQw2OaNG9nMB1hQVrhzWc3kA0LuxZWnY6eca8 +W9WQwR+ua2H45B6cQOJ4E39xu0rq2gJDORVLQig1tTaOWb1qG+ovWcGLi+CAGE8 sfYDkxkS1pxINB+zkwZE9HIQ3JwrockZUFOU5ZD6w== X-ME-Sender: Received: from acer.zyxst.net (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id AABC4249CD; Sat, 14 Oct 2017 17:26:04 -0400 (EDT) Date: Sat, 14 Oct 2017 22:26:02 +0100 From: tech-lists To: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: problems getting AMD C-70 APU working with powerd/cpufreq Message-ID: <20171014212602.GB92751@acer.zyxst.net> Mail-Followup-To: freebsd-hardware@freebsd.org, freebsd-mobile@freebsd.org References: <20171013123721.GA27736@acer.zyxst.net> <20171014215317.K34192@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20171014215317.K34192@sola.nimnet.asn.au> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 21:26:07 -0000 Hi, thanks for taking the time to look at this, On Sat, Oct 14, 2017 at 10:36:02PM +1100, Ian Smith wrote: >On Fri, 13 Oct 2017 13:37:21 +0100, tech-lists wrote: > > Hi, > > > > I have a netbook with amd c-70 cpu and am trying to get powerd > > to work with it. Will this chip not work with cpufreq/powerd? > >Perhaps not. oh well!! > > > system: FreeBSD 11.1-STABLE #0 r324342 > > > > # sysctl debug.cpufreq.verbose=1 > > debug.cpufreq.verbose: 0 -> 1 > >This shows that cpufreq was alreasy loaded. It's in the GENERIC kernel. >Have a good browse through cpufreq(4). I can't comment about earlier versions of FreeBSD, but this sysctl is present on 11.1-stable without cpufreq loaded. I'm using a modified kernel - modified to the extent that superfluous stuff has been removed, because this machine is hardware-challenged. Without cpufreq loaded, the following sysctls are present: # sysctl -a | grep cpufreq debug.cpufreq.verbose: 0 debug.cpufreq.lowest: 0 # uname -i ACER # cat /sys/amd64/conf/ACER |grep cpufreq # # cat /boot/loader.conf amdtemp_load="YES" # I've known this machine has had issues with cpufreq for a while, but this is the first time I've sat down to try work out why. This is one of the reasons why cpufreq isn't in my kernel. which is why I was able to > > # kldload cpufreq > > # no message (I set debug.cpufreq.verbose to 1 in order to hopefully see more output) > > dev.acpi_perf.1.%parent: cpu1 > > dev.acpi_perf.0.%parent: cpu0 > >These are interesting. In cpufreq(4) you'll see acpi_perf is one of the >absolute frequency control drivers, presumably used (see also in dmesg) >because the expected driver for AMD processors, powernow, did not attach >- though your verbose dmesg shows nothing about any failure/s to attach. > > > dev.cpu.1.cx_method: C1/hlt C2/io > > dev.cpu.1.cx_usage_counters: 237351 1893186 > > dev.cpu.1.cx_usage: 11.14% 88.85% last 156us > > dev.cpu.1.cx_lowest: C2 > >At least you're getting plentiful use of C2 state, though I'm not aware >how much power saving that might buy you on that AMD CPU. Not a lot! ;) One of the reasons I'm interested in powerd/cpufreq is that I beleive it can make turbo kick in. Apparently this chip has a turbo mode @1.333GHz. might be wrong about that though. >So, there's no dev.cpu.0.freq nor dev.cpu.0.freq_levels - therefore >powerd has nothing to work with. Its (misleading?) message doesn't mean >cpufreq not loaded, but that the sysctls powerd relies upon don't exist. [...] >Nothing in any of those suggests that this cpu has any other frequency >available than 1000MHz, which seems quite bizarre to me. Of course it's >possible FreeBSD hasn't been taught to recognise this particular cpu. > >You haven't disabled anything in $BIOS related to power or freq control? The bios has only a very limited number of options for this machine - possibly by design as the machine is a netbook. Options for overclocking are not present at all. >The cpuid output has a heading "Advanced Power Management Feature Flags" >near the bottom, but none are shown. yeah, odd that >Hope someone else has something more useful to offer, and thanks for >mailing me those files when my browser was deemed too old for your site. thanks again for your help -- J.