I have spent considerable hours searching forums and googling. I have yet to find out what "lm-sensors acpitz-virtual-0 Adapter: Virtual device temp1:" is actually looking at. I have an Abit IP35 motherboard with Ubuntu 9.04 installed. Here is the output from sensors:

acpitz-virtual-0
Adapter: Virtual device
temp1: +47.0°C (crit = +90.0°C) <--- Keeps overheating to 121 C and shutting the computer down.

w83627dhg-isa-0290
Adapter: ISA adapter
VCore: +1.13 V (min = +0.00 V, max = +1.74 V)
in1: +6.34 V (min = +6.97 V, max = +3.38 V) ALARM <--My bios isn't set for this high voltage. Don't know why it is reading this high.
AVCC: +3.26 V (min = +2.11 V, max = +0.58 V) ALARM
3VCC: +3.26 V (min = +1.97 V, max = +2.56 V) ALARM
in4: +1.19 V (min = +0.00 V, max = +0.51 V) ALARM
in5: +1.25 V (min = +1.22 V, max = +0.53 V) ALARM
in6: +5.07 V (min = +4.92 V, max = +0.46 V) ALARM
VSB: +3.22 V (min = +0.00 V, max = +0.53 V) ALARM
VBAT: +3.17 V (min = +0.30 V, max = +2.88 V) ALARM
Case Fan: 0 RPM (min = 340 RPM, div = 128) ALARM
CPU Fan: 1534 RPM (min = 332 RPM, div = 16)
Aux Fan: 0 RPM (min = 340 RPM, div = 128) ALARM
fan4: 0 RPM (min = 340 RPM, div = 128) ALARM
fan5: 0 RPM (min = 2109 RPM, div = 128) ALARM
Sys Temp: +40.0°C (high = +16.0°C, hyst = -124.0°C) ALARM sensor = thermistor
CPU Temp: +47.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
AUX Temp: +42.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +0.000 V

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +42.0°C (high = +82.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +38.0°C (high = +82.0°C, crit = +100.0°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2: +44.0°C (high = +82.0°C, crit = +100.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +37.0°C (high = +82.0°C, crit = +100.0°C)

Virtual Device Temp 1 keeps going up to 121 degrees and the computer shuts down. None of the others overheat. Also, my bios does not show my voltages to be set like it lists above. The bios in the motherboard is the latest from Abit. Anyone have any ideas about what is going on???

A couple thoughts:

1)
It looks like (based on the temp value alone) a clone of the line:

CPU Temp: +47.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode

To break the item down: acpitz-virtual-0 = ACPI Thermal Zone (virtual) Device0

I'd say it's the ACPI system's method of monitoring the CPU temp. Note that the data may or may not be entirely accurate, and also, based on:

Sys Temp: +40.0°C (high = +16.0°C, hyst = -124.0°C) ALARM sensor = thermistor which indicates a thoroughly ridiculous hysteresis value of -124.0 'C you may need to do a little bit of adjusting on your sensors.conf file, though adjustment may or may not affect that particular virtual 'device'.

The ACPITZ data has been known to be the cause of the exact situation you are experiencing, on other machines too, though usually laptop machines. FWIW, at your discretion, you can disable the TZ functionality. One way to do so is via the kernel config.

Sasha

Thank you for the quick reply.

When my tem1 shows 121 degrees C there is no other temp reading on the sensor list that is the same. Later, when my computer temp reaches 121 again I will copy and past the entire sensor output again so you can see this. I believe it is either a separate 'device' from those listed below or the sensor itself is defective. I will not be able to cool the affected device if I can't find it. I have taken canned "Dust Remover" and tried to cool different areas of the motherboard to see if I could get a response. So far I have been unable to locate it.

It's worth noting that depending on exactly how each particular device is read, and configured, the values each of them shows may not scale identically as the temp changes; what I mean is, for example, depending on any computations/formulae you have configured in your sensors.conf file, you can pretty much make any one of the various sensors display very accurate, or totally out-of-whack, values; and if two readings are being obtained from the same sensor, but being computed differently, their respective values will differ.

So for further example, sensor ABC gives a reading of 40, and goes up one degree at a time; but the same sensor ABC being read/calculated by another means, might go up by 2 degrees for every ONE degree that ABC actually rises.

Have you by chance looked on lm_sensors list of known configurations, to see if there's a similar motherboard listed as yours, with a working configuration file?

Please do provide the next output again when the temp claims to be over heating.

Sasha

http://lists.lm-sensors.org/pipermai...er/021663.html

The above is older (2007) but you may find it an interesting read. I googled "Abit IP35 lm_sensors" and got lots of results.

Cheers,
Sasha

Hello Maintech

Please post your sensors3.conf file.

Places to look for a sensors3.conf file for your motherboard (or a similar one can be a good starting point): http://www.lm-sensors.org/wiki/Configurations, http://lm-sensors-db.berlios.de/ http://www.lathspell.de/linux/lm_sensors/ and http://khali.linux-fr.org/devel/lm-sensors/.

Generally motherboard manufacturers provide BIOS that shows everything that the hardware measures. There may be a clue about what acpitz-virtual-0 is in the BIOS' system monitoring screens.

Best

Charles

I will attach the file since it is too large to post. It seems from what I have been reading, this "temp1" is the 'motherboard temperature'. Where on the motherboard IS this being monitored??

Attached Files

	sensor3.conf.txt (69.8 KB, 350 views)
	sensors.conf.txt (83.6 KB, 155 views)

I haven't researched your exact motherboard nor examined the attached files, but meanwhile, here's some more general info/questions:

1 -- First, which version of lm_sensors are you using? An older one, that uses sensors.conf, or a newer one that uses sensors[B]3[B].conf? (You've attached one of each file)

2 - Catkin is right: there's usually a BIOS screen where you can roughly compare your lm_sensors data against what the BIOS is showing. It(the data) tends to be not identical, because the CPU/machine is under less load when running the BIOS, compared to when it's running a loaded OS, which can make temperatures a little higher when the OS is running.

Also, depending on the BIOS, not every sensor/reading may be present in the BIOS:

Example 2a) on my desktop machine, the BIOS does not show 1 of the 4 fans, and does not show my CPU core(s) temps, only a single CPU temp (the socket temp I believe)

Example 2b) I upgraded the BIOS on my 10-year-old PII-333MHz firewall machine a while back, and now, the BIOS doesn't even have a hardware data page with temps or fans where previously it did.. Weird.

3- In the case of a "system temp" or a "motherboard" temp, this is sometimes one of two or more possibilities: it can be an actual sensor on the motherboard somewhere, which is reporting the ambient temperature of the board or the inside of the box; OR
3b- it can be the "CPU Socket temp" or "die temp" which is a diode (often) underneath the CPU, which roughly tells the temperature of the CPU socket or "CPU die" (the block of metal/ceramic or whatever, that the CPU core is housed in) as opposed to the core-temps themselves (the reading from INSIDE the CPU's guts). Understandably, the die-temp/socket-temp should be lower than the core temps by 5-10'C or more, and should react MUCH slower to system load than the core temps.

Sasha

Thanks I'm sorry -- I have studied it (the sensors3.conf one) and can't help

I have finally determined what the issue was. The temperature being monitored was at the base of the cpu. I believe that was mentioned in an earlier post. My bios doesn't show it. After much changing of bios settings and checking temps and checking hardware, I finally determined the source of the issue and now all is well. There was an airflow issue around the base of the cpu. The cpu heat sink and cpu core temps were just fine. The temp of the cpu as a whole (single sensor for cpu) was fine. But the base wasn't cooling and it has it's own temp sensor. I repositioned some things and re-directed air flow to go around the base. It worked so well I have been able to overclock the system considerably and all heat readings (including Temp1) are all well within setpoints.

Thank YOU ALL for your assistance. It was your suggestions that gave me ideas of where to check. I may not have found it if not for ALL your help.