I am having this issue with Intrepid. Current updates applied as of 11/27/2008
10pm est.
The processor is a Core2Duo E7200. The motherboard is a Foxconn G31AXK. The
fans are working and are set to be permanently ON.
uname -a
Linux quasar 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64
GNU/Linux
dmesg output is attached.
Fan throttling via ACPI is DISABLED in the bios but ACPI in the kernel
seems unaware of this. Also the temperatures read by ACPI are totally
wrong and the attempts at starting the fans (which are always running)
are totally unnecessary. Actual processor temps are in the low 30's C
but the temps being read are 183C - constantly.
more /proc/acpi/fan/FAN/state
status: on
more /proc/acpi/thermal_zone/THRM/*
::::::::::::::
/proc/acpi/thermal_zone/THRM/cooling_mode
::::::::::::::
0 - Active; 1 - Passive
::::::::::::::
/proc/acpi/thermal_zone/THRM/polling_frequency
::::::::::::::
<polling disabled>
::::::::::::::
/proc/acpi/thermal_zone/THRM/state
::::::::::::::
state: passive
::::::::::::::
/proc/acpi/thermal_zone/THRM/temperature
::::::::::::::
temperature: 183 C
::::::::::::::
/proc/acpi/thermal_zone/THRM/trip_points
::::::::::::::
critical (S5): 232 C
passive: 50 C: tc1=4 tc2=3 tsp=60 devices=CPU0
active[0]: 50 C: devices= FAN
Its really stupid. I dont know where ACPI is getting these numbers for
current and critical temp either. The BIOS is not reporting inaccurate
temps in the display and the system runs cool with no instability that
would accompany such drastically high temps. The processor would not be
destroyed running at that temp. The bios is also configured to shutdown
at some high double digit celsius value - cant recall offhand what I set
it to.
I have removed and blacklisted thermal due to this bug. Not something I
should have to do.
My processor also has one core being slowed for no apparent reason. Im
not sure if this is related. Could this be a BIOS compatibility issue?
cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to [EMAIL PROTECTED], please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1.60 GHz - 2.53 GHz
available frequency steps: 2.53 GHz, 1.60 GHz
available cpufreq governors: powersave, userspace, ondemand, conservative,
performance
current policy: frequency should be within 1.60 GHz and 1.60 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1.60 GHz - 2.53 GHz
available frequency steps: 2.53 GHz, 1.60 GHz
available cpufreq governors: powersave, userspace, ondemand, conservative,
performance
current policy: frequency should be within 1.60 GHz and 2.53 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
----------
The current policy freq range for cpu0 is set static. I am currently attempting
to find out how to resolve this too.
This is my first bug post in awhile so please forgive me if I have
omitted any necessary information.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/20014571/dmesg.log
--
ACPI: Unable to turn cooling...
https://bugs.launchpad.net/bugs/63550
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
