high cpu temperature

rrodrigues · 2010-02-12 15:15:46

Hi all. i've new arch installation a few days ago. However i could stop notice that the temperature of my laptop e always high (and when i reboot to windows fan is always working like crazy).

After 20 min using my laptop the temperature from sensors are:

 ~ $ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:       +83.0°C  (crit = +108.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +76.0°C  (high = +105.0°C, crit = +105.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +79.0°C  (high = +105.0°C, crit = +105.0°C)

Someone can help with this? dont know what to do..

There some information:

 ~ $ uname -a
Linux doguito 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 9 15:12:10 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz GenuineIntel GNU/Linux

and

 ~ $ cat /proc/cpuinfo 
processor       : 0    
vendor_id       : GenuineIntel
cpu family      : 6           
model           : 23          
model name      : Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz
stepping        : 10                                             
cpu MHz         : 800.000                                        
cache size      : 3072 KB                                        
physical id     : 0                                              
siblings        : 2                                              
core id         : 0                                              
cpu cores       : 2                                              
apicid          : 0                                              
initial apicid  : 0                                              
fpu             : yes                                            
fpu_exception   : yes                                            
cpuid level     : 13                                             
wp              : yes                                            
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi flexpriority                                                                         
bogomips        : 5056.67                                                                          
clflush size    : 64                                                                               
cache_alignment : 64                                                                               
address sizes   : 36 bits physical, 48 bits virtual                                                
power management:                                                                                  

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6           
model           : 23          
model name      : Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz
stepping        : 10                                             
cpu MHz         : 800.000
cache size      : 3072 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi flexpriority
bogomips        : 5056.17
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

toad · 2010-02-12 15:31:29

Arch on a laptop requires a little bit more meddling than on a desktop. Check the wiki under Laptop to get started.
http://wiki.archlinux.org/index.php/Laptop
http://wiki.archlinux.org/index.php/Laptop_Mode_Tools

rrodrigues · 2010-02-13 00:40:39

thanks and sorry, it was easy
i think laptop mode tool did the trick

rrodrigues · 2010-02-13 17:01:42

hi again.
I've another problem.
if i start my laptop the temperature goes up (like 60º/70º) and fan doesn't start. Then if i restart computer the fan start to could down the cpu temperature (start when init gets to deamons start up).

Any possible help?

ArchSoarer · 2010-02-18 04:41:09

rrodrigues wrote:

hi again.
I've another problem.
if i start my laptop the temperature goes up (like 60º/70º) and fan doesn't start. Then if i restart computer the fan start to could down the cpu temperature (start when init gets to deamons start up).
Any possible help?

You can try to pass to the kernel line in /boot/grub/menu.lst the option acpi_osi="Linux" so the fan works fine. It's a common problem on a Toshiba laptop and netbooks. Anyway, on a wake up from hibernate the fan won't work. I only use the pm_utils to kinda "backup" my work in case I could not save and turn off.

rrodrigues · 2010-03-02 01:08:03

well... i think it helps but the overheating of the cpu continuous to be random.. i dont understand, sometimes the fan starts when computer starts (if the cpu temperature is high, like 40 ºC, it certainly starts) but another times it doesnt starts... i dont know why sometimes the fan works and another dont..

i have a toshiba laptop.. a new one.. u500-12d.. someone else have the same problem and know how to fix it?

another think.. i can load/install the toshiba-acpi module.. i dont know if it helps.... and i dont find any place to install it... the module is important?

thanks for any help

Skyalmian · 2010-04-20 05:02:00

Fiddling with these issues... acpi on makes for no boot. I've been running Arch Linux 64 exclusively (no Windows partition) on this Toshiba L505D-S5983 since April 10 or so with acpi=off and unconcerned about that until now, to when I'm trying to get any kind of temperature or battery output for tint2/conky and finding they're related to acpi -- and no go so far. I have "acpi=ht" + "acpi_osi="Linux"" in use presently which has lead to two Arch Linux icons displaying in the upper left corner of the screen as well as: "hwclock error: "select() to /dev/rtc to wait for clock tick timed out"" showing up in the list of messages... As far as power management goes (laptop-mode-tools, etc.), I think I'll skip that and just go with a battery output percentage with countdown timer -- if I can figure out how to get even that...

If a cooking CPU becomes a threat then I'll swap out the eSATA drive with the original in the closet which has Windows 7 on it...

Last edited by Skyalmian (2010-04-20 06:09:27)

Skyalmian · 2010-04-20 07:53:03

Okay, finally have a temperature reading from something...

Installed "acpi", "lm_sensors", read this thread, read this Wiki section on setting up lm_sensors...

Wow...this is harsh. Only one sensor...

[skyalmian@alcyone ~]$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: TOSHIBA Satellite L505D (laptop)
# Board: TOSHIBA Portable PC

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): YES
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...                           Success!
    (driver `k10temp')
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom 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): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   Yes
Found unknown chip with ID 0xfc11
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

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): YES
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): YES
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter:  (i2c-1)
Do you want to scan it? (YES/no/selectively): YES

Next adapter:  (i2c-2)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x28
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter:  (i2c-3)
Do you want to scan it? (YES/no/selectively): YES

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 10h thermal sensors' (confidence: 9)

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

[skyalmian@alcyone ~]$ lm-sensors
bash: lm-sensors: command not found
[skyalmian@alcyone ~]$ lm_sensors
bash: lm_sensors: command not found
[skyalmian@alcyone ~]$ sensors-detect
You need to be root to run this script.
[skyalmian@alcyone ~]$ clear

[skyalmian@alcyone ~]$ sudo sensors-detect



[skyalmian@alcyone ~]$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: TOSHIBA Satellite L505D (laptop)
# Board: TOSHIBA Portable PC

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): YES
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...                           Success!
    (driver `k10temp')
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom 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): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   Yes
Found unknown chip with ID 0xfc11
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

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): YES
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): YES
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter:  (i2c-1)
Do you want to scan it? (YES/no/selectively): YES

Next adapter:  (i2c-2)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x28
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter:  (i2c-3)
Do you want to scan it? (YES/no/selectively): YES

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 10h thermal sensors' (confidence: 9)

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

[skyalmian@alcyone ~]$

[skyalmian@alcyone ~]$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +65.5°C  (high = +70.0°C, crit = +100.0°C)

Edit: Fan kicked on...

Last edited by Skyalmian (2010-04-20 07:57:07)

Arch Linux

#1 2010-02-12 15:15:46

high cpu temperature

#2 2010-02-12 15:31:29

Re: high cpu temperature

#3 2010-02-13 00:40:39

Re: high cpu temperature

#4 2010-02-13 17:01:42

Re: high cpu temperature

#5 2010-02-18 04:41:09

Re: high cpu temperature

#6 2010-03-02 01:08:03

Re: high cpu temperature

#7 2010-04-20 05:02:00

Re: high cpu temperature

#8 2010-04-20 07:53:03

Re: high cpu temperature

Board footer