CPU Temperature Indicator

[Per Bothner]

On 02/02/2013 03:01 PM, Adam Williamson wrote:
> The OS is not involved in over-temp shutdown logic. It happens at the
> ACPI level. The firmware lets the kernel know, so you can at least see a
> message in your /var/log/messages to let you know that you hit the
> thermal cutoff, but the logic to trigger the shutdown is in the
> firmware, not in the OS. You should be able to tell
> from /var/log/messages if you're hitting thermal cutoff, just look for a
> message about critical temperature threshold exceeded (or something
> roughly like that) around the time of the shutdown.

Nothing:

Feb  2 19:17:04 localhost dbus-daemon[680]: dbus[680]: [system] 
Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb  2 19:17:04 localhost dbus[680]: [system] Activating service 
name='org.freedesktop.PackageKit' (using servicehelper)
Feb  2 19:17:04 localhost dbus-daemon[680]: dbus[680]: [system] 
Successfully activated service 'org.freedesktop.PackageKit'
Feb  2 19:17:04 localhost dbus[680]: [system] Successfully activated 
service 'org.freedesktop.PackageKit'
Feb  2 19:17:05 localhost colord: Device added: xrandr-LVDS1
Feb  2 19:17:05 localhost colord: Device added: xrandr-HF289H-917KHM05AN23
Feb  2 19:17:05 localhost colord: Profile added: 
icc-6a2849e9b3401a08105371302270eb85
Feb  2 19:17:05 localhost colord: Profile added: 
icc-2c3dd46afcc42cbfb2ea346905053fe0
Feb  2 19:17:05 localhost colord: Profile added: 
icc-f2b36b411782f640c134b543422fb837
Feb  2 19:17:05 localhost colord: Profile added: 
icc-18c1913600268443c454cb2d282a2ff3
Feb  2 19:17:05 localhost colord: Profile added: 
icc-d4ced510609f96a382ec0a0e9de39025
Feb  2 19:17:05 localhost colord: Profile added: 
icc-7de1ea5909be7d079286386b3a5696c5
Feb  2 19:17:05 localhost colord: Profile added: 
icc-eb5854c2ffaa976b49cfaaebb0591437
Feb  2 19:17:05 localhost colord: Profile added: 
icc-1ff34df90cfc1ff61b5eabcb6649abd3
Feb  2 19:17:06 localhost goa[1947]: goa-daemon version 3.6.2 starting 
[main.c:112, main()]
Feb  2 19:17:16 localhost dbus-daemon[680]: ** Message: No devices in 
use, exit
Feb  2 19:17:23 localhost systemd-logind[668]: Removed session 1.

While things are running hot, that might not be a problem.  A number of 
files
are truncated.  For example:
/usr/libexec/gcc/x86_64-redhat-linux/4.7.2/
-rwxr-xr-x. 1 root root 11444232 Nov  9 05:07 cc1
-rwxr-xr-x. 1 root root 12402736 Nov  9 05:07 cc1plus
-rwxr-xr-x. 1 root root        0 Nov  9 05:07 collect2
-rwxr-xr-x. 1 root root     6256 Nov  9 05:07 ecj1
-rwxr-xr-x. 1 root root 11068216 Nov  9 05:06 jc1
-rwxr-xr-x. 1 root root   203464 Nov  9 05:07 jvgenmain
lrwxrwxrwx. 1 root root       22 Feb  1 09:07 liblto_plugin.so -> 
liblto_plugin.so.0.0.0
lrwxrwxrwx. 1 root root       22 Feb  1 09:07 liblto_plugin.so.0 -> 
liblto_plugin.so.0.0.0
-rwxr-xr-x. 1 root root        0 Nov  9 05:07 liblto_plugin.so.0.0.0
-rwxr-xr-x. 1 root root        0 Nov  9 05:06 lto1

I may need to re-install.  Is there a way to clone my F17 installation
before I run fedup?  It would be nice to have a fedup mode that installs
to a new partition, based on settings and packages in the currently
running one.  Given existing F18 problems, I'm a bit nervous about running
fedup in place and thus risking my working F17 installation.  I guess
I could back up my disk with clonezilla (for example), but that's a pain.
-- 
	--Per Bothner
per at bothner.com   http://per.bothner.com/