[8.10] ACPI: Critical trip point

Bug #264069 reported by little jo
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
acpi (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: acpi

Hello,
i use Intrepid version.
ACPI : 1.1-1ubuntu1

After using it several hours, my laptop automatically shuts down.

/var/log/kern.log :
Sep 2 18:28:18 ubuntu kernel: [ 6520.511160] ACPI: Critical trip point
Sep 2 18:28:18 ubuntu kernel: [ 6520.511199] Critical temperature reached (112 C), shutting down.
Sep 2 18:28:18 ubuntu kernel: [ 6520.518502] Critical temperature reached (52 C), shutting down.
Sep 2 18:28:24 ubuntu kernel: [ 6526.894850] mtrr: no MTRR for 94000000,2000000 found
Sep 2 18:28:28 ubuntu kernel: [ 6530.260396] ip6_tables: (C) 2000-2006 Netfilter Core Team
...

Revision history for this message
Chris Coulson (chrisccoulson) 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. Please also describe whether you can hear your fan working correctly.

Changed in acpi:
assignee: nobody → chrisccoulson
status: New → Incomplete
Revision history for this message
Barteq (barteqpl) wrote :

Hello.

I've got very similar problem with my Thinkpad T61. Under 8.10 laptop halts with "Critical temperature reached", even if it's quite idle. Fan works all the time, if computer gets hotter - fan becomes faster, so acpi works ok. It's set to 'auto' mode. Halts are quite random, sometimes without significant load average.. Today it halted while writing someting on the gnome-terminal with browser opened and temeratures about 60 C. (got sensors aplet with core1/2 and nvidia temerature).
It happens also while watching HD movie (halted in the middle) and while playing games (halted on quake3 or need for speed).
Tried to use tpfand to speed up fan when temerature becomes too high, but it made halts to show up more often.

Strange things are happening with fan control..

root@thinkpad:~# echo level 5 > /proc/acpi/ibm/fan
root@thinkpad:~# cat /proc/acpi/ibm/fan
status: enabled
speed: 3320
level: 5
commands: level <level> (<level> is 0-7, auto, disengaged, full-speed)
commands: enable, disable
commands: watchdog <timeout> (<timeout> is 0 (off), 1-120 (seconds))

After a few seconds (max 3)

root@thinkpad:~# cat /proc/acpi/ibm/fan
status: enabled
speed: 3320
level: auto
commands: level <level> (<level> is 0-7, auto, disengaged, full-speed)
commands: enable, disable
commands: watchdog <timeout> (<timeout> is 0 (off), 1-120 (seconds))

Level was auto changed to 'auto'... so wired. Under 8.04 it behaves normally.
Don't know if it's related, but might be..

Some logs:

Oct 26 20:43:14 thinkpad kernel: [73432.097298] ACPI: Critical trip point
Oct 26 20:43:14 thinkpad kernel: [73432.097311] Critical temperature reached (100 C), shutting down.
Oct 26 20:43:14 thinkpad kernel: [73432.367173] Critical temperature reached (89 C), shutting down.
--
Oct 25 14:46:08 thinkpad kernel: [238292.256976] ACPI: Critical trip point
Oct 25 14:46:08 thinkpad kernel: [238292.256987] Critical temperature reached (100 C), shutting down.
Oct 25 14:46:08 thinkpad kernel: [238292.524348] Critical temperature reached (91 C), shutting down.

/proc/acpi/thermal_zone/THM0/temperature
temperature: 55 C
/proc/acpi/thermal_zone/THM0/trip_points
critical (S5): 127 C

/proc/acpi/thermal_zone/THM1/temperature
temperature: 48 C
/proc/acpi/thermal_zone/THM1/trip_points
critical (S5): 100 C
passive: 96 C: tc1=5 tc2=4 tsp=600 devices=CPU0 CPU1

Revision history for this message
Barteq (barteqpl) wrote :
Revision history for this message
Barteq (barteqpl) wrote :
Revision history for this message
Barteq (barteqpl) wrote :
Changed in acpi (Ubuntu):
assignee: Chris Coulson (chrisccoulson) → nobody
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.