Date: Thu, 15 Jan 2015 14:57:34 -0800 From: Justin Hibbits <jrh29@alumni.cwru.edu> 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: <CAHSQbTB0wkTT93Y5AueePERxAfVNLbhQbeAk9uQh3R7kC1bdpQ@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <markmi@dsl-only.net> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHSQbTB0wkTT93Y5AueePERxAfVNLbhQbeAk9uQh3R7kC1bdpQ>