Date: Wed, 9 Sep 2009 03:54:38 +1000 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Henrik Friedrichsen <hrkfdn@gmail.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Detecting CPU throttling on over temperature Message-ID: <20090909030624.Y89278@sola.nimnet.asn.au> In-Reply-To: <cbbf66600909080652qa6a90cckff95e6d18561be24@mail.gmail.com> References: <200909082209.37454.doconnor@gsoft.com.au> <cbbf66600909080652qa6a90cckff95e6d18561be24@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 8 Sep 2009, Henrik Friedrichsen wrote: > I don't know whether there is a more convenient way, but you could > definitely check the current CPU frequency to detect whether it > changed from the previous one or not. There are several ways to this, > depends on the CPU. You can try messing with cpufreq(4). > > On Tue, Sep 8, 2009 at 2:39 PM, Daniel O'Connor<doconnor@gsoft.com.au> wrote: > > Hi, > > 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? Might be easier to hack powerd.c as an existing pretty lightweight way of monitoring CPU freq (to log or signal on detected freq lowered by throttling, say?) even if you don't need/want it to actually vary freq according to load, eg setting idle/busy shift factors to 'never/always'? cheers, Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090909030624.Y89278>