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? Thanks. -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090908/64f9ea31/attachment.pgp
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? > > Thanks. > > -- > 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 >
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. -- Alexander Motin
on 09/09/2009 18:38 Kurt Jaeger said the following:> Hi! > > [on coretemp module, Alexander Motin <mav@FreeBSD.org> wrote:] >> AFAIR C2D supports three protection technologies. When CPU is hot, it >> starts reducing frequency (multiplier) and voltage, alike to IEST. If it >> is insufficient, it starts to skip core cycles, alike to TCC. If it is >> still insufficient and temperature rises above about 100C, emergency >> shutdown happens. > > Cool. I just tested coretemp on some CPU here, works very nice! > > Any information on what can be done with AMD CPUs with respect > to temperature monitoring ?amdtemp(4) ? :-) -- Andriy Gapon
Le Mar 8 sep 09 ? 14:39:36 +0200, Daniel O'Connor <doconnor@gsoft.com.au> ?crivait?:> 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?Have you tried the ports sysutils/lmmon and sysutils/wmlmmon? Some others exist under /usr/ports/sysutils, but I don't use them. Regards, -- Th. Thomas. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090909/d4fec293/attachment.pgp