Date: Sat, 17 Jan 2015 08:09:16 -0800 From: Justin Hibbits <chmeeedalf@gmail.com> To: Mark Millard <markmi@dsl-only.net> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <markmi@dsl-only.net> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150117080916.3e321a4f>