CPU Temperature warning spamming syslog
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After upgrading to Karmic, the syslog is constantly spammed with these messages:
[ 5694.592683] CPU0: Temperature above threshold, cpu clock throttled (total events = 4220841)
[ 5694.592699] CPU1: Temperature above threshold, cpu clock throttled (total events = 4220850)
[ 5694.593238] CPU0: Temperature/speed normal
[ 5694.593244] CPU1: Temperature/speed normal
The messages happen so fast that the dd/rsyslogd completely saturate the CPU. Within 1 hour of upgrading, /var/log/messages and /var/log/syslog had both grown larger than 200mb.
This is especially annoying because this machine supports neither temperature monitoring nor CPU throttling.
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0c: al 2369 F...m pulseaudio
/dev/snd/pcmC0D0p: al 2369 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'ICH5'/'Intel ICH5 with AD1981B at irq 17'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 26
Simple ctrls : 19
Date: Thu Oct 29 12:58:02 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
MachineType: Dell Computer Corporation OptiPlex GX270
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:
dmi.bios.date: 06/26/2006
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A07
dmi.board.name: 0Y1057
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComp
dmi.product.name: OptiPlex GX270
dmi.sys.vendor: Dell Computer Corporation
I have same messages, but only AFTER evolution has been started. until then it is fine, but run evolutio nad CPU is maxed out.