Incorrect Temperature Reporting Causes Hard Shutdown

Bug #296056 reported by atc
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Anything even remotely CPU intensive causes the reporting of CPU temperature to increase rapidly thus a hard-shutdown occurs. Running `apt-get upgrade`, `apt-get install` or even just scrolling the visible WLAN list will cause this.

I am retrieving the temperature via `acpi -t` in a shell. Running an apt-get upgrade and monitoring the CPU temperature via acpi shows it increasing to critical point (90 C +), from an idle temperature of between 48 and 51 C.

I have added the following modules to /etc/modules as suggested on the Ubuntu Forums (http://ubuntuforums.org/showthread.php?t=539365&page=5):
* battery
* ac
* thermal
* processor
* acpi-cpufreq
* cpufreq-userspace

I also tried adding trip points to /etc/rc.local, but this didn't help either:
* echo -n “90:80:60:75:70:65″ > /proc/acpi/thermal_zone/THM0/trip_points
* echo 2 > /proc/acpi/thermal_zone/THM0/polling_frequency

_Additional Information_
1) Description: Ubuntu 8.10, Release: 8.10
2) Not applicable, as I am not sure what software package is causing this. Assuming ACPI is the culprit: 1.1-1ubuntu1.
3) I expect the computer not to be shutdown
4) A forced shutdown, or in the worst case a 'hard shutdown': the computer doesn't turn off gracefully but instantly.

_Hardware Information_
IBM Thinkpad X31
768MB RAM
60GB HDD
ATI Radeon Mobility M6 using radeonfb

Revision history for this message
atc (atc-) wrote :
Revision history for this message
atc (atc-) wrote :

I've managed to trigger a hard shutdown by viewing an image & AJAX intensive website like Google Analytics. This is a critical bug and is more than likely damaging my hardware.

Revision history for this message
xteejx (xteejx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments (if possible with the system as it is above).
This is most definately sounding like an ACPI problem. Rest assured a LOT of newer hardware (2000 onwards) has a thermal cutout sensor on the motherboard as a fail-safe in case system fans die or things like that, so its very doubtful your hardware will be severely damaged in any way.
Thanks in advance :)

Revision history for this message
atc (atc-) wrote :

Hi Teej, thanks for replying. I wasn't aware of that Wiki page whilst writing the report (I should've searched though!). I've attached a .tar.bz with the requested information.

Cheers/

Revision history for this message
xteejx (xteejx) wrote :

All required information is attached as per Debugging Procedures for ACPI. This should be enough information to help in resolving this problem. If any more information is required by another triager/developer, please attach it. Thank you.

Changed in linux:
status: Incomplete → Confirmed
Revision history for this message
barlennan (barlennan) wrote :

I found that uninstalling powersaved and installing powernowd stopped the random shutdowns on my k7 laptop, although it did not fix the temperature reporting.

Revision history for this message
Alex (alextcollins) wrote :

It seems a cleaned heatsink and CPU and a fresh dose of Arctic Silver 5 has resolved this issue. I've done a clean reinstall of Xubuntu 8.10 and my Thinkpad X31 hasn't shutdown without being told to.

Revision history for this message
atc (atc-) wrote :

'Alex' above is me, the original bug reporter.

Revision history for this message
Andy Walker (walkeraj) wrote :

Seems like this was just a heatsink problem and has been reported as such by the original reporter. Closing as invalid.

Changed in linux:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.