Looks like, that primary P4 systems have the problem
(I've not registered this issue before karmic and the syslog replacement called rsyslog).
My P4 3.0 GHz is running since the first day with a temperature 70...75°C, its not a fan issue or cooling problem.. its designed by Intel.
I've investigated now ~5 days with the problem with no acceptable solution (at least for me).
The Bug is partial fixed with the additional rsyslog temperature conf file to prevent the massive flood of various logfiles and filling up /var with messages like that
[11400.257971] CPU0: Temperature above threshold, cpu clock throttled (total events = 1972881)
[11400.258565] CPU0: Temperature/speed normal
But if you check the process you'll see a neverending stongly cpu consuming dd process (invoked by rsyslogd)
root 4443 1 11 21:25 ? 00:00:01 dd bs=1 if=/proc/kmsg of=/var/run/rsyslog/kmsg
The only way to have a little bit silence is, to stop the rsyslog proces until a fix is available
Don't forget, to stop again after reboot.
# sudo service rsyslog stop
Looks like, that primary P4 systems have the problem
(I've not registered this issue before karmic and the syslog replacement called rsyslog).
My P4 3.0 GHz is running since the first day with a temperature 70...75°C, its not a fan issue or cooling problem.. its designed by Intel.
I've investigated now ~5 days with the problem with no acceptable solution (at least for me).
The Bug is partial fixed with the additional rsyslog temperature conf file to prevent the massive flood of various logfiles and filling up /var with messages like that
[11400.257971] CPU0: Temperature above threshold, cpu clock throttled (total events = 1972881)
[11400.258565] CPU0: Temperature/speed normal
But if you check the process you'll see a neverending stongly cpu consuming dd process (invoked by rsyslogd) run/rsyslog/ kmsg
root 4443 1 11 21:25 ? 00:00:01 dd bs=1 if=/proc/kmsg of=/var/
The only way to have a little bit silence is, to stop the rsyslog proces until a fix is available
Don't forget, to stop again after reboot.
# sudo service rsyslog stop