From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 02:41:06 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4B831065676; Thu, 10 Sep 2009 02:41:06 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3C83E8FC08; Thu, 10 Sep 2009 02:41:05 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n8A2f4UX067649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 12:11:04 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Robert Noland Date: Thu, 10 Sep 2009 12:10:59 +0930 User-Agent: KMail/1.9.10 References: <1252426982.00160755.1252414203@10.7.7.3> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> In-Reply-To: <1252501703.85394.3473.camel@balrog.2hip.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1407885.oH7L6S3sN3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909101211.01534.doconnor@gsoft.com.au> X-Spam-Score: -3.611 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Alexander Motin , FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 02:41:07 -0000 --nextPart1407885.oH7L6S3sN3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Robert Noland wrote: > > I am pretty sure it would be throttling but I think that works by > > maintaining the frequency but stalling the CPU some percentage of > > the time. I have p4tcc loaded (in GENERIC) but it doesn't show up, > > I only get.. > > Is this a core2duo? IIRC, they generally don't go into TCC until > around 100C. I did pull the c2d cpu docs at one point trying to look > at cpufreq. If you are bored, you can grab the docs from intel and > double check. Hmm, I only managed to get it to 75C or so.. Unfortunately the remote system which was exhibiting the problem has=20 been fixed and the onsite guy doesn't have time to pull it out and=20 break it again :( The coretemp source suggests that there are 2 max junction temperatures=20 for Core2Duos - 85C & 100C. However I just realised the "faulty" system has an E2140 in it which has=20 a 65W TDP, whereas the bench system has an E7500 with a TDP of 35W - I=20 guess that could explain the difference. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1407885.oH7L6S3sN3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKqGc95ZPcIHs/zowRAkcXAJ4rSsodJlqgMNH7tkmYiU9hvDxS9wCgi7N7 n4EJZQsP6hoXti6TexQkwj0= =Volh -----END PGP SIGNATURE----- --nextPart1407885.oH7L6S3sN3--