* [lm-sensors] CPU temperatures not being showed?
@ 2014-02-15 9:28 Muhammad Umair
2014-02-15 16:03 ` Guenter Roeck
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: Muhammad Umair @ 2014-02-15 9:28 UTC (permalink / raw)
To: lm-sensors
Hi,
I have a machine running Motherboard: Supermicro H8DGU with AMD Opteron
6380 (16-core) x2 CPUs. Its running Ubuntu Server 12.04.3 LTS, uname -a:
Linux sysname 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
I have installed sensors version 3.3.2 with libsensors version 3.3.1. The
output of sensors-detect is as follows:
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# System: Supermicro H8DGU [1234567890]
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... Success!
(driver `k10temp')
AMD Family 15h power sensors... Success!
(driver `fam15h_power')
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Winbond W83627DHG-P/W83527HG Super IO Sensors'
(address 0xa10, but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Found `IPMI BMC KCS' at 0xca2... Success!
(confidence 8, driver `to-be-written')
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc
SB600/SB700/SB800 SMBus
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `to-be-written':
* ISA bus, address 0xca2
Chip `IPMI BMC KCS' (confidence: 8)
Driver `fam15h_power' (autoloaded):
* Chip `AMD Family 15h power sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
* Chip `AMD Family 15h thermal sensors' (confidence: 9)
Note: there is no driver for IPMI BMC KCS yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.
No modules to load, skipping modules configuration.
And this is the is the output of sensors:
fam15h_power-pci-00c4
Adapter: PCI adapter
power1: 41.15 W (crit = 114.49 W)
fam15h_power-pci-00d4
Adapter: PCI adapter
power1: 40.99 W (crit = 114.49 W)
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +15.0°C (high = +70.0°C)
(crit = +70.0°C, hyst = +67.0°C)
k10temp-pci-00cb
Adapter: PCI adapter
temp1: +15.4°C (high = +70.0°C)
k10temp-pci-00d3
Adapter: PCI adapter
temp1: +15.0°C (high = +70.0°C)
(crit = +70.0°C, hyst = +67.0°C)
k10temp-pci-00db
Adapter: PCI adapter
temp1: +15.1°C (high = +70.0°C)
I am getting no CPU/CPU core temperature readings at all. And I don't know
these PCI Adapter temperature readings exactly represent. Is my
motherboard and CPU supported? If so what am I doing wrong or not doing?
Kindly help me out here!
Regards
--
Using Opera's mail client: http://www.opera.com/mail/
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [lm-sensors] CPU temperatures not being showed?
2014-02-15 9:28 [lm-sensors] CPU temperatures not being showed? Muhammad Umair
@ 2014-02-15 16:03 ` Guenter Roeck
2014-02-15 17:19 ` Muhammad Umair
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Guenter Roeck @ 2014-02-15 16:03 UTC (permalink / raw)
To: lm-sensors
On 02/15/2014 01:28 AM, Muhammad Umair wrote:
> Hi,
>
>
> I have a machine running Motherboard: Supermicro H8DGU with AMD Opteron 6380 (16-core) x2 CPUs. Its running Ubuntu Server 12.04.3 LTS, uname -a: Linux sysname 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> I have installed sensors version 3.3.2 with libsensors version 3.3.1. The output of sensors-detect is as follows:
>
> # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
> # System: Supermicro H8DGU [1234567890]
>
> This program will help you determine which kernel modules you need
> to load to use lm_sensors most effectively. It is generally safe
> and recommended to accept the default answers to all questions,
> unless you know what you're doing.
>
> Some south bridges, CPUs or memory controllers contain embedded sensors.
> Do you want to scan for them? This is totally safe. (YES/no):
>
> Silicon Integrated Systems SIS5595... No
> VIA VT82C686 Integrated Sensors... No
> VIA VT8231 Integrated Sensors... No
> AMD K8 thermal sensors... No
> AMD Family 10h thermal sensors... No
> AMD Family 11h thermal sensors... No
> AMD Family 12h and 14h thermal sensors... No
> AMD Family 15h thermal sensors... Success!
> (driver `k10temp')
> AMD Family 15h power sensors... Success!
> (driver `fam15h_power')
> Intel digital thermal sensor... No
> Intel AMB FB-DIMM thermal sensor... No
> VIA C7 thermal sensor... No
> VIA Nano thermal sensor... No
>
> Some Super I/O chips contain embedded sensors. We have to write to
> standard I/O ports to probe them. This is usually safe.
> Do you want to scan for Super I/O sensors? (YES/no):
>
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor/ITE'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
> Found `Winbond W83627DHG-P/W83527HG Super IO Sensors'
> (address 0xa10, but not activated)
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor/ITE'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> Trying family `ITE'... No
>
> Some systems (mainly servers) implement IPMI, a set of common interfaces
> through which system health data may be retrieved, amongst other things.
> We first try to get the information from SMBIOS. If we don't find it
> there, we have to read from arbitrary I/O ports to probe for such
> interfaces. This is normally safe. Do you want to scan for IPMI
> interfaces? (YES/no):
>
> Found `IPMI BMC KCS' at 0xca2... Success!
> (confidence 8, driver `to-be-written')
>
> Some hardware monitoring chips are accessible through the ISA I/O ports.
> We have to write to arbitrary I/O ports to probe them. This is usually
> safe though. Yes, you do have ISA I/O ports even if you do not have any
> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
>
> Probing for `National Semiconductor LM78' at 0x290... No
> Probing for `National Semiconductor LM79' at 0x290... No
> Probing for `Winbond W83781D' at 0x290... No
> Probing for `Winbond W83782D' at 0x290... No
>
> Lastly, we can probe the I2C/SMBus adapters for connected hardware
> monitoring devices. This is the most risky part, and while it works
> reasonably well on most systems, it has been reported to cause trouble
> on some systems.
> Do you want to probe the I2C/SMBus adapters now? (YES/no):
>
> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
>
> Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `to-be-written':
> * ISA bus, address 0xca2
> Chip `IPMI BMC KCS' (confidence: 8)
>
> Driver `fam15h_power' (autoloaded):
> * Chip `AMD Family 15h power sensors' (confidence: 9)
>
> Driver `k10temp' (autoloaded):
> * Chip `AMD Family 15h thermal sensors' (confidence: 9)
>
> Note: there is no driver for IPMI BMC KCS yet.
> Check http://www.lm-sensors.org/wiki/Devices for updates.
>
> No modules to load, skipping modules configuration.
>
>
>
> And this is the is the output of sensors:
>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1: 41.15 W (crit = 114.49 W)
>
> fam15h_power-pci-00d4
> Adapter: PCI adapter
> power1: 40.99 W (crit = 114.49 W)
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1: +15.0°C (high = +70.0°C)
> (crit = +70.0°C, hyst = +67.0°C)
>
> k10temp-pci-00cb
> Adapter: PCI adapter
> temp1: +15.4°C (high = +70.0°C)
>
> k10temp-pci-00d3
> Adapter: PCI adapter
> temp1: +15.0°C (high = +70.0°C)
> (crit = +70.0°C, hyst = +67.0°C)
>
> k10temp-pci-00db
> Adapter: PCI adapter
> temp1: +15.1°C (high = +70.0°C)
>
>
> I am getting no CPU/CPU core temperature readings at all. And I don't know these PCI Adapter temperature readings exactly represent. Is my motherboard and CPU supported? If so what am I doing wrong or not doing? Kindly help me out here!
>
k10temp _is_ the CPU temperature. The readings are notoriously
unreliable, especially at low temperatures. You should see
the readings go up with higher load.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [lm-sensors] CPU temperatures not being showed?
2014-02-15 9:28 [lm-sensors] CPU temperatures not being showed? Muhammad Umair
2014-02-15 16:03 ` Guenter Roeck
@ 2014-02-15 17:19 ` Muhammad Umair
2014-02-15 17:39 ` Guenter Roeck
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Muhammad Umair @ 2014-02-15 17:19 UTC (permalink / raw)
To: lm-sensors
On Sat, 15 Feb 2014 21:03:23 +0500, Guenter Roeck <linux@roeck-us.net>
wrote:
> On 02/15/2014 01:28 AM, Muhammad Umair wrote:
>> Hi,
>>
>>
>> I have a machine running Motherboard: Supermicro H8DGU with AMD Opteron
>> 6380 (16-core) x2 CPUs. Its running Ubuntu Server 12.04.3 LTS, uname
>> -a: Linux sysname 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25
>> 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>
>> I have installed sensors version 3.3.2 with libsensors version 3.3.1.
>> The output of sensors-detect is as follows:
>>
>> # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
>> # System: Supermicro H8DGU [1234567890]
>>
>> This program will help you determine which kernel modules you need
>> to load to use lm_sensors most effectively. It is generally safe
>> and recommended to accept the default answers to all questions,
>> unless you know what you're doing.
>>
>> Some south bridges, CPUs or memory controllers contain embedded sensors.
>> Do you want to scan for them? This is totally safe. (YES/no):
>>
>> Silicon Integrated Systems SIS5595... No
>> VIA VT82C686 Integrated Sensors... No
>> VIA VT8231 Integrated Sensors... No
>> AMD K8 thermal sensors... No
>> AMD Family 10h thermal sensors... No
>> AMD Family 11h thermal sensors... No
>> AMD Family 12h and 14h thermal sensors... No
>> AMD Family 15h thermal sensors... Success!
>> (driver `k10temp')
>> AMD Family 15h power sensors... Success!
>> (driver `fam15h_power')
>> Intel digital thermal sensor... No
>> Intel AMB FB-DIMM thermal sensor... No
>> VIA C7 thermal sensor... No
>> VIA Nano thermal sensor... No
>>
>> Some Super I/O chips contain embedded sensors. We have to write to
>> standard I/O ports to probe them. This is usually safe.
>> Do you want to scan for Super I/O sensors? (YES/no):
>>
>> Probing for Super-I/O at 0x2e/0x2f
>> Trying family `National Semiconductor/ITE'... No
>> Trying family `SMSC'... No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
>> Found `Winbond W83627DHG-P/W83527HG Super IO Sensors'
>> (address 0xa10, but not activated)
>> Probing for Super-I/O at 0x4e/0x4f
>> Trying family `National Semiconductor/ITE'... No
>> Trying family `SMSC'... No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
>> Trying family `ITE'... No
>>
>> Some systems (mainly servers) implement IPMI, a set of common interfaces
>> through which system health data may be retrieved, amongst other things.
>> We first try to get the information from SMBIOS. If we don't find it
>> there, we have to read from arbitrary I/O ports to probe for such
>> interfaces. This is normally safe. Do you want to scan for IPMI
>> interfaces? (YES/no):
>>
>> Found `IPMI BMC KCS' at 0xca2... Success!
>> (confidence 8, driver `to-be-written')
>>
>> Some hardware monitoring chips are accessible through the ISA I/O ports.
>> We have to write to arbitrary I/O ports to probe them. This is usually
>> safe though. Yes, you do have ISA I/O ports even if you do not have any
>> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
>>
>> Probing for `National Semiconductor LM78' at 0x290... No
>> Probing for `National Semiconductor LM79' at 0x290... No
>> Probing for `Winbond W83781D' at 0x290... No
>> Probing for `Winbond W83782D' at 0x290... No
>>
>> Lastly, we can probe the I2C/SMBus adapters for connected hardware
>> monitoring devices. This is the most risky part, and while it works
>> reasonably well on most systems, it has been reported to cause trouble
>> on some systems.
>> Do you want to probe the I2C/SMBus adapters now? (YES/no):
>>
>> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc
>> SB600/SB700/SB800 SMBus
>>
>> Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
>> Do you want to scan it? (YES/no/selectively):
>> Now follows a summary of the probes I have just done.
>> Just press ENTER to continue:
>>
>> Driver `to-be-written':
>> * ISA bus, address 0xca2
>> Chip `IPMI BMC KCS' (confidence: 8)
>>
>> Driver `fam15h_power' (autoloaded):
>> * Chip `AMD Family 15h power sensors' (confidence: 9)
>>
>> Driver `k10temp' (autoloaded):
>> * Chip `AMD Family 15h thermal sensors' (confidence: 9)
>>
>> Note: there is no driver for IPMI BMC KCS yet.
>> Check http://www.lm-sensors.org/wiki/Devices for updates.
>>
>> No modules to load, skipping modules configuration.
>>
>>
>>
>> And this is the is the output of sensors:
>>
>> fam15h_power-pci-00c4
>> Adapter: PCI adapter
>> power1: 41.15 W (crit = 114.49 W)
>>
>> fam15h_power-pci-00d4
>> Adapter: PCI adapter
>> power1: 40.99 W (crit = 114.49 W)
>>
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> temp1: +15.0°C (high = +70.0°C)
>> (crit = +70.0°C, hyst = +67.0°C)
>>
>> k10temp-pci-00cb
>> Adapter: PCI adapter
>> temp1: +15.4°C (high = +70.0°C)
>>
>> k10temp-pci-00d3
>> Adapter: PCI adapter
>> temp1: +15.0°C (high = +70.0°C)
>> (crit = +70.0°C, hyst = +67.0°C)
>>
>> k10temp-pci-00db
>> Adapter: PCI adapter
>> temp1: +15.1°C (high = +70.0°C)
>>
>>
>> I am getting no CPU/CPU core temperature readings at all. And I don't
>> know these PCI Adapter temperature readings exactly represent. Is my
>> motherboard and CPU supported? If so what am I doing wrong or not
>> doing? Kindly help me out here!
>>
>
> k10temp _is_ the CPU temperature. The readings are notoriously
> unreliable, especially at low temperatures. You should see
> the readings go up with higher load.
>
> Guenter
>
>
Thanks for the info! but isn't it also supposed to show core temperatures?
And regardless of that, The machine has 2 AMD Opteron 6380 CPUs, so why
exactly is it showing 4 temperature readings? Shouldn't they just be 2?
Regards
--
Using Opera's mail client: http://www.opera.com/mail/
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [lm-sensors] CPU temperatures not being showed?
2014-02-15 9:28 [lm-sensors] CPU temperatures not being showed? Muhammad Umair
2014-02-15 16:03 ` Guenter Roeck
2014-02-15 17:19 ` Muhammad Umair
@ 2014-02-15 17:39 ` Guenter Roeck
2014-02-15 19:23 ` Muhammad Umair
2014-02-15 19:55 ` Jean Delvare
4 siblings, 0 replies; 6+ messages in thread
From: Guenter Roeck @ 2014-02-15 17:39 UTC (permalink / raw)
To: lm-sensors
On 02/15/2014 09:19 AM, Muhammad Umair wrote:
> On Sat, 15 Feb 2014 21:03:23 +0500, Guenter Roeck <linux@roeck-us.net> wrote:
>
>> On 02/15/2014 01:28 AM, Muhammad Umair wrote:
>>> Hi,
>>>
>>>
>>> I have a machine running Motherboard: Supermicro H8DGU with AMD Opteron 6380 (16-core) x2 CPUs. Its running Ubuntu Server 12.04.3 LTS, uname -a: Linux sysname 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> I have installed sensors version 3.3.2 with libsensors version 3.3.1. The output of sensors-detect is as follows:
>>>
>>> # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
>>> # System: Supermicro H8DGU [1234567890]
>>>
>>> This program will help you determine which kernel modules you need
>>> to load to use lm_sensors most effectively. It is generally safe
>>> and recommended to accept the default answers to all questions,
>>> unless you know what you're doing.
>>>
>>> Some south bridges, CPUs or memory controllers contain embedded sensors.
>>> Do you want to scan for them? This is totally safe. (YES/no):
>>>
>>> Silicon Integrated Systems SIS5595... No
>>> VIA VT82C686 Integrated Sensors... No
>>> VIA VT8231 Integrated Sensors... No
>>> AMD K8 thermal sensors... No
>>> AMD Family 10h thermal sensors... No
>>> AMD Family 11h thermal sensors... No
>>> AMD Family 12h and 14h thermal sensors... No
>>> AMD Family 15h thermal sensors... Success!
>>> (driver `k10temp')
>>> AMD Family 15h power sensors... Success!
>>> (driver `fam15h_power')
>>> Intel digital thermal sensor... No
>>> Intel AMB FB-DIMM thermal sensor... No
>>> VIA C7 thermal sensor... No
>>> VIA Nano thermal sensor... No
>>>
>>> Some Super I/O chips contain embedded sensors. We have to write to
>>> standard I/O ports to probe them. This is usually safe.
>>> Do you want to scan for Super I/O sensors? (YES/no):
>>>
>>> Probing for Super-I/O at 0x2e/0x2f
>>> Trying family `National Semiconductor/ITE'... No
>>> Trying family `SMSC'... No
>>> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
>>> Found `Winbond W83627DHG-P/W83527HG Super IO Sensors'
>>> (address 0xa10, but not activated)
>>> Probing for Super-I/O at 0x4e/0x4f
>>> Trying family `National Semiconductor/ITE'... No
>>> Trying family `SMSC'... No
>>> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
>>> Trying family `ITE'... No
>>>
>>> Some systems (mainly servers) implement IPMI, a set of common interfaces
>>> through which system health data may be retrieved, amongst other things.
>>> We first try to get the information from SMBIOS. If we don't find it
>>> there, we have to read from arbitrary I/O ports to probe for such
>>> interfaces. This is normally safe. Do you want to scan for IPMI
>>> interfaces? (YES/no):
>>>
>>> Found `IPMI BMC KCS' at 0xca2... Success!
>>> (confidence 8, driver `to-be-written')
>>>
>>> Some hardware monitoring chips are accessible through the ISA I/O ports.
>>> We have to write to arbitrary I/O ports to probe them. This is usually
>>> safe though. Yes, you do have ISA I/O ports even if you do not have any
>>> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
>>>
>>> Probing for `National Semiconductor LM78' at 0x290... No
>>> Probing for `National Semiconductor LM79' at 0x290... No
>>> Probing for `Winbond W83781D' at 0x290... No
>>> Probing for `Winbond W83782D' at 0x290... No
>>>
>>> Lastly, we can probe the I2C/SMBus adapters for connected hardware
>>> monitoring devices. This is the most risky part, and while it works
>>> reasonably well on most systems, it has been reported to cause trouble
>>> on some systems.
>>> Do you want to probe the I2C/SMBus adapters now? (YES/no):
>>>
>>> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
>>>
>>> Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
>>> Do you want to scan it? (YES/no/selectively):
>>> Now follows a summary of the probes I have just done.
>>> Just press ENTER to continue:
>>>
>>> Driver `to-be-written':
>>> * ISA bus, address 0xca2
>>> Chip `IPMI BMC KCS' (confidence: 8)
>>>
>>> Driver `fam15h_power' (autoloaded):
>>> * Chip `AMD Family 15h power sensors' (confidence: 9)
>>>
>>> Driver `k10temp' (autoloaded):
>>> * Chip `AMD Family 15h thermal sensors' (confidence: 9)
>>>
>>> Note: there is no driver for IPMI BMC KCS yet.
>>> Check http://www.lm-sensors.org/wiki/Devices for updates.
>>>
>>> No modules to load, skipping modules configuration.
>>>
>>>
>>>
>>> And this is the is the output of sensors:
>>>
>>> fam15h_power-pci-00c4
>>> Adapter: PCI adapter
>>> power1: 41.15 W (crit = 114.49 W)
>>>
>>> fam15h_power-pci-00d4
>>> Adapter: PCI adapter
>>> power1: 40.99 W (crit = 114.49 W)
>>>
>>> k10temp-pci-00c3
>>> Adapter: PCI adapter
>>> temp1: +15.0°C (high = +70.0°C)
>>> (crit = +70.0°C, hyst = +67.0°C)
>>>
>>> k10temp-pci-00cb
>>> Adapter: PCI adapter
>>> temp1: +15.4°C (high = +70.0°C)
>>>
>>> k10temp-pci-00d3
>>> Adapter: PCI adapter
>>> temp1: +15.0°C (high = +70.0°C)
>>> (crit = +70.0°C, hyst = +67.0°C)
>>>
>>> k10temp-pci-00db
>>> Adapter: PCI adapter
>>> temp1: +15.1°C (high = +70.0°C)
>>>
>>>
>>> I am getting no CPU/CPU core temperature readings at all. And I don't know these PCI Adapter temperature readings exactly represent. Is my motherboard and CPU supported? If so what am I doing wrong or not doing? Kindly help me out here!
>>>
>>
>> k10temp _is_ the CPU temperature. The readings are notoriously
>> unreliable, especially at low temperatures. You should see
>> the readings go up with higher load.
>>
>> Guenter
>>
>>
>
> Thanks for the info! but isn't it also supposed to show core temperatures? And regardless of that, The machine has 2 AMD Opteron 6380 CPUs, so why exactly is it showing 4 temperature readings? Shouldn't they just be 2?
>
I don't know exactly what readings those CPUs provide. The datasheet should tell.
The output itself suggests that it is for two different CPUs; you can see that there
are four sensors, two of which support critical temperature readings and two don't.
So it looks like you get two readings per CPU. Possibly one is the package temperature
and one is the CPU temperature. Again, the datasheet should tell you what exactly
it is (or maybe someone on the list knows better than me).
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [lm-sensors] CPU temperatures not being showed?
2014-02-15 9:28 [lm-sensors] CPU temperatures not being showed? Muhammad Umair
` (2 preceding siblings ...)
2014-02-15 17:39 ` Guenter Roeck
@ 2014-02-15 19:23 ` Muhammad Umair
2014-02-15 19:55 ` Jean Delvare
4 siblings, 0 replies; 6+ messages in thread
From: Muhammad Umair @ 2014-02-15 19:23 UTC (permalink / raw)
To: lm-sensors
On Sat, 15 Feb 2014 22:39:00 +0500, Guenter Roeck <linux@roeck-us.net>
wrote:
> On 02/15/2014 09:19 AM, Muhammad Umair wrote:
>> On Sat, 15 Feb 2014 21:03:23 +0500, Guenter Roeck <linux@roeck-us.net>
>> wrote:
>>
>>> On 02/15/2014 01:28 AM, Muhammad Umair wrote:
>>>> Hi,
>>>>
>>>>
>>>> I have a machine running Motherboard: Supermicro H8DGU with AMD
>>>> Opteron 6380 (16-core) x2 CPUs. Its running Ubuntu Server 12.04.3
>>>> LTS, uname -a: Linux sysname 3.5.0-23-generic #35~precise1-Ubuntu SMP
>>>> Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>> I have installed sensors version 3.3.2 with libsensors version 3.3.1.
>>>> The output of sensors-detect is as follows:
>>>>
>>>> # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
>>>> # System: Supermicro H8DGU [1234567890]
>>>>
>>>> This program will help you determine which kernel modules you need
>>>> to load to use lm_sensors most effectively. It is generally safe
>>>> and recommended to accept the default answers to all questions,
>>>> unless you know what you're doing.
>>>>
>>>> Some south bridges, CPUs or memory controllers contain embedded
>>>> sensors.
>>>> Do you want to scan for them? This is totally safe. (YES/no):
>>>>
>>>> Silicon Integrated Systems SIS5595... No
>>>> VIA VT82C686 Integrated Sensors... No
>>>> VIA VT8231 Integrated Sensors... No
>>>> AMD K8 thermal sensors... No
>>>> AMD Family 10h thermal sensors... No
>>>> AMD Family 11h thermal sensors... No
>>>> AMD Family 12h and 14h thermal sensors... No
>>>> AMD Family 15h thermal sensors... Success!
>>>> (driver `k10temp')
>>>> AMD Family 15h power sensors... Success!
>>>> (driver `fam15h_power')
>>>> Intel digital thermal sensor... No
>>>> Intel AMB FB-DIMM thermal sensor... No
>>>> VIA C7 thermal sensor... No
>>>> VIA Nano thermal sensor... No
>>>>
>>>> Some Super I/O chips contain embedded sensors. We have to write to
>>>> standard I/O ports to probe them. This is usually safe.
>>>> Do you want to scan for Super I/O sensors? (YES/no):
>>>>
>>>> Probing for Super-I/O at 0x2e/0x2f
>>>> Trying family `National Semiconductor/ITE'... No
>>>> Trying family `SMSC'... No
>>>> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
>>>> Found `Winbond W83627DHG-P/W83527HG Super IO Sensors'
>>>> (address 0xa10, but not activated)
>>>> Probing for Super-I/O at 0x4e/0x4f
>>>> Trying family `National Semiconductor/ITE'... No
>>>> Trying family `SMSC'... No
>>>> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
>>>> Trying family `ITE'... No
>>>>
>>>> Some systems (mainly servers) implement IPMI, a set of common
>>>> interfaces
>>>> through which system health data may be retrieved, amongst other
>>>> things.
>>>> We first try to get the information from SMBIOS. If we don't find it
>>>> there, we have to read from arbitrary I/O ports to probe for such
>>>> interfaces. This is normally safe. Do you want to scan for IPMI
>>>> interfaces? (YES/no):
>>>>
>>>> Found `IPMI BMC KCS' at 0xca2... Success!
>>>> (confidence 8, driver `to-be-written')
>>>>
>>>> Some hardware monitoring chips are accessible through the ISA I/O
>>>> ports.
>>>> We have to write to arbitrary I/O ports to probe them. This is usually
>>>> safe though. Yes, you do have ISA I/O ports even if you do not have
>>>> any
>>>> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
>>>>
>>>> Probing for `National Semiconductor LM78' at 0x290... No
>>>> Probing for `National Semiconductor LM79' at 0x290... No
>>>> Probing for `Winbond W83781D' at 0x290... No
>>>> Probing for `Winbond W83782D' at 0x290... No
>>>>
>>>> Lastly, we can probe the I2C/SMBus adapters for connected hardware
>>>> monitoring devices. This is the most risky part, and while it works
>>>> reasonably well on most systems, it has been reported to cause trouble
>>>> on some systems.
>>>> Do you want to probe the I2C/SMBus adapters now? (YES/no):
>>>>
>>>> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies
>>>> Inc SB600/SB700/SB800 SMBus
>>>>
>>>> Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
>>>> Do you want to scan it? (YES/no/selectively):
>>>> Now follows a summary of the probes I have just done.
>>>> Just press ENTER to continue:
>>>>
>>>> Driver `to-be-written':
>>>> * ISA bus, address 0xca2
>>>> Chip `IPMI BMC KCS' (confidence: 8)
>>>>
>>>> Driver `fam15h_power' (autoloaded):
>>>> * Chip `AMD Family 15h power sensors' (confidence: 9)
>>>>
>>>> Driver `k10temp' (autoloaded):
>>>> * Chip `AMD Family 15h thermal sensors' (confidence: 9)
>>>>
>>>> Note: there is no driver for IPMI BMC KCS yet.
>>>> Check http://www.lm-sensors.org/wiki/Devices for updates.
>>>>
>>>> No modules to load, skipping modules configuration.
>>>>
>>>>
>>>>
>>>> And this is the is the output of sensors:
>>>>
>>>> fam15h_power-pci-00c4
>>>> Adapter: PCI adapter
>>>> power1: 41.15 W (crit = 114.49 W)
>>>>
>>>> fam15h_power-pci-00d4
>>>> Adapter: PCI adapter
>>>> power1: 40.99 W (crit = 114.49 W)
>>>>
>>>> k10temp-pci-00c3
>>>> Adapter: PCI adapter
>>>> temp1: +15.0°C (high = +70.0°C)
>>>> (crit = +70.0°C, hyst = +67.0°C)
>>>>
>>>> k10temp-pci-00cb
>>>> Adapter: PCI adapter
>>>> temp1: +15.4°C (high = +70.0°C)
>>>>
>>>> k10temp-pci-00d3
>>>> Adapter: PCI adapter
>>>> temp1: +15.0°C (high = +70.0°C)
>>>> (crit = +70.0°C, hyst = +67.0°C)
>>>>
>>>> k10temp-pci-00db
>>>> Adapter: PCI adapter
>>>> temp1: +15.1°C (high = +70.0°C)
>>>>
>>>>
>>>> I am getting no CPU/CPU core temperature readings at all. And I don't
>>>> know these PCI Adapter temperature readings exactly represent. Is my
>>>> motherboard and CPU supported? If so what am I doing wrong or not
>>>> doing? Kindly help me out here!
>>>>
>>>
>>> k10temp _is_ the CPU temperature. The readings are notoriously
>>> unreliable, especially at low temperatures. You should see
>>> the readings go up with higher load.
>>>
>>> Guenter
>>>
>>>
>>
>> Thanks for the info! but isn't it also supposed to show core
>> temperatures? And regardless of that, The machine has 2 AMD Opteron
>> 6380 CPUs, so why exactly is it showing 4 temperature readings?
>> Shouldn't they just be 2?
>>
>
> I don't know exactly what readings those CPUs provide. The datasheet
> should tell.
> The output itself suggests that it is for two different CPUs; you can
> see that there
> are four sensors, two of which support critical temperature readings and
> two don't.
> So it looks like you get two readings per CPU. Possibly one is the
> package temperature
> and one is the CPU temperature. Again, the datasheet should tell you
> what exactly
> it is (or maybe someone on the list knows better than me).
>
> Guenter
>
>
>
>
Okay thanks man! If anyone else has something more to add, please do so!
Also the reason I am trying to use lm-sensors is that because machines in
our lab with the same configuration are experiencing random spontaneous
reboots, which may occur with a gap of a few days or may not occur at all.
The logs show nothing so I was suspecting a hardware problem. Will the
readings from lm-sensors be atleast reliable enough in those regards? to
identify if maybe the reboots are somehow temperature related? I was
planning on scripting a small cron to log CPU temperatures using
lm-sensors periodically, so I could look at them the next time the machine
reboots.
Any thoughts on that?
Regards
--
Using Opera's mail client: http://www.opera.com/mail/
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [lm-sensors] CPU temperatures not being showed?
2014-02-15 9:28 [lm-sensors] CPU temperatures not being showed? Muhammad Umair
` (3 preceding siblings ...)
2014-02-15 19:23 ` Muhammad Umair
@ 2014-02-15 19:55 ` Jean Delvare
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2014-02-15 19:55 UTC (permalink / raw)
To: lm-sensors
On Sun, 16 Feb 2014 00:23:39 +0500, Muhammad Umair wrote:
> Also the reason I am trying to use lm-sensors is that because machines in
> our lab with the same configuration are experiencing random spontaneous
> reboots, which may occur with a gap of a few days or may not occur at all.
> The logs show nothing so I was suspecting a hardware problem. Will the
> readings from lm-sensors be atleast reliable enough in those regards? to
> identify if maybe the reboots are somehow temperature related? I was
> planning on scripting a small cron to log CPU temperatures using
> lm-sensors periodically, so I could look at them the next time the machine
> reboots.
>
> Any thoughts on that?
Yes, it is a good idea to use lm-sensors for that. You could use
sensord to log the values, for example. You may want to decrease the
logging interval to say 1 minute, instead of the default 5 minutes, to
increase your chances to catch the problematic conditions (if that's
really what your problem is.)
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-02-15 19:55 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-15 9:28 [lm-sensors] CPU temperatures not being showed? Muhammad Umair
2014-02-15 16:03 ` Guenter Roeck
2014-02-15 17:19 ` Muhammad Umair
2014-02-15 17:39 ` Guenter Roeck
2014-02-15 19:23 ` Muhammad Umair
2014-02-15 19:55 ` Jean Delvare
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.