From owner-freebsd-acpi@FreeBSD.ORG Sun Mar 29 22:53:53 2009 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65EA81065670 for ; Sun, 29 Mar 2009 22:53:53 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from woodbine.london.02.net (woodbine.london.02.net [87.194.255.145]) by mx1.freebsd.org (Postfix) with ESMTP id E09168FC15 for ; Sun, 29 Mar 2009 22:53:52 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from [192.168.1.75] (93.97.24.219) by woodbine.london.02.net (8.5.016.1) id 4979BCBF01EF217D; Sun, 29 Mar 2009 23:52:47 +0100 Message-ID: <49CFFBBE.30605@onetel.com> Date: Sun, 29 Mar 2009 23:52:46 +0100 From: Chris Whitehouse User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Ian Smith References: <49C80E65.9090500@onetel.com> <49C93309.6050708@iki.fi> <20090325140718.J95588@sola.nimnet.asn.au> <49C9EE50.6070507@onetel.com> <1237992462.1297.22.camel@RabbitsDen> <49CBF7D1.20102@onetel.com> <49CC147A.3030805@root.org> <1238118621.1365.35.camel@RabbitsDen> <49CCDCBA.3000406@onetel.com> <20090329223815.U95588@sola.nimnet.asn.au> In-Reply-To: <20090329223815.U95588@sola.nimnet.asn.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org Subject: Re: acpi_tz0: _CRT value is absurd, ignored (256.0C) (was pr kern/105537) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2009 22:53:54 -0000 Ian Smith wrote: > > > If (\_OSI ("Windows 2001")) > > > { > > > Store (0x04, C014) > > > } > > > > > > If (\_OSI ("Windows 2001 SP1")) > > > { > > > Store (0x04, C014) > > > } > > > > > > If (\_OSI ("Windows 2001 SP2")) > > > { > > > Store (0x05, C014) > > > } > > > > > > If (\_OSI ("Windows 2006")) > > > { > > > Store (0x06, C014) > > > } > > > > > > Chris, you should be able to set hw.acpi.osname= > > above> in loader.conf and see if things improve somewhat. Note that > > > "Windows 2001" and "Windows 2001 SP1" are identical. > > > > sysctl says it is an unknown oid > > Try adding it to loader.conf and rebooting. Nope still unknown oid. But in view of other progress I don't think that matters, at least for me. > Quacks like a CPU0. This one triggers passive cooling. Its temperature > values are generally 2-3C lower than the (eyeball) average of coretemp > values, except when heating up fast, when it lags the latter by 5-6C. > > I don't know where these various sensors live. Board? Package? Die? > > > hw.acpi.thermal.tz2.temperature: 43.0C > > hw.acpi.thermal.tz2.active: -1 > > hw.acpi.thermal.tz2.passive_cooling: 0 > > hw.acpi.thermal.tz2.thermal_flags: 0 > > hw.acpi.thermal.tz2._PSV: -1 > > hw.acpi.thermal.tz2._HOT: -1 > > hw.acpi.thermal.tz2._CRT: 105.0C > > hw.acpi.thermal.tz2._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > > hw.acpi.thermal.tz2._TC1: 1 > > hw.acpi.thermal.tz2._TC2: 2 > > hw.acpi.thermal.tz2._TSP: 300 > > CPU1. From the messages it appears that burnk7 ran on just CPU0 (tz1). For some of the time I was running one instance of burnK7, other times 2 instances. I just tested and 2 instances does run on both cores. > > fetch www.fishercroft.plus.com/messages.gz > > > > will get bits of /var/log/messages with the normal startup messages and the > > output of > > > > #!/bin/sh > > while [ TRUE ]; do > > logger \ > > ` sysctl -n dev.cpu.0.temperature ; sysctl -n dev.cpu.1.temperature ; \ > > sysctl -n hw.acpi.thermal.tz0.temperature ; sysctl -n > > hw.acpi.thermal.tz0.active ; sysctl -n hw.acpi.thermal.tz0._CRT ; \ > > sysctl -n hw.acpi.thermal.tz1.temperature ; sysctl -n > > hw.acpi.thermal.tz1.active ; sysctl -n hw.acpi.thermal.tz1._CRT ; \ > > sysctl -n hw.acpi.thermal.tz2.temperature ; sysctl -n > > hw.acpi.thermal.tz2.active ; sysctl -n hw.acpi.thermal.tz2._CRT ; \ > > sysctl -n hw.acpi.thermal.tz3.temperature ; sysctl -n > > hw.acpi.thermal.tz3.active ; sysctl -n hw.acpi.thermal.tz3._CRT ; \ > > sysctl -n hw.acpi.thermal.tz4.temperature ; sysctl -n > > hw.acpi.thermal.tz4.active ; sysctl -n hw.acpi.thermal.tz4._CRT ` > > sleep 5 > > done > > > > (sorry bad wrapping) > > Good data. I don't know if it helps track the ASL re $subject though. > > > The two cpu temps come from coretemp.ko module. > > These I don't get. They always track a few degrees above tz1 value, but > rarely differ by more than 2C, while your burnk7 run showed CPU0 getting > much hotter than CPU1, which only slowly rose during the run, indicating > sympathetic package warming with an essentially idle CPU1, perhaps? Do you mean TZ1 gets much hotter than TZ2? When I ran 2 instances of burnk7 one ran on each cpu (viewed in top). When I ran a single instance the on-die temps in the first two columns still tracked each other. Also this machine is running KDE which is always doing something which blurs the figures a bit. I put messages2 next the previous one, I think it shows that tz2 is not cpu1 even if tz1 is measuring cpu temp somehow. dev.cpu.n.temperature columns are the on-die temps. Those oids are only visible when coretemp is loaded, I don't know if the ASL is using those temperature probes. Chris