On Saturday, 29 ×January 2005 16:26, Yedidyah Bar-David wrote: > On Sat, Jan 29, 2005 at 03:23:39PM +0200, Ira Abramov wrote: > > Howdie people, > > > > I have a new machine running just under a month at the hosting farm at > > Nezeq Benleumi. it's a generic 1U rigged by "5 exits" which I thought > > was well ventilated, however the following messages started appearing in > > the logs and on the console: > > > > Message from [EMAIL PROTECTED] at Sat Jan 29 15:03:22 2005 ... > > jenna kernel: CPU1: Temperature above threshold > > > > Message from [EMAIL PROTECTED] at Sat Jan 29 15:03:22 2005 ... > > jenna kernel: CPU0: Temperature above threshold > > > > Message from [EMAIL PROTECTED] at Sat Jan 29 15:03:22 2005 ... > > jenna kernel: CPU0: Running in modulated clock mode > > > > Message from [EMAIL PROTECTED] at Sat Jan 29 15:03:22 2005 ... > > jenna kernel: CPU1: Running in modulated clock mode > > > > (it's a hyperthreading P4, obviously) > > These seem to come directly from the CPU, not from your w83627hf. > IIRC there are tools that can show the actual readings from the CPU > itself, don't remember names. Try searching freshmeat for sensor, > temperature, etc. > > As far as I know, lm-sensors never reads this. It only reads data > from the relevant chip on the motherboard. > > > searching around google tells me this is a cooling problem, but... (and > > there are several buts!) > > > > 1. nobody says if it is a big problem or a little problem. > > You can always stick a non-computerized thermometer there and see > what the actual temperature is. Then look up the specs at Intel (I > think a P4 shouldn't suffer much from up to around 60-70deg C) and > decide how bad this is.
Most thermometers out there are for liquid or tissue measurments, not surface ones. Some multimeter kits are sold with an optional thermistor you can stick anywhere with a drop of thermoconducting compound. As an added bonus you can check the voltage with it. :) Or you can buy a thermistor off the local radio store, but then you'll have to make a calibration table (using hot water and "photo" quicksilver thermometer). > > 2. nobody says if this is the kernel just reporting me what happend to > > the CPU or the kernel deciding to switch the CPU to a "modulated clock > > mode" > > I also don't know. > > > 3. I tend not to trust the way the kernel measures the CPU temp since > > the numbers I got from the output of "sensors" never made much sense, > > and the CPU is not under any serious stress in there. > > As I said, I do not think it's the same source. > > > chopped out the memory module reports and fitting line length to a > > readable Email length, this is the output of "sensors": > > > > w83627hf-isa-0290 > > Adapter: ISA adapter > > VCore 1: +0.02 V (min = +1.95 V, max = +2.16 V) > > VCore 2: +1.18 V (min = +1.95 V, max = +2.16 V) > > +3.3V: +3.41 V (min = +3.14 V, max = +3.47 V) > > +5V: +5.16 V (min = +4.76 V, max = +5.24 V) > > +12V: +12.28 V (min = +10.82 V, max = +13.19 V) > > -12V: +1.62 V (min = -13.18 V, max = -10.80 V) > > -5V: +0.43 V (min = -5.25 V, max = -4.75 V) > > V5SB: +5.64 V (min = +4.76 V, max = +5.24 V) > > VBat: +3.22 V (min = +2.40 V, max = +3.60 V) > > fan1: 0 RPM (min = 675000 RPM, div = 2) > > fan2: 0 RPM (min = 96428 RPM, div = 2) > > fan3: 7336 RPM (min = 1318 RPM, div = 8) > > temp1: +127 C (high =-118 C, hyst = +1 C) sensor = thermistor > > temp2: +116.5 C (high = +80 C, hyst =+75 C) sensor = diode ALARM > > temp3: +127.0 C (high = +80 C, hyst =+75 C) sensor = thermistor ALARM > > vid: +2.050 V (VRM Version 8.2) > > alarms: Chassis intrusion detection ALARM Hmm. Are you sure the chip is correct? sensors-detect? The temperature values are not making any sense. Are you sure there is a connection between the sensors and the chip or are there any sensor at all? 127 C is too suspicious a number. There are a number of sensors that can come with that chip. Maybe the type in sensors.conf is wrong. > Are you sure the entirety of [lm-sensors modules, sensors program > and libraries, /etc/sensors.conf] are of the same version and > up-to-date? You should realize that the modules report the raw > data they get from the sensors, and this gets translated to what > you see here according to rules in /etc/sensors.conf. sensors-detect should give out the section of http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/etc/sensors.conf.eg you copy to your sensors.conf. Choosing the sensor type according to the manual is up to you. :) > You should find the raw data somewhere under /sys. Try > find /sys -iname "*w83627*" > In a specific machine here, which is i2c - not isa, it's under > /sys/bus/i2c/drivers/lm85/. > > A simple way to see how close to reality this is (or even send a > fix to lm-sensors if needed), assuming you can have some downtime, > is to look at the BIOS's report at various actual temperatures (e.g. > using a good ventilator to cool everything a lot, look at both sensors > and BIOS while it's getting warmer and finding the connection, which > should be linear). -- Sincerely Yours, Vasiliev Michael NP: XMMS is not loaded. ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
