From owner-freebsd-ppc@FreeBSD.ORG Sun Jan 18 07:28:41 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 A4FC76B8 for ; Sun, 18 Jan 2015 07:28:41 +0000 (UTC) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::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 2F13079A for ; Sun, 18 Jan 2015 07:28:41 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id r20so3046770wiv.4 for ; Sat, 17 Jan 2015 23:28:39 -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=dqWGqJ63FKGO93F146U9b3ZdS/p3zYp7MuleXCkSQjU=; b=ybRVnM9yF6UvR32vVyp9qaq6wFtB663wfgzGODl/sJL92INdanwApwDX+b1+la6Bf2 WAagVArJOxmKBZEpacbUz088CFAmkycxsubJQittkRm8rqQ3eY+TvcV6AoCvaqxTQFNS zwZEA19rAJZD6aGn/jzAIsVUDxgUDAfPS8TtZSo4ivhFT8OcYyLaYobanIPwLT0P45Qk P8ppXI4Io7xd9tcQxypvuublaHwXxQ1mc1uJ3NuxpSZmzCa6947c1pKx6T2ZhnENWlSG 3zfkg0WDUWE1v0/g/sJagttMnk+qyIFVyGLj1hwRIRtXouGq+pC3zxgdboDN2lGZsjtS KB4A== MIME-Version: 1.0 X-Received: by 10.180.7.198 with SMTP id l6mr22784521wia.26.1421566119614; Sat, 17 Jan 2015 23:28:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.41.136 with HTTP; Sat, 17 Jan 2015 23:28:39 -0800 (PST) In-Reply-To: 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> <8E81058D-DFF8-4C54-8FA2-1202CC03081D@dsl-only.net> Date: Sat, 17 Jan 2015 23:28:39 -0800 X-Google-Sender-Auth: X4lhSu2-dVAINWjGCPNoflTlin8 Message-ID: Subject: Re: PowerMac G5 quad-core, CPU A1 DIODE TEMP: 90.8 C (for example): How to handle? [Mac OS X behavior] 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: Sun, 18 Jan 2015 07:28:41 -0000 Intel CPUs do the same thing these days. They do it without the OS assistance. So maybe we need to add a thermal throttling module that inserts a fixed number of HLT cycles with a timer, or something along those lines, to try and enforce some form of processing duty cycle. (And there'll be a minimum length to stay asleep regardless; as entering sleep states does consume juice.) -adrian On 17 January 2015 at 21:36, Justin Hibbits wrote: > I noticed on my quad running OS X spins up the fans all the way down at > 55C. Perhaps you can try that, set the initial multiplier to 300 or more. > I can add a sysctl to change the multiplier, if that would help people. > > -Justin > On Jan 17, 2015 2:25 PM, "Mark Millard" wrote: > >> Looks like only Justin and Nathan got the graph (since I directly sent the >> message to them but the mail list stripped it). >> >> === >> 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. >> >> >> >> >> === >> 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" >> >> === >> 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"