Date: Wed, 9 Sep 2009 17:47:12 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Alexander Motin <mav@freebsd.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Detecting CPU throttling on over temperature Message-ID: <200909091747.19696.doconnor@gsoft.com.au> In-Reply-To: <4AA72D4D.9080505@FreeBSD.org> References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2079163.TrhI4ZJgtH Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Alexander Motin wrote: > Daniel O'Connor wrote: > > On Wed, 9 Sep 2009, Alexander Motin wrote: > >> Daniel O'Connor wrote: > >>> I recently discovered a system where the floppy drive cable was > >>> intermittently fouling the CPU fan - I believe this caused the > >>> CPU to overheat and then get throttled by the BIOS. > >>> > >>> Does anyone know if it is possible to determine if this is the > >>> case? ie is there a way to be informed if throttling has > >>> occurred? > >> > >> Theoretically it is possible. I know off-topic tool reporting > >> this. Also you can just monitor CPU temperature, depending on CPU > >> type. > > > > Monitoring CPU temperature is a bit difficult, there are a lack of > > tools (although I have some code it's not complete). > > There indeed problems with MB monitoring, as it is non-standard. But > modern CPUs also include on-chip thermal sensors. For Core2Duo family > coretemp module works fine and precisely. Ahh coretemp, I had forgotten about that. I did a test on the bench (on a 7.2 system) here and realised that I=20 can't actually detect throttling. coretemp reported 72 & 78C but the=20 frequency was still 2933MHz. I am pretty sure it would be throttling but I think that works by=20 maintaining the frequency but stalling the CPU some percentage of the=20 time. I have p4tcc loaded (in GENERIC) but it doesn't show up, I only=20 get.. dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=3D\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 2933 dev.cpu.0.freq_levels: 2933/35000 2566/30625 2199/26250 1833/21875=20 1466/17500 1099/13125 733/8750 366/4375 dev.cpu.0.cx_supported: C1/0 C2/85 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% dev.cpu.0.temperature: 44 dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=3D\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/0 C2/85 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% dev.cpu.1.temperature: 36 I see some odd results if I disable the fan while running 'dd=20 if=3D/dev/zero bs=3D128k count=3D5000 | md5' in a loop. The throughput seem= s=20 to remain the same (odd) but the CPU idle time goes up when it gets=20 hot. > > The problem is that the CPU temperature is only a proxy > > measurement, I would much prefer to be told directly the BIOS is > > throttling rather than guess :) > > While ACPI could implement thermal throttling, AFAIK TM1/TM2 > technologies of P4 and above families are working just in CPU > hardware. BIOS only initializes them. OK. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2079163.TrhI4ZJgtH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKp2SP5ZPcIHs/zowRAvyTAJ9ATYlx0wWM0LhhK4VkLl6a3NnSwwCfS5sX gkMUWYIRrXYwALtpSvxJuIg= =dGDv -----END PGP SIGNATURE----- --nextPart2079163.TrhI4ZJgtH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909091747.19696.doconnor>