From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 12 03:13:29 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE378CCF for ; Mon, 12 Jan 2015 03:13:29 +0000 (UTC) Received: from o1.email.leadonics.com (o1.email.leadonics.com [50.31.32.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63B2F8B0 for ; Mon, 12 Jan 2015 03:13:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=email.leadonics.com; h=content-type:mime-version:from:to:reply-to:subject:list-unsubscribe; s=smtpapi; bh=edbvWi0FbcOxZcmELWm7rpzjnyU=; b=xQ0Fyx60aRUtUw+R0a UPhp7e5dwzyXkYfov4IUNEAE2Gm0HUijFQMqry0eKZ8n/fvUQnpriAX34aJvkU3p gVLtOYaKZTcO4cV75TuhDjjP+DAwIO3J2fojj0qlMmmppvh4b5VrnMuWvAPJNpsA 06GpljLYqJEKVwPfCadDHf5TA= Received: by filter-161.sjc1.sendgrid.net with SMTP id filter-161.27609.54B33B85A 2015-01-12 03:12:06.115623928 +0000 UTC Received: from MTM0MzU2Nw (unknown [10.42.83.122]) by ismtpd-083 (SG) with HTTP id 14adc2083de.665f.d9700 for ; Mon, 12 Jan 2015 03:12:06 +0000 (UTC) MIME-Version: 1.0 From: Platinum Property Group To: freebsd-ppc@freebsd.org Reply-to: sales@ppg.co.th Subject: Save over 1 Million THB on a condo 300 meters from Pratumnak beach, in Pattaya, Thailand Message-ID: <14adc2083de.665f.d9700@ismtpd-083> Date: Mon, 12 Jan 2015 03:12:06 +0000 (UTC) X-SG-EID: Vb+Anvs0EfIvXbjCHlZrgfJ7kERTSlN8eYfhjx7Ga+UJ5fe3h1a/wsmf6WQIw1b++LMBGPrEbSA+pt do7TF5NBKpRRew7lbnGS/R8T/g1+2OCrqJ0vKmeB4VSo2dBC2xqgkXGyXRkPXJibFjSsEQf/NOFGI8 GuPsHMi0/kgOlJ8= X-SG-ID: VPWZYjw6GOzHdwkwPeoX9QiEbzQXX/gF9P8njHP5+LBNxlCvH6h2TKPX70qCZtVZXQtfBrp/Y5agbq fkKH0ABV4S/xSWbvgP04Jo6GBR4ATnr8IouYjIMK3+MzUIjaQYoiked5L4d8zbnW6+R6x2kMa9LGaz fe/B+wKL2KzyQCwHEJf8vs+0QiO45/hJY5CLw13eQU7rB4KRXyXk62jWHA== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2015 03:13:30 -0000
=09=09=09=09=09=09=09

Time sensitive offer direct from t= he developer (that's us!):
An additional=C2=A015% discount on top of the alread= y discounted Thai/Company quota=C2=A0price

As the developer, we are offering a special January promotion on s= elected units on the 2nd, 3rd and 4th floors in The J= ewel Pratumnak. 17 units in total, this promotion is valid unti= l 31st January 2015.

This offer is an=C2=A0extre= mely generous discount of 15% on top of the already discounted Thai/Company= quota price list.

A 65 SQM=C2=A0uni= t on the 4th floor normally sells for 4,615,000 but is now priced a= t 3,608,930.=C2=A0You save a massive=C2=A01,006,070=C2=A0THB!

We also have 38 SQM units,= these normally sell for 2,546,000 but is now priced at 1,990,972. You save 555,028 THB!

<= span style=3D"color: rgb(255, 0, 0);" data-mce-style=3D"color: #ff0000;">Click here=C2=A0right now to download the = info pack and price list, or you can call or email me=C2= =A0to arrange a visit to our show room on Pratumnak. This = offer ends very soon and they will sell fast so act now! Fantastic for inve= stors and residents alike.

Email:=C2=A0<= a href=3D"mailto:michael@ppg.co.th" data-mce-href=3D"mailto:michael@ppg.co.= th">michael@ppg.co.th
Phone: +66 8 2362= 1938

3D""

Some more information about=C2=A0The Jewel Pratumnak:

The Jewel Pratumn= ak, an exclusive mid-rise condominium featuring 122 luxury condos in the ex= clusive area of Pratumnak, Pattaya. The development includes a Sky Garden, = infinity pool, fitness centre and sauna on the 14th floor and luxury fixtur= es and fittings throughout.

  • Condos are available wit= h an interest free payment plan
  • Great exchanges= rates for investors in current climate
  • Averag= e area rental returns over 15% per annum
  • Averag= e area condominium values have risen 40% in the last 2 years
  • Uninterrupted ocean views for an affordable price
  • Pratumnak showroom with two condo types now open=
  • World class design and build quality
  • 300 meters to Cozy Beach, Pratumnak
  • 2 minutes from Walking Street and Jomtien

    • Situated on Pratumnak - Kasetsin Soi 1, The Jewel is set on a quie= t road leading down to cozy beach. The development is positioned in one of = the most desirable locations in all of Pattaya and offers a range of first = class facilities. These include a 14th floor sky garden and infinity pool, = fully equipped gymnasium and sauna, covered parking, free Wi Fi and 24 hour= security. The Jewel has proven to be an extremely popular project with man= y units sold to existing Platinum Property Group customers.

    Project Features:

    • Every unit com= es with luxury fixtures and bathroom fittings
    • Built-in = kitchens with composite surfaces
    • Raised ceiling heights= and innovative room layouts
    • Fully Equipped Fitness Cen= tre on the14th=C2=A0Floor
    • Sauna and Steam room on the 1= 4th=C2=A0Floor
    • Sky Garden on the 14th Floor
      • =
    • All condos have exterior views
    • Ocean v= iews=C2=A0of Jomtien, Pratumnak and Pattaya Bay
    • Built on an Elevated corner site in prime location
      • 400m from Cozy Beach
    • 14th floor Infinity pool and= sky garden
    • Sheltered Parking
    • CCTV = / Key Card Access

    The Jewel Condominium is perfectl= y located, and we believe it offers the best value for money when compared = to similar condos.

    If you would like to learn more about = this amazing project please contact me by replying to this email, or callin= g me=C2=A0on +66 8 2362 1938 outside of Thailand, or on 08 2362 1938 if you= are inside Thailand.

    Or click here= to download=C2=A0the info pack=C2=A0and price = list instantly.

    Kind Regards

    M= ichael Ainscough
    Platinum Property Group Sales Manag= er

    Email:=C2=A0michael@ppg.co.th=
    Phone: +66 8 2362 1938

=C2=A0

=C2=A0

=C2=A0

If you would like to unsubscribe click here.
=09 =09=09=09=09= From owner-freebsd-ppc@FreeBSD.ORG Thu Jan 15 02:37:25 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CD3F7ACA for ; Thu, 15 Jan 2015 02:37:25 +0000 (UTC) Received: from asp.reflexion.net (outbound-244.asp.reflexion.net [69.84.129.244]) (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 8B6477A1 for ; Thu, 15 Jan 2015 02:37:25 +0000 (UTC) Received: (qmail 7878 invoked from network); 15 Jan 2015 02:30:44 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 15 Jan 2015 02:30:44 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Wed, 14 Jan 2015 21:30:43 -0500 (EST) Received: (qmail 14656 invoked from network); 15 Jan 2015 02:30:43 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 15 Jan 2015 02:30:43 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id C4FA91C43AB for ; Wed, 14 Jan 2015 18:30:37 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? Message-Id: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> Date: Wed, 14 Jan 2015 18:30:42 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 02:37:25 -0000 Context: I got my hands on a PowerMac G5 quad-core that when the cores are kept = busy (think "make -j 8 buildworld buildkernel") CPU A1's diode ends up = apparently stabilizing between 90degC and, say, 91.6degC, resulting in a = shutdown. (See the temperature message list below from one boot through = the automatic shutdown.) Question: Would a temperature threshold change or a fan-operation change of some = kind be appropriate to try? (If so: what and how?) Or is this likely = sufficient evidence that the G5 just should not be used? Information: $ grep -i temperature /var/log/messages Jan 14 01:42:29 FBSDG5M1 kernel: WARNING: Current temperature (CPU B1 = DIODE TEMP: 91.6 C) exceeds critical temperature (90.0 C); count=3D1 Jan 14 01:42:31 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 91.3 C) exceeds critical temperature (90.0 C); count=3D1 Jan 14 01:42:31 FBSDG5M1 kernel: WARNING: Current temperature (CPU A0 = DIODE TEMP: 91.4 C) exceeds critical temperature (90.0 C); count=3D1 Jan 14 01:46:21 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.6 C) exceeds critical temperature (90.0 C); count=3D1 Jan 14 01:46:24 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.9 C) exceeds critical temperature (90.0 C); count=3D2 Jan 14 01:48:21 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 93.0 C) exceeds critical temperature (90.0 C); count=3D1 Jan 14 01:48:23 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 95.7 C) exceeds critical temperature (90.0 C); count=3D2 Jan 14 01:48:25 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 95.7 C) exceeds critical temperature (90.0 C); count=3D3 Jan 14 01:48:26 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.9 C) exceeds critical temperature (90.0 C); count=3D4 Jan 14 01:49:56 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=3D1 Jan 14 01:49:58 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=3D2 Jan 14 01:50:00 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=3D3 Jan 14 01:50:02 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.8 C) exceeds critical temperature (90.0 C); count=3D4 Jan 14 01:50:03 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.8 C) exceeds critical temperature (90.0 C); count=3D5 Jan 14 01:50:06 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.6 C) exceeds critical temperature (90.0 C); count=3D6 Jan 14 01:50:06 FBSDG5M1 kernel: WARNING: CPU A1 DIODE TEMP temperature = exceeded critical temperature 6 times in a row; shutting down! Jan 14 01:50:07 FBSDG5M1 kernel: WARNING: Current temperature (CPU A1 = DIODE TEMP: 90.2 C) exceeds critical temperature (90.0 C); count=3D7 Jan 14 01:50:07 FBSDG5M1 kernel: WARNING: CPU A1 DIODE TEMP temperature = exceeded critical temperature 7 times in a row; shutting down! $ uname -a FreeBSD FBSDG5M1 10.1-RELEASE-p3 FreeBSD 10.1-RELEASE-p3 #2 r276159M: = Tue Dec 23 22:25:28 PST 2014 = root@FBSDG5M1:/usr/obj/usr/src/sys/GENERIC64vtsc powerpc GENERIC64vtsc is a GENERIC64 variant that builds both vt and sc (but not = ps3). $ freebsd-version -ku 10.1-RELEASE-p3 10.1-RELEASE-p3 (The context meets the criteria for freebsd -k to be accurate to what = was in use: the default kernel name.) $ svnlite info /usr/src/ Path: /usr/src Working Copy Root Path: /usr/src URL: https://svn0.us-west.freebsd.org/base/releng/10.1 Relative URL: ^/releng/10.1 Repository Root: https://svn0.us-west.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 276159 Node Kind: directory Schedule: normal Last Changed Author: des Last Changed Rev: 276159 Last Changed Date: 2014-12-23 14:56:01 -0800 (Tue, 23 Dec 2014) $ svnlite status /usr/src/ ? /usr/src/.snap ? /usr/src/restoresymtable M /usr/src/sys/ddb/db_main.c M /usr/src/sys/ddb/db_script.c M /usr/src/sys/powerpc/ofw/ofw_machdep.c M /usr/src/sys/powerpc/ofw/ofwcall64.S $ more /etc/make.conf WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D $ more /etc/src.conf WITH_DEBUG_FILES=3D WITHOUT_CLANG=3D $ more /usr/src/sys/powerpc/conf/GENERIC64vtsc include GENERIC64 ident GENERIC64vtsc nooptions PS3 #Sony Playstation 3 = HACK!!! to allow sc options DDB # HACK!!! to dump early crash = info (but 11.0-CURRENT already has it) options GDB # HACK!!! ... #options KTR #options KTR_MASK=3DKTR_TRAP #options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable extra checking typically used for FreeBSD 11.0-CURRENT: nooptions DEADLKRES #Enable the deadlock resolver nooptions INVARIANTS #Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT #Extra sanity checks of internal = structures, required by INVARIANTS nooptions WITNESS #Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN #Don't run witness on spinlocks = for speed nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones =3D=3D=3D Mark Millard markmi@dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Thu Jan 15 22:40:07 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3AFCE39A for ; Thu, 15 Jan 2015 22:40:07 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 E8C6AAFA for ; Thu, 15 Jan 2015 22:40:06 +0000 (UTC) Received: (qmail 12829 invoked from network); 15 Jan 2015 22:33:25 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 15 Jan 2015 22:33:25 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Thu, 15 Jan 2015 17:33:25 -0500 (EST) Received: (qmail 27564 invoked from network); 15 Jan 2015 22:33:24 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 15 Jan 2015 22:33:24 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 9731B1C43A7 for ; Thu, 15 Jan 2015 14:33:19 -0800 (PST) From: Mark Millard Message-Id: <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] Date: Thu, 15 Jan 2015 14:33:22 -0800 References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> To: FreeBSD PowerPC ML In-Reply-To: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 22:40:07 -0000 For a well-operating PowerMac G5 quad-core for recording over 30 = minutes, sampling about once a second, starting idle and doing "make -j = 8 buildworld buildkernel": Low value to high value (for type of value to get idea of range = expected)... dev.smusat.0.cpu_a0_diode_temp: 38.8C to dev.smusat.1.cpu_b1_diode_temp: = 68.7C dev.smu.0.fans.cpu_a_intake.rpm: 484 to dev.smu.0.fans.cpu_a_intake.rpm: = 1549 dev.smu.0.fans.cpu_a_pump.rpm: 1235 to dev.smu.0.fans.cpu_a_pump.rpm: = 2214 I put the problem PowerMac G5 quad-core in a about 56degF room in order = to try to have it run longer so I could collect more information. This = seems to have been enough to keep it somewhat below 90degC generally for = the CPU diodes over the initial 30 minutes of "make -j 8 buildworld = buildkernel". Low value to high value (for type of value to get idea of range = happening, limited to the first 30 minutes or so)... dev.smusat.0.cpu_a0_diode_temp: 38.2C to dev.smusat.0.cpu_a1_diode_temp: = 90.2C (Just one 90.2C at that point and one dev.smusat.0.cpu_a1_diode_temp: = 90.1C but a bunch of 89.[5-9]C's.) dev.smu.0.fans.cpu_a_intake.rpm: 485 to dev.smu.0.fans.cpu_a_intake.rpm: = 3184 dev.smu.0.fans.cpu_a_pump.rpm: 1254 to dev.smu.0.fans.cpu_a_pump.rpm: = 3636 Letting it run longer, however, has lead to more 90.[0-9]C's and = messages like (all but the 1st two are from after the 30 minutes): WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds = critical temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds = critical temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds = critical temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds = critical temperature (90.0 C); count=3D2 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds = critical temperature (90.0 C); count=3D3 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds = critical temperature (90.0 C); count=3D4 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds = critical temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds = critical temperature (90.0 C); count=3D2 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds = critical temperature (90.0 C); count=3D3 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds = critical temperature (90.0 C); count=3D2 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds = critical temperature (90.0 C); count=3D3 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds = critical temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds = critical temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds = critical temperature (90.0 C); count=3D2 It did automatically shut down after about 50 min. The other 3 CPU = diodes were in the range 68C to 74C or so. A1 just seems to register = hotter. It ended with the recorded sequence for a1: dev.smusat.0.cpu_a1_diode_temp: 89.2C dev.smusat.0.cpu_a1_diode_temp: 90.6C dev.smusat.0.cpu_a1_diode_temp: 90.6C dev.smusat.0.cpu_a1_diode_temp: 90.1C dev.smusat.0.cpu_a1_diode_temp: 89.9C dev.smusat.0.cpu_a1_diode_temp: 90.1C dev.smusat.0.cpu_a1_diode_temp: 90.9C dev.smusat.0.cpu_a1_diode_temp: 91.3C dev.smusat.0.cpu_a1_diode_temp: 91.1C dev.smusat.0.cpu_a1_diode_temp: 91.4C dev.smusat.0.cpu_a1_diode_temp: 91.8C dev.smusat.0.cpu_a1_diode_temp: 92.0C The high fan/pump figures recorded were: dev.smu.0.fans.cpu_b_intake.rpm: 3199 dev.smu.0.fans.cpu_a_intake.rpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_pump.rpm: 3637 These are all well above those recorded for the well-operating PowerMac = G5 quad-core. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Thu Jan 15 22:57:36 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1EB17B2 for ; Thu, 15 Jan 2015 22:57:36 +0000 (UTC) Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EEACD1B for ; Thu, 15 Jan 2015 22:57:36 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id b6so15764735lbj.8 for ; Thu, 15 Jan 2015 14:57:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=TDoGWlr/8BflbsveYBcBwKiJmEMerSL9+biscJ+/baI=; b=oc3yxv3KJIgL2KLJ8CHw6JMEKWZGYrzX6XEnGTivpiAgOPM3en8lUBZNeoHnlMMKnc DFjMt09d4XA4Zt/E+HvhszO6HJEZ4gvaR8pmL2/+kaBZ0kqXKgaRsQyQZW7NqgJja6Cw D8pI4/oPGAIFwV2WCPqibV/F523wBpfaudnXAwDTSQr9yjD3VfjymEBIGV6OUFcJYIcy 6LfjNapt0nGk0O9bPM6NaSnS+3/WvLg4Ot3hdrYp2dKrPSTsVyAAA1dZHCSw22JGAbMC r2dres6uUYylG/6fSXA1abed554/8Ch9l9wyyQrV0X2vq9J6KRf22mVzai2yaYqFrO26 NxrA== MIME-Version: 1.0 X-Received: by 10.112.8.69 with SMTP id p5mr12340827lba.97.1421362654146; Thu, 15 Jan 2015 14:57:34 -0800 (PST) Sender: chmeeedalf@gmail.com Received: by 10.25.126.214 with HTTP; Thu, 15 Jan 2015 14:57:34 -0800 (PST) In-Reply-To: <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> Date: Thu, 15 Jan 2015 14:57:34 -0800 X-Google-Sender-Auth: SkGRli3ImDaFA30ttjDAw9b4Yxk Message-ID: Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] From: Justin Hibbits To: Mark Millard Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 22:57:36 -0000 Hi Mark, All I can offer to this is a "Me Too". With OS X, running 32 python 'while True: pass' instances, core temperature never once got above 75C, but with FreeBSD, ports building repeatedly caused shutdowns. It's possible, I guess, that we are misreading the sensors, but I'm not certain at all. This happens with both of my quads. I thought maybe the LCS just needs recharged, but seeing your message, it might be a FreeBSD issue. Nathan, can you comment on this? - Justin On Thu, Jan 15, 2015 at 2:33 PM, Mark Millard wrote: > For a well-operating PowerMac G5 quad-core for recording over 30 minutes,= sampling about once a second, starting idle and doing "make -j 8 buildworl= d buildkernel": > > Low value to high value (for type of value to get idea of range expected)= ... > > dev.smusat.0.cpu_a0_diode_temp: 38.8C to dev.smusat.1.cpu_b1_diode_temp: = 68.7C > > dev.smu.0.fans.cpu_a_intake.rpm: 484 to dev.smu.0.fans.cpu_a_intake.rpm: = 1549 > > dev.smu.0.fans.cpu_a_pump.rpm: 1235 to dev.smu.0.fans.cpu_a_pump.rpm: 221= 4 > > > I put the problem PowerMac G5 quad-core in a about 56degF room in order t= o try to have it run longer so I could collect more information. This seems= to have been enough to keep it somewhat below 90degC generally for the CPU= diodes over the initial 30 minutes of "make -j 8 buildworld buildkernel". > > Low value to high value (for type of value to get idea of range happening= , limited to the first 30 minutes or so)... > > dev.smusat.0.cpu_a0_diode_temp: 38.2C to dev.smusat.0.cpu_a1_diode_temp: = 90.2C > (Just one 90.2C at that point and one dev.smusat.0.cpu_a1_diode_temp: 90.= 1C but a bunch of 89.[5-9]C's.) > > dev.smu.0.fans.cpu_a_intake.rpm: 485 to dev.smu.0.fans.cpu_a_intake.rpm: = 3184 > > dev.smu.0.fans.cpu_a_pump.rpm: 1254 to dev.smu.0.fans.cpu_a_pump.rpm: 363= 6 > > Letting it run longer, however, has lead to more 90.[0-9]C's and messages= like (all but the 1st two are from after the 30 minutes): > > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds critical= temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical= temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical= temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds critical= temperature (90.0 C); count=3D2 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds critical= temperature (90.0 C); count=3D3 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds critical= temperature (90.0 C); count=3D4 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds critical= temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds critical= temperature (90.0 C); count=3D2 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical= temperature (90.0 C); count=3D3 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical= temperature (90.0 C); count=3D2 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical= temperature (90.0 C); count=3D3 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical= temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical= temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds critical= temperature (90.0 C); count=3D2 > > It did automatically shut down after about 50 min. The other 3 CPU diodes= were in the range 68C to 74C or so. A1 just seems to register hotter. It e= nded with the recorded sequence for a1: > > dev.smusat.0.cpu_a1_diode_temp: 89.2C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 89.9C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 90.9C > dev.smusat.0.cpu_a1_diode_temp: 91.3C > dev.smusat.0.cpu_a1_diode_temp: 91.1C > dev.smusat.0.cpu_a1_diode_temp: 91.4C > dev.smusat.0.cpu_a1_diode_temp: 91.8C > dev.smusat.0.cpu_a1_diode_temp: 92.0C > > > The high fan/pump figures recorded were: > > dev.smu.0.fans.cpu_b_intake.rpm: 3199 > dev.smu.0.fans.cpu_a_intake.rpm: 3200 > dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_a_pump.rpm: 3637 > > These are all well above those recorded for the well-operating PowerMac G= 5 quad-core. > > =3D=3D=3D > Mark Millard > markmi at dsl-only.net > > > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" From owner-freebsd-ppc@FreeBSD.ORG Thu Jan 15 23:02:50 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92AD5845 for ; Thu, 15 Jan 2015 23:02:50 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 759F3DE6 for ; Thu, 15 Jan 2015 23:02:50 +0000 (UTC) Received: from aurora.physics.berkeley.edu (aurora.Physics.Berkeley.EDU [128.32.117.67]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id t0FN2kVf021235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 15 Jan 2015 15:02:47 -0800 Message-ID: <54B84716.90307@freebsd.org> Date: Thu, 15 Jan 2015 15:02:46 -0800 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVZVS1TwqDKmkUUhIjwdBGXA7xJx78hZp76Bc+VqKZFV1sofSXCX8aSo6nRyFuo+6jJurl0JXWKX5kOgZo9T03+CE1KDZnbEQ6s= X-Sonic-ID: C;wkqjngqd5BGklfCsS5uE/A== M;uE/9ngqd5BGklfCsS5uE/A== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 23:02:50 -0000 The thermal control loop in the kernel is *extremely* simple-minded, just doing a linear ramp-up of fans to match some sort of average temperature in the thermal zone. I'm sure it just isn't sufficient for these machines. Some sort of better algorithm would probably get more enthusiastic with fans when things get toward limits. You can see the algorithm in pmac_therm_manage_fans() in powermac_thermal.c. For testing purposes, you can also manipulate the fans from userland by sysctl if you disable kernel fan control (sysctl machdep.manage_fans). Note that this *also* disables thermal shutdowns, so be very careful not to set the machine on fire. -Nathan On 01/15/15 14:57, Justin Hibbits wrote: > Hi Mark, > > All I can offer to this is a "Me Too". With OS X, running 32 python > 'while True: pass' instances, core temperature never once got above > 75C, but with FreeBSD, ports building repeatedly caused shutdowns. > It's possible, I guess, that we are misreading the sensors, but I'm > not certain at all. > > This happens with both of my quads. I thought maybe the LCS just > needs recharged, but seeing your message, it might be a FreeBSD issue. > > Nathan, can you comment on this? > > - Justin > > On Thu, Jan 15, 2015 at 2:33 PM, Mark Millard wrote: >> For a well-operating PowerMac G5 quad-core for recording over 30 minutes, sampling about once a second, starting idle and doing "make -j 8 buildworld buildkernel": >> >> Low value to high value (for type of value to get idea of range expected)... >> >> dev.smusat.0.cpu_a0_diode_temp: 38.8C to dev.smusat.1.cpu_b1_diode_temp: 68.7C >> >> dev.smu.0.fans.cpu_a_intake.rpm: 484 to dev.smu.0.fans.cpu_a_intake.rpm: 1549 >> >> dev.smu.0.fans.cpu_a_pump.rpm: 1235 to dev.smu.0.fans.cpu_a_pump.rpm: 2214 >> >> >> I put the problem PowerMac G5 quad-core in a about 56degF room in order to try to have it run longer so I could collect more information. This seems to have been enough to keep it somewhat below 90degC generally for the CPU diodes over the initial 30 minutes of "make -j 8 buildworld buildkernel". >> >> Low value to high value (for type of value to get idea of range happening, limited to the first 30 minutes or so)... >> >> dev.smusat.0.cpu_a0_diode_temp: 38.2C to dev.smusat.0.cpu_a1_diode_temp: 90.2C >> (Just one 90.2C at that point and one dev.smusat.0.cpu_a1_diode_temp: 90.1C but a bunch of 89.[5-9]C's.) >> >> dev.smu.0.fans.cpu_a_intake.rpm: 485 to dev.smu.0.fans.cpu_a_intake.rpm: 3184 >> >> dev.smu.0.fans.cpu_a_pump.rpm: 1254 to dev.smu.0.fans.cpu_a_pump.rpm: 3636 >> >> Letting it run longer, however, has lead to more 90.[0-9]C's and messages like (all but the 1st two are from after the 30 minutes): >> >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds critical temperature (90.0 C); count=1 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); count=1 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); count=1 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds critical temperature (90.0 C); count=2 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=3 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds critical temperature (90.0 C); count=4 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=1 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=2 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); count=3 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); count=2 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); count=3 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); count=1 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); count=1 >> WARNING: Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds critical temperature (90.0 C); count=2 >> >> It did automatically shut down after about 50 min. The other 3 CPU diodes were in the range 68C to 74C or so. A1 just seems to register hotter. It ended with the recorded sequence for a1: >> >> dev.smusat.0.cpu_a1_diode_temp: 89.2C >> dev.smusat.0.cpu_a1_diode_temp: 90.6C >> dev.smusat.0.cpu_a1_diode_temp: 90.6C >> dev.smusat.0.cpu_a1_diode_temp: 90.1C >> dev.smusat.0.cpu_a1_diode_temp: 89.9C >> dev.smusat.0.cpu_a1_diode_temp: 90.1C >> dev.smusat.0.cpu_a1_diode_temp: 90.9C >> dev.smusat.0.cpu_a1_diode_temp: 91.3C >> dev.smusat.0.cpu_a1_diode_temp: 91.1C >> dev.smusat.0.cpu_a1_diode_temp: 91.4C >> dev.smusat.0.cpu_a1_diode_temp: 91.8C >> dev.smusat.0.cpu_a1_diode_temp: 92.0C >> >> >> The high fan/pump figures recorded were: >> >> dev.smu.0.fans.cpu_b_intake.rpm: 3199 >> dev.smu.0.fans.cpu_a_intake.rpm: 3200 >> dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 >> dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 >> dev.smu.0.fans.cpu_a_pump.rpm: 3637 >> >> These are all well above those recorded for the well-operating PowerMac G5 quad-core. >> >> === >> Mark Millard >> markmi at dsl-only.net >> >> >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@FreeBSD.ORG Fri Jan 16 07:11:35 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3033AE1 for ; Fri, 16 Jan 2015 07:11:35 +0000 (UTC) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CF8B336 for ; Fri, 16 Jan 2015 07:11:35 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id uy5so17103546obc.8 for ; Thu, 15 Jan 2015 23:11:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type; bh=fiOvTAa08tSG82VVD9pR+gq6pBjIzmxH/v2B09WCYzI=; b=B1w5naVzYEUn5dxBNcVSvu/K4ZkCCT3rTln1sCnPXuMEYx+iR4RIyrSDfH1UG7kAYQ BdYTbH2NRO2/Xk/XGmxWgyS+l8RjdiG0ukrR8MTOOLBEgAPvKXG8t0zbUlEarpXIwYpP 5uYl9mxRAQ/Y8JLLCaVfVsZzn/KieTiUeiT0XnWjP5bFV0CszzirU4bDw8QL/MeNWstd spLomRf0BIM2tYavoSx/8HfksEFqL03gu1yR9u5iPsD4KLQ9ln78qyzlhv1eeKweKAd5 e8xfNm3A11VPlpFzRLZ1OQ/2N+fhFjT1E1uApAbz5fHQ76BiSJJJlNhP4FlgoBJ2Px6b eV2A== X-Received: by 10.202.213.144 with SMTP id m138mr7904640oig.87.1421392294864; Thu, 15 Jan 2015 23:11:34 -0800 (PST) Received: from zhabar.attlocal.net (107-222-186-3.lightspeed.sntcca.sbcglobal.net. [107.222.186.3]) by mx.google.com with ESMTPSA id ck6sm1221499oeb.0.2015.01.15.23.11.33 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jan 2015 23:11:34 -0800 (PST) Date: Thu, 15 Jan 2015 23:11:29 -0800 From: Justin Hibbits To: Mark Millard Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] Message-ID: <20150115231129.1b28c8d0@zhabar.attlocal.net> In-Reply-To: <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; powerpc64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/0TFZNBK/e+.jhnGKvTzDJe7" Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 07:11:35 -0000 --MP_/0TFZNBK/e+.jhnGKvTzDJe7 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, 15 Jan 2015 14:33:22 -0800 Mark Millard wrote: > For a well-operating PowerMac G5 quad-core for recording over 30 > minutes, sampling about once a second, starting idle and doing "make > -j 8 buildworld buildkernel": > > Low value to high value (for type of value to get idea of range > expected)... > > dev.smusat.0.cpu_a0_diode_temp: 38.8C to > dev.smusat.1.cpu_b1_diode_temp: 68.7C > > dev.smu.0.fans.cpu_a_intake.rpm: 484 to > dev.smu.0.fans.cpu_a_intake.rpm: 1549 > > dev.smu.0.fans.cpu_a_pump.rpm: 1235 to dev.smu.0.fans.cpu_a_pump.rpm: > 2214 > > > I put the problem PowerMac G5 quad-core in a about 56degF room in > order to try to have it run longer so I could collect more > information. This seems to have been enough to keep it somewhat below > 90degC generally for the CPU diodes over the initial 30 minutes of > "make -j 8 buildworld buildkernel". > > Low value to high value (for type of value to get idea of range > happening, limited to the first 30 minutes or so)... > > dev.smusat.0.cpu_a0_diode_temp: 38.2C to > dev.smusat.0.cpu_a1_diode_temp: 90.2C (Just one 90.2C at that point > and one dev.smusat.0.cpu_a1_diode_temp: 90.1C but a bunch of > 89.[5-9]C's.) > > dev.smu.0.fans.cpu_a_intake.rpm: 485 to > dev.smu.0.fans.cpu_a_intake.rpm: 3184 > > dev.smu.0.fans.cpu_a_pump.rpm: 1254 to dev.smu.0.fans.cpu_a_pump.rpm: > 3636 > > Letting it run longer, however, has lead to more 90.[0-9]C's and > messages like (all but the 1st two are from after the 30 minutes): > > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds > critical temperature (90.0 C); count=1 WARNING: Current temperature > (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); > count=1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) > exceeds critical temperature (90.0 C); count=1 WARNING: Current > temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds critical temperature > (90.0 C); count=2 WARNING: Current temperature (CPU A1 DIODE TEMP: > 90.4 C) exceeds critical temperature (90.0 C); count=3 WARNING: > Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds critical > temperature (90.0 C); count=4 WARNING: Current temperature (CPU A1 > DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds > critical temperature (90.0 C); count=2 WARNING: Current temperature > (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); > count=3 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) > exceeds critical temperature (90.0 C); count=2 WARNING: Current > temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature > (90.0 C); count=3 WARNING: Current temperature (CPU A1 DIODE TEMP: > 90.1 C) exceeds critical temperature (90.0 C); count=1 WARNING: > Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical > temperature (90.0 C); count=1 WARNING: Current temperature (CPU A1 > DIODE TEMP: 90.6 C) exceeds critical temperature (90.0 C); count=2 > > It did automatically shut down after about 50 min. The other 3 CPU > diodes were in the range 68C to 74C or so. A1 just seems to register > hotter. It ended with the recorded sequence for a1: > > dev.smusat.0.cpu_a1_diode_temp: 89.2C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 89.9C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 90.9C > dev.smusat.0.cpu_a1_diode_temp: 91.3C > dev.smusat.0.cpu_a1_diode_temp: 91.1C > dev.smusat.0.cpu_a1_diode_temp: 91.4C > dev.smusat.0.cpu_a1_diode_temp: 91.8C > dev.smusat.0.cpu_a1_diode_temp: 92.0C > > > The high fan/pump figures recorded were: > > dev.smu.0.fans.cpu_b_intake.rpm: 3199 > dev.smu.0.fans.cpu_a_intake.rpm: 3200 > dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_a_pump.rpm: 3637 > > These are all well above those recorded for the well-operating > PowerMac G5 quad-core. > > === > Mark Millard > markmi at dsl-only.net Could you try the attached patch? (Untested here, my quad isn't up). It scales more exponentially, hitting full blast around the thermal midpoint. This can obviously be adjusted up or down, but should be a good starting point. We should probably also have a backoff algorithm, to keep the fans going longer after it cools, like OS X does. - Justin --MP_/0TFZNBK/e+.jhnGKvTzDJe7 Content-Type: text/x-patch Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename=pmac_therm.diff Index: sys/powerpc/powermac/powermac_thermal.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/powerpc/powermac/powermac_thermal.c (revision 277043) +++ sys/powerpc/powermac/powermac_thermal.c (working copy) @@ -137,10 +137,11 @@ nsens =3D nsens_zone =3D 0; average_excess =3D max_excess_zone =3D 0; SLIST_FOREACH(sensor, &sensors, entries) { - frac_excess =3D (sensor->last_val - + temp =3D imin(sensor->last_val, sensor->sensor->max_temp); + frac_excess =3D (temp - sensor->sensor->target_temp)*100 / (sensor->sensor->max_temp - - sensor->sensor->target_temp); + temp + 1); if (frac_excess < 0) frac_excess =3D 0; if (sensor->sensor->zone =3D=3D fan->fan->zone) { @@ -166,6 +167,7 @@ * Scale the fan linearly in the max temperature in its * thermal zone. */ + max_excess_zone =3D imin(max_excess_zone, 100); fan->fan->set(fan->fan, max_excess_zone * (fan->fan->max_rpm - fan->fan->min_rpm)/100 + fan->fan->min_rpm); --MP_/0TFZNBK/e+.jhnGKvTzDJe7-- From owner-freebsd-ppc@FreeBSD.ORG Fri Jan 16 08:50:43 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4C1C2C55 for ; Fri, 16 Jan 2015 08:50:43 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 083F7E5B for ; Fri, 16 Jan 2015 08:50:41 +0000 (UTC) Received: (qmail 22273 invoked from network); 16 Jan 2015 08:50:40 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 16 Jan 2015 08:50:40 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Fri, 16 Jan 2015 03:50:40 -0500 (EST) Received: (qmail 4234 invoked from network); 16 Jan 2015 08:50:39 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 16 Jan 2015 08:50:39 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 530871C43A7; Fri, 16 Jan 2015 00:50:38 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] From: Mark Millard In-Reply-To: <20150115231129.1b28c8d0@zhabar.attlocal.net> Date: Fri, 16 Jan 2015 00:50:37 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <272F2B8F-E134-4130-A86B-3CD5C4D20480@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> To: Justin Hibbits X-Mailer: Apple Mail (2.1993) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 08:50:43 -0000 Thanks: I'll try it. But it may be a while before I get to the experiment, possibly the = weekend. (So the following is based on 10.1-STABLE as it was when I = built it, just like the prior notes.) I've tried the experiment of letting the problem G5 quad-core sit idle = for 9+ hours. Its stable state has long been around/near: dev.smusat.0.cpu_a0_diode_temp: 61.3C dev.smusat.0.cpu_a1_diode_temp: 64.0C dev.smusat.0.cpu_a0_core_current: 11 dev.smusat.0.cpu_a1_core_current: 15 dev.smusat.1.cpu_b0_diode_temp: 45.7C dev.smusat.1.cpu_b1_diode_temp: 45.2C dev.smusat.1.cpu_b0_core_current: 13 dev.smusat.1.cpu_b1_core_current: 12 dev.smu.0.fans.cpu_a_intake.rpm: 1460 dev.smu.0.fans.cpu_b_intake.rpm: 1462 dev.smu.0.fans.cpu_a_exhaust.rpm: 1471 dev.smu.0.fans.cpu_b_exhaust.rpm: 1471 dev.smu.0.fans.cpu_a_pump.rpm: 2097 =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Jan-15, at 11:11 PM, Justin Hibbits = wrote: On Thu, 15 Jan 2015 14:33:22 -0800 Mark Millard wrote: > For a well-operating PowerMac G5 quad-core for recording over 30 > minutes, sampling about once a second, starting idle and doing "make > -j 8 buildworld buildkernel": >=20 > Low value to high value (for type of value to get idea of range > expected)... >=20 > dev.smusat.0.cpu_a0_diode_temp: 38.8C to > dev.smusat.1.cpu_b1_diode_temp: 68.7C >=20 > dev.smu.0.fans.cpu_a_intake.rpm: 484 to > dev.smu.0.fans.cpu_a_intake.rpm: 1549 >=20 > dev.smu.0.fans.cpu_a_pump.rpm: 1235 to dev.smu.0.fans.cpu_a_pump.rpm: > 2214 >=20 >=20 > I put the problem PowerMac G5 quad-core in a about 56degF room in > order to try to have it run longer so I could collect more > information. This seems to have been enough to keep it somewhat below > 90degC generally for the CPU diodes over the initial 30 minutes of > "make -j 8 buildworld buildkernel". >=20 > Low value to high value (for type of value to get idea of range > happening, limited to the first 30 minutes or so)... >=20 > dev.smusat.0.cpu_a0_diode_temp: 38.2C to > dev.smusat.0.cpu_a1_diode_temp: 90.2C (Just one 90.2C at that point > and one dev.smusat.0.cpu_a1_diode_temp: 90.1C but a bunch of > 89.[5-9]C's.) >=20 > dev.smu.0.fans.cpu_a_intake.rpm: 485 to > dev.smu.0.fans.cpu_a_intake.rpm: 3184 >=20 > dev.smu.0.fans.cpu_a_pump.rpm: 1254 to dev.smu.0.fans.cpu_a_pump.rpm: > 3636 >=20 > Letting it run longer, however, has lead to more 90.[0-9]C's and > messages like (all but the 1st two are from after the 30 minutes): >=20 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds > critical temperature (90.0 C); count=3D1 WARNING: Current temperature > (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); > count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) > exceeds critical temperature (90.0 C); count=3D1 WARNING: Current > temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds critical temperature > (90.0 C); count=3D2 WARNING: Current temperature (CPU A1 DIODE TEMP: > 90.4 C) exceeds critical temperature (90.0 C); count=3D3 WARNING: > Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds critical > temperature (90.0 C); count=3D4 WARNING: Current temperature (CPU A1 > DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds > critical temperature (90.0 C); count=3D2 WARNING: Current temperature > (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); > count=3D3 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) > exceeds critical temperature (90.0 C); count=3D2 WARNING: Current > temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature > (90.0 C); count=3D3 WARNING: Current temperature (CPU A1 DIODE TEMP: > 90.1 C) exceeds critical temperature (90.0 C); count=3D1 WARNING: > Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical > temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 > DIODE TEMP: 90.6 C) exceeds critical temperature (90.0 C); count=3D2 >=20 > It did automatically shut down after about 50 min. The other 3 CPU > diodes were in the range 68C to 74C or so. A1 just seems to register > hotter. It ended with the recorded sequence for a1: >=20 > dev.smusat.0.cpu_a1_diode_temp: 89.2C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 89.9C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 90.9C > dev.smusat.0.cpu_a1_diode_temp: 91.3C > dev.smusat.0.cpu_a1_diode_temp: 91.1C > dev.smusat.0.cpu_a1_diode_temp: 91.4C > dev.smusat.0.cpu_a1_diode_temp: 91.8C > dev.smusat.0.cpu_a1_diode_temp: 92.0C >=20 >=20 > The high fan/pump figures recorded were: >=20 > dev.smu.0.fans.cpu_b_intake.rpm: 3199 > dev.smu.0.fans.cpu_a_intake.rpm: 3200 > dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_a_pump.rpm: 3637 >=20 > These are all well above those recorded for the well-operating > PowerMac G5 quad-core. >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net Could you try the attached patch? (Untested here, my quad isn't up). It scales more exponentially, hitting full blast around the thermal midpoint. This can obviously be adjusted up or down, but should be a good starting point. We should probably also have a backoff algorithm, to keep the fans going longer after it cools, like OS X does. - Justin From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 07:08:26 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C41187D0 for ; Sat, 17 Jan 2015 07:08:26 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 7DC12C9 for ; Sat, 17 Jan 2015 07:08:26 +0000 (UTC) Received: (qmail 28762 invoked from network); 17 Jan 2015 07:08:19 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 17 Jan 2015 07:08:19 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Sat, 17 Jan 2015 02:08:19 -0500 (EST) Received: (qmail 20410 invoked from network); 17 Jan 2015 07:08:19 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Jan 2015 07:08:19 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 124781C43A4; Fri, 16 Jan 2015 23:08:12 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] From: Mark Millard In-Reply-To: <20150115231129.1b28c8d0@zhabar.attlocal.net> Date: Fri, 16 Jan 2015 23:08:17 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> To: Justin Hibbits X-Mailer: Apple Mail (2.1993) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 07:08:26 -0000 Hi. An oddity of the patch is dev.smu.0.fans.cpu_a_exhaust.rpm is almost = always zero when sampled: (This was during the "make -j 8 buildworld = buildkernel" sort of test.) dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 278 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 The b_exhaust and the intakes and the a_pump look more reasonable. =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Jan-15, at 11:11 PM, Justin Hibbits = wrote: On Thu, 15 Jan 2015 14:33:22 -0800 Mark Millard wrote: > For a well-operating PowerMac G5 quad-core for recording over 30 > minutes, sampling about once a second, starting idle and doing "make > -j 8 buildworld buildkernel": >=20 > Low value to high value (for type of value to get idea of range > expected)... >=20 > dev.smusat.0.cpu_a0_diode_temp: 38.8C to > dev.smusat.1.cpu_b1_diode_temp: 68.7C >=20 > dev.smu.0.fans.cpu_a_intake.rpm: 484 to > dev.smu.0.fans.cpu_a_intake.rpm: 1549 >=20 > dev.smu.0.fans.cpu_a_pump.rpm: 1235 to dev.smu.0.fans.cpu_a_pump.rpm: > 2214 >=20 >=20 > I put the problem PowerMac G5 quad-core in a about 56degF room in > order to try to have it run longer so I could collect more > information. This seems to have been enough to keep it somewhat below > 90degC generally for the CPU diodes over the initial 30 minutes of > "make -j 8 buildworld buildkernel". >=20 > Low value to high value (for type of value to get idea of range > happening, limited to the first 30 minutes or so)... >=20 > dev.smusat.0.cpu_a0_diode_temp: 38.2C to > dev.smusat.0.cpu_a1_diode_temp: 90.2C (Just one 90.2C at that point > and one dev.smusat.0.cpu_a1_diode_temp: 90.1C but a bunch of > 89.[5-9]C's.) >=20 > dev.smu.0.fans.cpu_a_intake.rpm: 485 to > dev.smu.0.fans.cpu_a_intake.rpm: 3184 >=20 > dev.smu.0.fans.cpu_a_pump.rpm: 1254 to dev.smu.0.fans.cpu_a_pump.rpm: > 3636 >=20 > Letting it run longer, however, has lead to more 90.[0-9]C's and > messages like (all but the 1st two are from after the 30 minutes): >=20 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds > critical temperature (90.0 C); count=3D1 WARNING: Current temperature > (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); > count=3D1 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) > exceeds critical temperature (90.0 C); count=3D1 WARNING: Current > temperature (CPU A1 DIODE TEMP: 90.2 C) exceeds critical temperature > (90.0 C); count=3D2 WARNING: Current temperature (CPU A1 DIODE TEMP: > 90.4 C) exceeds critical temperature (90.0 C); count=3D3 WARNING: > Current temperature (CPU A1 DIODE TEMP: 90.6 C) exceeds critical > temperature (90.0 C); count=3D4 WARNING: Current temperature (CPU A1 > DIODE TEMP: 90.4 C) exceeds critical temperature (90.0 C); count=3D1 > WARNING: Current temperature (CPU A1 DIODE TEMP: 90.4 C) exceeds > critical temperature (90.0 C); count=3D2 WARNING: Current temperature > (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature (90.0 C); > count=3D3 WARNING: Current temperature (CPU A1 DIODE TEMP: 90.1 C) > exceeds critical temperature (90.0 C); count=3D2 WARNING: Current > temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical temperature > (90.0 C); count=3D3 WARNING: Current temperature (CPU A1 DIODE TEMP: > 90.1 C) exceeds critical temperature (90.0 C); count=3D1 WARNING: > Current temperature (CPU A1 DIODE TEMP: 90.1 C) exceeds critical > temperature (90.0 C); count=3D1 WARNING: Current temperature (CPU A1 > DIODE TEMP: 90.6 C) exceeds critical temperature (90.0 C); count=3D2 >=20 > It did automatically shut down after about 50 min. The other 3 CPU > diodes were in the range 68C to 74C or so. A1 just seems to register > hotter. It ended with the recorded sequence for a1: >=20 > dev.smusat.0.cpu_a1_diode_temp: 89.2C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.6C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 89.9C > dev.smusat.0.cpu_a1_diode_temp: 90.1C > dev.smusat.0.cpu_a1_diode_temp: 90.9C > dev.smusat.0.cpu_a1_diode_temp: 91.3C > dev.smusat.0.cpu_a1_diode_temp: 91.1C > dev.smusat.0.cpu_a1_diode_temp: 91.4C > dev.smusat.0.cpu_a1_diode_temp: 91.8C > dev.smusat.0.cpu_a1_diode_temp: 92.0C >=20 >=20 > The high fan/pump figures recorded were: >=20 > dev.smu.0.fans.cpu_b_intake.rpm: 3199 > dev.smu.0.fans.cpu_a_intake.rpm: 3200 > dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_a_pump.rpm: 3637 >=20 > These are all well above those recorded for the well-operating > PowerMac G5 quad-core. >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net Could you try the attached patch? (Untested here, my quad isn't up). It scales more exponentially, hitting full blast around the thermal midpoint. This can obviously be adjusted up or down, but should be a good starting point. We should probably also have a backoff algorithm, to keep the fans going longer after it cools, like OS X does. - Justin From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 07:31:52 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6FE2A907 for ; Sat, 17 Jan 2015 07:31:52 +0000 (UTC) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C4EC31F for ; Sat, 17 Jan 2015 07:31:52 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id wp18so1403545obc.3 for ; Fri, 16 Jan 2015 23:31:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=QSZWhIGMLHvRCbVHXdtYOgCnzWC9HiYFGhIyAqTZkGg=; b=E4zGjehYJfVhHzTY0p47TUaPoFDQGOlH2e41zS39E9yqv63tsyaQnI2UkLQZABnBu0 V4h7mNp/B66nnjn4xrmPqk/hGGK0UrTv22A1PKBVy3fYL1q+JyRzOntdVLYDqsXFzvNx Mp7F5EUO+ysi4k9pRz3qsIS9jW2eDmshcY5hBIiuymOheZZ/T38n85ihAOd5r+it+cNF r+wFjPaFtdrEIicIOMPzZlgjSYEKNqwMiJYmhAxhPz4m9bREy3+vC71unjP5jypXs5tf 4Dl8dj6qqQmuO+SgoAums4klyKa78dZAOo72hJ+lXhAMOSTDfgJBLVJNeSXKyQzejwir PW4g== X-Received: by 10.182.181.106 with SMTP id dv10mr12172375obc.9.1421479911385; Fri, 16 Jan 2015 23:31:51 -0800 (PST) Received: from zhabar.attlocal.net (107-222-186-3.lightspeed.sntcca.sbcglobal.net. [107.222.186.3]) by mx.google.com with ESMTPSA id d6sm2851218obh.4.2015.01.16.23.31.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Jan 2015 23:31:50 -0800 (PST) Date: Fri, 16 Jan 2015 23:31:45 -0800 From: Justin Hibbits To: Mark Millard Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] Message-ID: <20150116233145.6708cc6f@zhabar.attlocal.net> In-Reply-To: <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; powerpc64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 07:31:52 -0000 On Fri, 16 Jan 2015 23:08:17 -0800 Mark Millard wrote: > Hi. > > An oddity of the patch is dev.smu.0.fans.cpu_a_exhaust.rpm is almost > always zero when sampled: (This was during the "make -j 8 buildworld > buildkernel" sort of test.) > > dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 278 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > > The b_exhaust and the intakes and the a_pump look more reasonable. > > === > Mark Millard > markmi at dsl-only.net > I think that might be simply a timing issue. I haven't seen any problems testing on my dual G5. How does the temperature look now? Do you still have overheating problems? I have an updated patch available at https://reviews.freebsd.org/D1549 , which is what I'm testing on my machine. - Justin From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 07:46:51 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1823B31 for ; Sat, 17 Jan 2015 07:46:50 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 9CE795F4 for ; Sat, 17 Jan 2015 07:46:50 +0000 (UTC) Received: (qmail 18962 invoked from network); 17 Jan 2015 07:46:49 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 17 Jan 2015 07:46:49 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Sat, 17 Jan 2015 02:46:49 -0500 (EST) Received: (qmail 16626 invoked from network); 17 Jan 2015 07:46:48 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Jan 2015 07:46:48 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 493521C4052; Fri, 16 Jan 2015 23:46:41 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] From: Mark Millard In-Reply-To: <20150116233145.6708cc6f@zhabar.attlocal.net> Date: Fri, 16 Jan 2015 23:46:47 -0800 Message-Id: <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> To: Justin Hibbits X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 07:46:51 -0000 After a while the problematic quad-core G5 automatically shut down. = b_intake.rpm was also always zero after a while. Before any patches I = never saw zeros via sysctl dev.smu . The lines were from repeating the = sysctl command about once a second and the zeros repeat second after = second, with rare exceptions over the long count of seconds. I'll see = about the updated patch. dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3195 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 3196 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3197 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3639 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3199 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 3200 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3197 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3616 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3199 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 3199 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3616 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3200 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 3201 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3551 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3200 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 3201 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3572 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3195 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 3198 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3616 ... the tail has b_exaust.rpm also 0 ...: dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3198 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3571 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3197 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3197 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3636 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3196 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3614 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3201 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3571 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3199 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3615 dev.smu.0.fans.cpu_a_intake.minrpm: 485 dev.smu.0.fans.cpu_a_intake.maxrpm: 3200 dev.smu.0.fans.cpu_a_intake.rpm: 3201 dev.smu.0.fans.cpu_b_intake.minrpm: 485 dev.smu.0.fans.cpu_b_intake.maxrpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 0 dev.smu.0.fans.cpu_a_exhaust.minrpm: 500 dev.smu.0.fans.cpu_a_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_a_exhaust.rpm: 0 dev.smu.0.fans.cpu_b_exhaust.minrpm: 500 dev.smu.0.fans.cpu_b_exhaust.maxrpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3199 dev.smu.0.fans.cpu_a_pump.minrpm: 1250 dev.smu.0.fans.cpu_a_pump.maxrpm: 3600 dev.smu.0.fans.cpu_a_pump.rpm: 3486 =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Jan-16, at 11:31 PM, Justin Hibbits = wrote: On Fri, 16 Jan 2015 23:08:17 -0800 Mark Millard wrote: > Hi. >=20 > An oddity of the patch is dev.smu.0.fans.cpu_a_exhaust.rpm is almost > always zero when sampled: (This was during the "make -j 8 buildworld > buildkernel" sort of test.) >=20 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 278 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 >=20 > The b_exhaust and the intakes and the a_pump look more reasonable. >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net >=20 I think that might be simply a timing issue. I haven't seen any problems testing on my dual G5. How does the temperature look now? Do you still have overheating problems? I have an updated patch available at https://reviews.freebsd.org/D1549 , which is what I'm testing on my machine. - Justin From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 07:47:49 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 93C52BC8 for ; Sat, 17 Jan 2015 07:47:49 +0000 (UTC) Received: from spazito3.arvixevps.com (spazito3.arvixevps.com [108.175.154.180]) (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 6DE92605 for ; Sat, 17 Jan 2015 07:47:49 +0000 (UTC) Received: from diariodoestadoms by spazito3.arvixevps.com with local (Exim 4.84) (envelope-from ) id 1YCO6n-000ClC-Ch for freebsd-ppc@freebsd.org; Fri, 16 Jan 2015 23:47:49 -0800 To: freebsd-ppc@freebsd.org Subject: Dear Beloved From: Madam Abra Jericho. Reply-To: mrsabrajerichofamily@gmail.com MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: Date: Fri, 16 Jan 2015 23:47:49 -0800 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - spazito3.arvixevps.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [505 504] / [47 12] X-AntiAbuse: Sender Address Domain - spazito3.arvixevps.com X-Get-Message-Sender-Via: spazito3.arvixevps.com: authenticated_id: diariodoestadoms/only user confirmed/virtual account not confirmed X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 07:47:49 -0000 Dear Beloved I am Madam Abra Jericho.A complete citizen of the Philippines, widow to the late Mr Mayor Jericho who was a victim of the terrorist attack in my country.We were married for 7 years without a child and my late husband was a government contractor. Before his death he had a foreign account in Germany the sum of $7.8M. This deposit was coded under a secret arrangement as a family treasure. This means that the security company does not know the real content of this trunk box which he distinguished and deposited with a security company in Germany I want you to do me a favor to receive this funds to a safe account in your country or any safer place as the beneficiary. I have plans to do investment in your country,like real estate and industrial production and I plead you take it as personal task to assist the widow like me. This is my reason for writing to you.Please if you are willing to assist me indicate your interest in replying. Yours Madam Abra Jericho From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 11:38:38 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 529A7D78 for ; Sat, 17 Jan 2015 11:38:38 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 05A2DC53 for ; Sat, 17 Jan 2015 11:38:37 +0000 (UTC) Received: (qmail 10140 invoked from network); 17 Jan 2015 11:38:36 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 17 Jan 2015 11:38:36 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Sat, 17 Jan 2015 06:38:36 -0500 (EST) Received: (qmail 32679 invoked from network); 17 Jan 2015 11:38:35 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Jan 2015 11:38:35 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 7DFE71C4052; Sat, 17 Jan 2015 03:38:33 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] From: Mark Millard In-Reply-To: <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> Date: Sat, 17 Jan 2015 03:38:33 -0800 Message-Id: <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> To: Justin Hibbits X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 11:38:38 -0000 I've now tested the new patch and strongly expect that the new code is = much better but it is not sufficient to keep the temperature down on the = problematical quad-core G5 that I've been testing via buildworld. It did = last over 30 minutes and there were no 0 rpm figures sampled for this = new code. Note: it turns out the two sysctl dumps of samples (dev.smu and = dev.smusat) are done (as a pair) more like once every 3 to 4 seconds, = not once a second. I include timestamps this time. The new code ended up keeping the intake and exhaust fans near the 3200 = maxrpm for a long time and the pump near the maxrpm 3600 too. But that = was not enough for this G5 to keep its cool. It would apparently take = giving the CPUs/cores some periodic idle time to cool down in order to = keep this G5 cool enough. (Really just cpu a1 needing such.) Over the interval below (01:45:51 to 02:13:50) no .rpm figure was = sampled as < 3100 and no pump.rpm was sampled as < 3400. Sat Jan 17 01:45:51 PST 2015 dev.smu.0.fans.cpu_a_intake.rpm: 3131 dev.smu.0.fans.cpu_b_intake.rpm: 3131 dev.smu.0.fans.cpu_a_exhaust.rpm: 3127 dev.smu.0.fans.cpu_b_exhaust.rpm: 3143 dev.smu.0.fans.cpu_a_pump.rpm: 3549 dev.smusat.0.cpu_a0_diode_temp: 59.4C dev.smusat.0.cpu_a1_diode_temp: 70.3C dev.smusat.1.cpu_b0_diode_temp: 59.1C dev.smusat.1.cpu_b1_diode_temp: 64.8C Sat Jan 17 01:45:54 PST 2015 ... Over the below range pump.rpm is sampled as < 3500 only 6 times = (each > 3400)... Sat Jan 17 02:01:46 PST 2015 dev.smu.0.fans.cpu_a_intake.rpm: 3197 dev.smu.0.fans.cpu_b_intake.rpm: 3202 dev.smu.0.fans.cpu_a_exhaust.rpm: 3200 dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 dev.smu.0.fans.cpu_a_pump.rpm: 3636 dev.smusat.0.cpu_a0_diode_temp: 67.6C dev.smusat.0.cpu_a1_diode_temp: 81.6C dev.smusat.1.cpu_b0_diode_temp: 61.0C dev.smusat.1.cpu_b1_diode_temp: 65.6C Sat Jan 17 02:01:50 PST 2015 ... The last lines that made it into the file before automatic shutdown = were ... Sat Jan 17 02:13:50 PST 2015 dev.smu.0.fans.cpu_a_intake.rpm: 3200 dev.smu.0.fans.cpu_b_intake.rpm: 3199 dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 dev.smu.0.fans.cpu_b_exhaust.rpm: 3197 dev.smu.0.fans.cpu_a_pump.rpm: 3614 dev.smusat.0.cpu_a0_diode_temp: 73.0C dev.smusat.0.cpu_a1_diode_temp: 90.9C dev.smusat.1.cpu_b0_diode_temp: 62.6C dev.smusat.1.cpu_b1_diode_temp: 67.1C Sat Jan 17 02:13:54 PST 2015 So for the last 12 minutes or so the cpu intakes, exhausts, and pump = were going basically full blast. It was not enough for my context but = likely would help some other contexts. =3D=3D=3D Mark Millard markmi at dsl-only.net ... On 2015-Jan-16, at 11:31 PM, Justin Hibbits > wrote: On Fri, 16 Jan 2015 23:08:17 -0800 Mark Millard > wrote: > Hi. >=20 > An oddity of the patch is dev.smu.0.fans.cpu_a_exhaust.rpm is almost > always zero when sampled: (This was during the "make -j 8 buildworld > buildkernel" sort of test.) >=20 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3197 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 278 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 > dev.smu.0.fans.cpu_a_exhaust.rpm: 0 >=20 > The b_exhaust and the intakes and the a_pump look more reasonable. >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net >=20 I think that might be simply a timing issue. I haven't seen any problems testing on my dual G5. How does the temperature look now? Do you still have overheating problems? I have an updated patch available at https://reviews.freebsd.org/D1549 , = which is what I'm testing on my machine. - Justin From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 16:09:34 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D64DF96 for ; Sat, 17 Jan 2015 16:09:34 +0000 (UTC) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 34D789F9 for ; Sat, 17 Jan 2015 16:09:34 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id wo20so23384602obc.13 for ; Sat, 17 Jan 2015 08:09:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type; bh=QWMHFaWu4y69JvuT4OrDccbH3Lae6ErZ5bJ2WZFQ6XI=; b=vBVbTHd0y1wNRMJo7c2PREfo53MMEhT+rmPoBuhFJwaI/AGKOE3Gv+ag6oCPZ3KKIA qQ9F52kqqiJalftd6onehaQ7OKD8T9Kf98RdqYZgxjmHjNtRod9rTVpaM37n0bJ4fPPW lJOcAA19X8Yp9llUn/v21/FnNCX+Z0AQBR8ZMdnEtAGN1pEQFHn0gRPFSBee42xdsmj4 GpzZRTuGtHqgKfV4YRMyT00tPOeD2xLVIunGnu39Eh7TDOdXwOftVBvpoFeJoW73KKNh Tl+8zIW8Z7yf1Awup2p1O1JAiZ7AgVNqEH7tPmON91zifgboB2Fdci/XFNor+p5GIe4d XDZA== X-Received: by 10.202.74.135 with SMTP id x129mr12256387oia.58.1421510973472; Sat, 17 Jan 2015 08:09:33 -0800 (PST) Received: from zhabar.attlocal.net (107-222-186-3.lightspeed.sntcca.sbcglobal.net. [107.222.186.3]) by mx.google.com with ESMTPSA id nt5sm3257906obb.26.2015.01.17.08.09.31 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Jan 2015 08:09:32 -0800 (PST) Date: Sat, 17 Jan 2015 08:09:16 -0800 From: Justin Hibbits To: Mark Millard Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] Message-ID: <20150117080916.3e321a4f@zhabar.attlocal.net> In-Reply-To: <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; powerpc64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/acTIDmWrXPrN2WZMPYIwyPF"; protocol="application/pgp-signature" Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 16:09:34 -0000 --Sig_/acTIDmWrXPrN2WZMPYIwyPF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable The new algorithm in this patch is supposed to put the fans at full throttle around the midpoint, so around 70C they should be at full blast. Have you tried the same machine under heavy load with OS X or Linux? We can keep adjusting the algorithm, as long as your machine is known to be good enough under one of those OSs. If they also overheat, there's nothing we can do, since OS X at least should run fine with heavy load, as long as the hardware can handle it. - Justin On Sat, 17 Jan 2015 03:38:33 -0800 Mark Millard wrote: > I've now tested the new patch and strongly expect that the new code > is much better but it is not sufficient to keep the temperature down > on the problematical quad-core G5 that I've been testing via > buildworld. It did last over 30 minutes and there were no 0 rpm > figures sampled for this new code. >=20 > Note: it turns out the two sysctl dumps of samples (dev.smu and > dev.smusat) are done (as a pair) more like once every 3 to 4 seconds, > not once a second. I include timestamps this time. >=20 > The new code ended up keeping the intake and exhaust fans near the > 3200 maxrpm for a long time and the pump near the maxrpm 3600 too. > But that was not enough for this G5 to keep its cool. It would > apparently take giving the CPUs/cores some periodic idle time to cool > down in order to keep this G5 cool enough. (Really just cpu a1 > needing such.) >=20 > Over the interval below (01:45:51 to 02:13:50) no .rpm figure was > sampled as < 3100 and no pump.rpm was sampled as < 3400. >=20 > Sat Jan 17 01:45:51 PST 2015 > dev.smu.0.fans.cpu_a_intake.rpm: 3131 > dev.smu.0.fans.cpu_b_intake.rpm: 3131 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3127 > dev.smu.0.fans.cpu_b_exhaust.rpm: 3143 > dev.smu.0.fans.cpu_a_pump.rpm: 3549 > dev.smusat.0.cpu_a0_diode_temp: 59.4C > dev.smusat.0.cpu_a1_diode_temp: 70.3C > dev.smusat.1.cpu_b0_diode_temp: 59.1C > dev.smusat.1.cpu_b1_diode_temp: 64.8C > Sat Jan 17 01:45:54 PST 2015 > ... Over the below range pump.rpm is sampled as < 3500 only 6 times > (each > 3400)... Sat Jan 17 02:01:46 PST 2015 > dev.smu.0.fans.cpu_a_intake.rpm: 3197 > dev.smu.0.fans.cpu_b_intake.rpm: 3202 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3200 > dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 > dev.smu.0.fans.cpu_a_pump.rpm: 3636 > dev.smusat.0.cpu_a0_diode_temp: 67.6C > dev.smusat.0.cpu_a1_diode_temp: 81.6C > dev.smusat.1.cpu_b0_diode_temp: 61.0C > dev.smusat.1.cpu_b1_diode_temp: 65.6C > Sat Jan 17 02:01:50 PST 2015 > ... The last lines that made it into the file before automatic > shutdown were ... Sat Jan 17 02:13:50 PST 2015 > dev.smu.0.fans.cpu_a_intake.rpm: 3200 > dev.smu.0.fans.cpu_b_intake.rpm: 3199 > dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 > dev.smu.0.fans.cpu_b_exhaust.rpm: 3197 > dev.smu.0.fans.cpu_a_pump.rpm: 3614 > dev.smusat.0.cpu_a0_diode_temp: 73.0C > dev.smusat.0.cpu_a1_diode_temp: 90.9C > dev.smusat.1.cpu_b0_diode_temp: 62.6C > dev.smusat.1.cpu_b1_diode_temp: 67.1C > Sat Jan 17 02:13:54 PST 2015 >=20 > So for the last 12 minutes or so the cpu intakes, exhausts, and pump > were going basically full blast. It was not enough for my context but > likely would help some other contexts. --Sig_/acTIDmWrXPrN2WZMPYIwyPF Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJUuoktAAoJEDDHhY43vi25RsUIAMMQ57C53kOFnneRhW2KixZa DJdttR7eWbrRt/IOfiubiQp36wMaUle96FxEAsimpoMnhTi1jNeGwDMRDiEdh3Ml R0BjoC/H0eN7nPd4hItfZdRI92vf5Os8lcexq7NARIk/kzKqv8V4sUojefDXPVBo VtgaC78PENX1OyxaIsdm72RgBCLI1kkhWua7AAB3ZQ9OHHk5J7CtsOaf3CNVfnCd 1T7QYGPsFD4qOEihTn4o51ADyfApJjJTHoy85WRxtwA8vLQ5ItQA+8TKE5F27z8U 08gmxitw6JlqH1G1toV9H9t4ev00I1vQ4a6SEkDpJYLIgdRl/pEB9VcGU4pA/LU= =V/mj -----END PGP SIGNATURE----- --Sig_/acTIDmWrXPrN2WZMPYIwyPF-- From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 16:35:38 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5BAF5485 for ; Sat, 17 Jan 2015 16:35:38 +0000 (UTC) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE265C5B for ; Sat, 17 Jan 2015 16:35:37 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id w61so24956190wes.1 for ; Sat, 17 Jan 2015 08:35:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=IV2YjFvTLt7U3/+Va6z9uuL/ErpL/nVbYtiOpsmImAg=; b=OIsylKfKbbgr1EuVSzuuc7pdce1ZOJ4qTYWYMUxDLN9GbtpRA6IJcZvW7xHknWs9bj M2MF+AJ1bxs8em6A0QU8EjnZte+M6FvrLk+YwBHJSnnxDD/Bt/p/sLqND2jOJ8ob7aFN +jzSDABlq2iB/iKU7nbPWsmhxH3BIqc/MHehhLaLnWpJxpQRhrBuKyC1eZVenoLs7Cdc 1yHgNrBoO3rJq6WCadmFZEqEXaZOS5zV6wuFN7fzIjSdVQoPRcjd4bYCRDuOvamvQ5Dw GoNR6HfB0IY+fvrhUcILzw7t1swVXLNdIY7FfE61dOQNE6eE4UQyWir3/AioJ62JwvPn 8eug== MIME-Version: 1.0 X-Received: by 10.194.108.9 with SMTP id hg9mr40400080wjb.68.1421512536399; Sat, 17 Jan 2015 08:35:36 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.41.136 with HTTP; Sat, 17 Jan 2015 08:35:36 -0800 (PST) In-Reply-To: <20150117080916.3e321a4f@zhabar.attlocal.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> <20150117080916.3e321a4f@zhabar.attlocal.net> Date: Sat, 17 Jan 2015 08:35:36 -0800 X-Google-Sender-Auth: RJQFIE8RwAs7VvqKcVgO6d_mVsw Message-ID: Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] From: Adrian Chadd To: Justin Hibbits Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD PowerPC ML , Mark Millard X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 16:35:38 -0000 On 17 January 2015 at 08:09, Justin Hibbits wrote: > The new algorithm in this patch is supposed to put the fans at full > throttle around the midpoint, so around 70C they should be at full > blast. > > Have you tried the same machine under heavy load with OS X or Linux? > We can keep adjusting the algorithm, as long as your machine is known > to be good enough under one of those OSs. If they also overheat, > there's nothing we can do, since OS X at least should run fine with > heavy load, as long as the hardware can handle it. Can you force introduce halt cycles to compensate for the increasing rise in temperature? -adrian > - Justin > > On Sat, 17 Jan 2015 03:38:33 -0800 > Mark Millard wrote: > >> I've now tested the new patch and strongly expect that the new code >> is much better but it is not sufficient to keep the temperature down >> on the problematical quad-core G5 that I've been testing via >> buildworld. It did last over 30 minutes and there were no 0 rpm >> figures sampled for this new code. >> >> Note: it turns out the two sysctl dumps of samples (dev.smu and >> dev.smusat) are done (as a pair) more like once every 3 to 4 seconds, >> not once a second. I include timestamps this time. >> >> The new code ended up keeping the intake and exhaust fans near the >> 3200 maxrpm for a long time and the pump near the maxrpm 3600 too. >> But that was not enough for this G5 to keep its cool. It would >> apparently take giving the CPUs/cores some periodic idle time to cool >> down in order to keep this G5 cool enough. (Really just cpu a1 >> needing such.) >> >> Over the interval below (01:45:51 to 02:13:50) no .rpm figure was >> sampled as < 3100 and no pump.rpm was sampled as < 3400. >> >> Sat Jan 17 01:45:51 PST 2015 >> dev.smu.0.fans.cpu_a_intake.rpm: 3131 >> dev.smu.0.fans.cpu_b_intake.rpm: 3131 >> dev.smu.0.fans.cpu_a_exhaust.rpm: 3127 >> dev.smu.0.fans.cpu_b_exhaust.rpm: 3143 >> dev.smu.0.fans.cpu_a_pump.rpm: 3549 >> dev.smusat.0.cpu_a0_diode_temp: 59.4C >> dev.smusat.0.cpu_a1_diode_temp: 70.3C >> dev.smusat.1.cpu_b0_diode_temp: 59.1C >> dev.smusat.1.cpu_b1_diode_temp: 64.8C >> Sat Jan 17 01:45:54 PST 2015 >> ... Over the below range pump.rpm is sampled as < 3500 only 6 times >> (each > 3400)... Sat Jan 17 02:01:46 PST 2015 >> dev.smu.0.fans.cpu_a_intake.rpm: 3197 >> dev.smu.0.fans.cpu_b_intake.rpm: 3202 >> dev.smu.0.fans.cpu_a_exhaust.rpm: 3200 >> dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 >> dev.smu.0.fans.cpu_a_pump.rpm: 3636 >> dev.smusat.0.cpu_a0_diode_temp: 67.6C >> dev.smusat.0.cpu_a1_diode_temp: 81.6C >> dev.smusat.1.cpu_b0_diode_temp: 61.0C >> dev.smusat.1.cpu_b1_diode_temp: 65.6C >> Sat Jan 17 02:01:50 PST 2015 >> ... The last lines that made it into the file before automatic >> shutdown were ... Sat Jan 17 02:13:50 PST 2015 >> dev.smu.0.fans.cpu_a_intake.rpm: 3200 >> dev.smu.0.fans.cpu_b_intake.rpm: 3199 >> dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 >> dev.smu.0.fans.cpu_b_exhaust.rpm: 3197 >> dev.smu.0.fans.cpu_a_pump.rpm: 3614 >> dev.smusat.0.cpu_a0_diode_temp: 73.0C >> dev.smusat.0.cpu_a1_diode_temp: 90.9C >> dev.smusat.1.cpu_b0_diode_temp: 62.6C >> dev.smusat.1.cpu_b1_diode_temp: 67.1C >> Sat Jan 17 02:13:54 PST 2015 >> >> So for the last 12 minutes or so the cpu intakes, exhausts, and pump >> were going basically full blast. It was not enough for my context but >> likely would help some other contexts. From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 19:45:23 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 49C39195 for ; Sat, 17 Jan 2015 19:45:23 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 EE1B6FE8 for ; Sat, 17 Jan 2015 19:45:22 +0000 (UTC) Received: (qmail 30628 invoked from network); 17 Jan 2015 19:45:20 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 17 Jan 2015 19:45:20 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Sat, 17 Jan 2015 14:45:20 -0500 (EST) Received: (qmail 3550 invoked from network); 17 Jan 2015 19:45:20 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Jan 2015 19:45:20 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id E923B1C43B3; Sat, 17 Jan 2015 11:45:15 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [more data] From: Mark Millard In-Reply-To: Date: Sat, 17 Jan 2015 11:45:18 -0800 Message-Id: <42358897-0AC2-4B35-BE01-1D4EB2CC2F47@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> <20150117080916.3e321a4f@zhabar.attlocal.net> To: Adrian Chadd , Justin Hibbits X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 19:45:23 -0000 While I mentioned forced idle time as a technical possibility I'm not so = sure that FreeBSD would want to automatically drop performance in order = to keep a machine running. In my case such would not be enough for me to = decide to continue to use the problematical quad-core G5. (I doubt that = it would be a minor amount of idle time that was required to get =E2=80=9C= make -j 8 buildworld buildkernel" or other such to work reliably on this = G5.) I will try something to put the problematical G5 under load under Mac OS = X 10.5, say 4+ copies of the HINT benchmark running concurrently if I = still have that around. But I'm not aware of a pre-existing way to see = the fans speeds, pump speeds, and other such in that context. I may only = learn if it automatically shuts down or not. For FreeBSD I was fairly = sure I'd be able to readily find such extra information (and I did). I'd say that what I reported for "01:45:51 to 02:13:50" was near = full-throttle over that time and it started at 70.3C. Looks like Justin = got it programmed with the properties he wanted. =3D=3D=3D Mark Millard markmi@dsl-only.net On 2015-Jan-17, at 08:35 AM, Adrian Chadd wrote: On 17 January 2015 at 08:09, Justin Hibbits = wrote: > The new algorithm in this patch is supposed to put the fans at full > throttle around the midpoint, so around 70C they should be at full > blast. >=20 > Have you tried the same machine under heavy load with OS X or Linux? > We can keep adjusting the algorithm, as long as your machine is known > to be good enough under one of those OSs. If they also overheat, > there's nothing we can do, since OS X at least should run fine with > heavy load, as long as the hardware can handle it. Can you force introduce halt cycles to compensate for the increasing rise in temperature? -adrian > - Justin >=20 > On Sat, 17 Jan 2015 03:38:33 -0800 > Mark Millard wrote: >=20 >> I've now tested the new patch and strongly expect that the new code >> is much better but it is not sufficient to keep the temperature down >> on the problematical quad-core G5 that I've been testing via >> buildworld. It did last over 30 minutes and there were no 0 rpm >> figures sampled for this new code. >>=20 >> Note: it turns out the two sysctl dumps of samples (dev.smu and >> dev.smusat) are done (as a pair) more like once every 3 to 4 seconds, >> not once a second. I include timestamps this time. >>=20 >> The new code ended up keeping the intake and exhaust fans near the >> 3200 maxrpm for a long time and the pump near the maxrpm 3600 too. >> But that was not enough for this G5 to keep its cool. It would >> apparently take giving the CPUs/cores some periodic idle time to cool >> down in order to keep this G5 cool enough. (Really just cpu a1 >> needing such.) >>=20 >> Over the interval below (01:45:51 to 02:13:50) no .rpm figure was >> sampled as < 3100 and no pump.rpm was sampled as < 3400. >>=20 >> Sat Jan 17 01:45:51 PST 2015 >> dev.smu.0.fans.cpu_a_intake.rpm: 3131 >> dev.smu.0.fans.cpu_b_intake.rpm: 3131 >> dev.smu.0.fans.cpu_a_exhaust.rpm: 3127 >> dev.smu.0.fans.cpu_b_exhaust.rpm: 3143 >> dev.smu.0.fans.cpu_a_pump.rpm: 3549 >> dev.smusat.0.cpu_a0_diode_temp: 59.4C >> dev.smusat.0.cpu_a1_diode_temp: 70.3C >> dev.smusat.1.cpu_b0_diode_temp: 59.1C >> dev.smusat.1.cpu_b1_diode_temp: 64.8C >> Sat Jan 17 01:45:54 PST 2015 >> ... Over the below range pump.rpm is sampled as < 3500 only 6 times >> (each > 3400)... Sat Jan 17 02:01:46 PST 2015 >> dev.smu.0.fans.cpu_a_intake.rpm: 3197 >> dev.smu.0.fans.cpu_b_intake.rpm: 3202 >> dev.smu.0.fans.cpu_a_exhaust.rpm: 3200 >> dev.smu.0.fans.cpu_b_exhaust.rpm: 3198 >> dev.smu.0.fans.cpu_a_pump.rpm: 3636 >> dev.smusat.0.cpu_a0_diode_temp: 67.6C >> dev.smusat.0.cpu_a1_diode_temp: 81.6C >> dev.smusat.1.cpu_b0_diode_temp: 61.0C >> dev.smusat.1.cpu_b1_diode_temp: 65.6C >> Sat Jan 17 02:01:50 PST 2015 >> ... The last lines that made it into the file before automatic >> shutdown were ... Sat Jan 17 02:13:50 PST 2015 >> dev.smu.0.fans.cpu_a_intake.rpm: 3200 >> dev.smu.0.fans.cpu_b_intake.rpm: 3199 >> dev.smu.0.fans.cpu_a_exhaust.rpm: 3199 >> dev.smu.0.fans.cpu_b_exhaust.rpm: 3197 >> dev.smu.0.fans.cpu_a_pump.rpm: 3614 >> dev.smusat.0.cpu_a0_diode_temp: 73.0C >> dev.smusat.0.cpu_a1_diode_temp: 90.9C >> dev.smusat.1.cpu_b0_diode_temp: 62.6C >> dev.smusat.1.cpu_b1_diode_temp: 67.1C >> Sat Jan 17 02:13:54 PST 2015 >>=20 >> So for the last 12 minutes or so the cpu intakes, exhausts, and pump >> were going basically full blast. It was not enough for my context but >> likely would help some other contexts. From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 22:04:26 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 45E8FA86 for ; Sat, 17 Jan 2015 22:04:26 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 EB285EC8 for ; Sat, 17 Jan 2015 22:04:25 +0000 (UTC) Received: (qmail 24240 invoked from network); 17 Jan 2015 22:04:24 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 17 Jan 2015 22:04:24 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Sat, 17 Jan 2015 17:04:24 -0500 (EST) Received: (qmail 5355 invoked from network); 17 Jan 2015 22:04:23 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Jan 2015 22:04:23 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id F2C791C43B4; Sat, 17 Jan 2015 14:04:18 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [Mac OS X behavior] From: Mark Millard In-Reply-To: <42358897-0AC2-4B35-BE01-1D4EB2CC2F47@dsl-only.net> Date: Sat, 17 Jan 2015 14:04:22 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <4B8426E1-B0C8-430E-BA9F-EBBF2B1B935E@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> <20150117080916.3e321a4f@zhabar.attlocal.net> <42358897-0AC2-4B35-BE01-1D4EB2CC2F47@dsl-only.net> To: Justin Hibbits , Nathan Whitehorn X-Mailer: Apple Mail (2.1993) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 22:04:26 -0000 Mac OS X 10.5 does force idle time of some form to keep core = temperatures down! My evidence is as follows. The application Temperature monitor does show me temperature records = (including graphs over time) under Mac OS X 10.5 for the G5. (No rpms.) = It displays the information as for cpu A 1&2 and cpu B 1&2 (instead of 0 = and 1). A2 is what it shows as a the hot one, matching FreeBSD's a1. I = watched with the current short-term temperature display updating once a = second (set via preferences). Once it reached around the low 90C range on A2 the temperature on A2 = started oscillating, going from the mid/low 90C's down to the = 60C's/70C's and back up again, over and over, fairly rapidly. But the = graph of the temperatures for all the cores shows all the CPU/core = temperatures as oscillating in matching timing. So I conclude that Mac OS X is doing something to give all the = CPUs/cores time to cool down as soon as any one of them gets too hot. So I do not expect Mac OS X to automatically power down, it has already = been far longer than it takes for FreeBSD to shutdown with the patched = RPM/cooling code. Menu meters shows the cores as fully used (mostly = 100%, occasional 99%). They are mostly running 6 of my double/long-long = HINT benchmark variants built various ways with parameter values input = that are designed for long runs. (HINT is memory/CPU limited until it = causes noticeable paging. But I've configured to not page with the 16GB = of RAM avilable.) So far the maximum temperature is 95.8C, and that is on A2. The next = highest core is A1 at 81.2C so far. During this oscillation A2's minumum = is 60.7C so far. There is a pattern to the drops: there is a sequence of 5 to 7 in a row = where the drop starts back up almost immediately but then there is a = longer duration with the temperatures staying down before it starts back = up again. After the longer duration drop the temperature rise is not as = rapid so it is longer until the next forced-drop. For the 5-7 in a row they tend to get somewhat closer together the = further into the sequence. It may be that the time between triggers the = longer cooling duration. The G5 has been kept busy for well over an hour, far longer than FreeBSD = did for "make -j 8 buildworld buildkernel" =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Jan-17, at 11:45 AM, Mark Millard = wrote: While I mentioned forced idle time as a technical possibility I'm not so = sure that FreeBSD would want to automatically drop performance in order = to keep a machine running. In my case such would not be enough for me to = decide to continue to use the problematical quad-core G5. (I doubt that = it would be a minor amount of idle time that was required to get =E2=80=9C= make -j 8 buildworld buildkernel" or other such to work reliably on this = G5.) I will try something to put the problematical G5 under load under Mac OS = X 10.5, say 4+ copies of the HINT benchmark running concurrently if I = still have that around. But I'm not aware of a pre-existing way to see = the fans speeds, pump speeds, and other such in that context. I may only = learn if it automatically shuts down or not. For FreeBSD I was fairly = sure I'd be able to readily find such extra information (and I did). I'd say that what I reported for "01:45:51 to 02:13:50" was near = full-throttle over that time and it started at 70.3C. Looks like Justin = got it programmed with the properties he wanted. =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Jan-17, at 08:35 AM, Adrian Chadd wrote: On 17 January 2015 at 08:09, Justin Hibbits = wrote: > The new algorithm in this patch is supposed to put the fans at full > throttle around the midpoint, so around 70C they should be at full > blast. >=20 > Have you tried the same machine under heavy load with OS X or Linux? > We can keep adjusting the algorithm, as long as your machine is known > to be good enough under one of those OSs. If they also overheat, > there's nothing we can do, since OS X at least should run fine with > heavy load, as long as the hardware can handle it. Can you force introduce halt cycles to compensate for the increasing rise in temperature? -adrian From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 22:20:18 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B1C4104 for ; Sat, 17 Jan 2015 22:20:18 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 C0D9FFE0 for ; Sat, 17 Jan 2015 22:20:17 +0000 (UTC) Received: (qmail 12856 invoked from network); 17 Jan 2015 22:20:16 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 17 Jan 2015 22:20:16 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Sat, 17 Jan 2015 17:20:16 -0500 (EST) Received: (qmail 26974 invoked from network); 17 Jan 2015 22:20:15 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Jan 2015 22:20:15 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id AC8EB1C43B6; Sat, 17 Jan 2015 14:20:10 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [Mac OS X behavior] From: Mark Millard In-Reply-To: <4B8426E1-B0C8-430E-BA9F-EBBF2B1B935E@dsl-only.net> Date: Sat, 17 Jan 2015 14:20:14 -0800 Message-Id: <592299C1-C92D-4CB3-8C4A-DB12FF7D102B@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> <20150117080916.3e321a4f@zhabar.attlocal.net> <42358897-0AC2-4B35-BE01-1D4EB2CC2F47@dsl-only.net> <4B8426E1-B0C8-430E-BA9F-EBBF2B1B935E@dsl-only.net> To: Justin Hibbits , Nathan Whitehorn X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 22:20:18 -0000 I've included a picture of the graph of core temperatures from Mac OS X, = spanning a little over 6 minutes. The core temperature plots are colored = non-black. The "5 to 7" that I mentioned below is more like "3 to 12" over this = time interval. =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Jan-17, at 02:04 PM, Mark Millard = wrote: Mac OS X 10.5 does force idle time of some form to keep core = temperatures down! My evidence is as follows. The application Temperature monitor does show me temperature records = (including graphs over time) under Mac OS X 10.5 for the G5. (No rpms.) = It displays the information as for cpu A 1&2 and cpu B 1&2 (instead of 0 = and 1). A2 is what it shows as a the hot one, matching FreeBSD's a1. I = watched with the current short-term temperature display updating once a = second (set via preferences). Once it reached around the low 90C range on A2 the temperature on A2 = started oscillating, going from the mid/low 90C's down to the = 60C's/70C's and back up again, over and over, fairly rapidly. But the = graph of the temperatures for all the cores shows all the CPU/core = temperatures as oscillating in matching timing. So I conclude that Mac OS X is doing something to give all the = CPUs/cores time to cool down as soon as any one of them gets too hot. So I do not expect Mac OS X to automatically power down, it has already = been far longer than it takes for FreeBSD to shutdown with the patched = RPM/cooling code. Menu meters shows the cores as fully used (mostly = 100%, occasional 99%). They are mostly running 6 of my double/long-long = HINT benchmark variants built various ways with parameter values input = that are designed for long runs. (HINT is memory/CPU limited until it = causes noticeable paging. But I've configured to not page with the 16GB = of RAM avilable.) So far the maximum temperature is 95.8C, and that is on A2. The next = highest core is A1 at 81.2C so far. During this oscillation A2's minumum = is 60.7C so far. There is a pattern to the drops: there is a sequence of 5 to 7 in a row = where the drop starts back up almost immediately but then there is a = longer duration with the temperatures staying down before it starts back = up again. After the longer duration drop the temperature rise is not as = rapid so it is longer until the next forced-drop. For the 5-7 in a row they tend to get somewhat closer together the = further into the sequence. It may be that the time between triggers the = longer cooling duration. The G5 has been kept busy for well over an hour, far longer than FreeBSD = did for "make -j 8 buildworld buildkernel" =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 17 22:25:56 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A5BDF20A for ; Sat, 17 Jan 2015 22:25:56 +0000 (UTC) Received: from asp.reflexion.net (outbound-240.asp.reflexion.net [69.84.129.240]) (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 28AA611B for ; Sat, 17 Jan 2015 22:25:55 +0000 (UTC) Received: (qmail 4933 invoked from network); 17 Jan 2015 22:25:54 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 17 Jan 2015 22:25:54 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.0) with SMTP; Sat, 17 Jan 2015 17:25:54 -0500 (EST) Received: (qmail 19279 invoked from network); 17 Jan 2015 22:25:54 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Jan 2015 22:25:54 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 737AF1C43B3; Sat, 17 Jan 2015 14:25:49 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [Mac OS X behavior] From: Mark Millard In-Reply-To: <592299C1-C92D-4CB3-8C4A-DB12FF7D102B@dsl-only.net> Date: Sat, 17 Jan 2015 14:25:52 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <8E81058D-DFF8-4C54-8FA2-1202CC03081D@dsl-only.net> References: <42CF1E40-5BD5-4B00-86E9-C62AEB9B8B93@dsl-only.net> <15A6D627-9DC7-48AF-B133-94980AFCE46A@dsl-only.net> <20150115231129.1b28c8d0@zhabar.attlocal.net> <0631235D-A505-4C37-87D7-6F46A14552AB@dsl-only.net> <20150116233145.6708cc6f@zhabar.attlocal.net> <31331F84-63CC-48B7-81B5-E70A22E88CB7@dsl-only.net> <604BAA0A-FD15-4310-88B2-DFEE9988D1EB@dsl-only.net> <20150117080916.3e321a4f@zhabar.attlocal.net> <42358897-0AC2-4B35-BE01-1D4EB2CC2F47@dsl-only.net> <4B8426E1-B0C8-430E-BA9F-EBBF2B1B935E@dsl-only.net> <592299C1-C92D-4CB3-8C4A-DB12FF7D102B@dsl-only.net> To: Justin Hibbits , Nathan Whitehorn X-Mailer: Apple Mail (2.1993) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 22:25:56 -0000 Looks like only Justin and Nathan got the graph (since I directly sent = the message to them but the mail list stripped it). =3D=3D=3D Mark Millard markmi T dsl-only.net On 2015-Jan-17, at 02:20 PM, Mark Millard = wrote: I've included a picture of the graph of core temperatures from Mac OS X, = spanning a little over 6 minutes. The core temperature plots are colored = non-black. The "5 to 7" that I mentioned below is more like "3 to 12" over this = time interval. =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Jan-17, at 02:04 PM, Mark Millard = wrote: Mac OS X 10.5 does force idle time of some form to keep core = temperatures down! My evidence is as follows. The application Temperature monitor does show me temperature records = (including graphs over time) under Mac OS X 10.5 for the G5. (No rpms.) = It displays the information as for cpu A 1&2 and cpu B 1&2 (instead of 0 = and 1). A2 is what it shows as a the hot one, matching FreeBSD's a1. I = watched with the current short-term temperature display updating once a = second (set via preferences). Once it reached around the low 90C range on A2 the temperature on A2 = started oscillating, going from the mid/low 90C's down to the = 60C's/70C's and back up again, over and over, fairly rapidly. But the = graph of the temperatures for all the cores shows all the CPU/core = temperatures as oscillating in matching timing. So I conclude that Mac OS X is doing something to give all the = CPUs/cores time to cool down as soon as any one of them gets too hot. So I do not expect Mac OS X to automatically power down, it has already = been far longer than it takes for FreeBSD to shutdown with the patched = RPM/cooling code. Menu meters shows the cores as fully used (mostly = 100%, occasional 99%). They are mostly running 6 of my double/long-long = HINT benchmark variants built various ways with parameter values input = that are designed for long runs. (HINT is memory/CPU limited until it = causes noticeable paging. But I've configured to not page with the 16GB = of RAM avilable.) So far the maximum temperature is 95.8C, and that is on A2. The next = highest core is A1 at 81.2C so far. During this oscillation A2's minumum = is 60.7C so far. There is a pattern to the drops: there is a sequence of 5 to 7 in a row = where the drop starts back up almost immediately but then there is a = longer duration with the temperatures staying down before it starts back = up again. After the longer duration drop the temperature rise is not as = rapid so it is longer until the next forced-drop. For the 5-7 in a row they tend to get somewhat closer together the = further into the sequence. It may be that the time between triggers the = longer cooling duration. The G5 has been kept busy for well over an hour, far longer than FreeBSD = did for "make -j 8 buildworld buildkernel" =3D=3D=3D Mark Millard markmi at dsl-only.net