All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem with thermal control: ACPI: Critical trip point - Critical temperature reached  - shutting down.
Date: Sat, 20 Dec 2008 00:06:19 -0600	[thread overview]
Message-ID: <494C8B5B.8020606@shaw.ca> (raw)
In-Reply-To: <gigib1$fbj$1@ger.gmane.org>

Alessandro Bono wrote:
> Hi all
> 
> My notebook shutdown down with intensive cpu load
> In log I found this type of messages 
> 
> 
> Dec 19 16:10:08 champagne kernel: ACPI: Critical trip point
> Dec 19 16:10:08 champagne kernel: Critical temperature reached (105 C), 
> shutting down.
> Dec 19 16:10:08 champagne kernel: ACPI: Critical trip point
> Dec 19 16:10:08 champagne kernel: Critical temperature reached (105 C), 
> shutting down.
> Dec 19 16:10:08 champagne kernel: ACPI: Critical trip point
> Dec 19 16:10:08 champagne kernel: Critical temperature reached (105 C), 
> shutting down.
> Dec 19 16:10:08 champagne kernel: ACPI: Critical trip point
> Dec 19 16:10:08 champagne kernel: Critical temperature reached (105 C), 
> shutting down.
> Dec 19 16:10:16 champagne kernel: Critical temperature reached (87 C), 
> shutting down.
> 
> Simply I can't do a "make -j2" to compile a kernel
> First time of this behaviour appear with 2.6.27 but maybe I didn't stress 
> enough my system
> Notebook is an hp 8510p, some log and information below
> 
> Any idea?
> 
> thanks
> 
> 
> cat /proc/acpi/thermal_zone/*/*
> <setting not supported>
> <polling disabled>
> state:                   active[0]
> temperature:             85 C
> critical (S5):           256 C
> passive:                 100 C: tc1=1 tc2=2 tsp=300 devices=CPU0 CPU1
> active[0]:               85 C: devices=C387
> active[1]:               65 C: devices=C388
> active[2]:               60 C: devices=C389
> active[3]:               45 C: devices=C38A
> active[4]:               35 C: devices=C38B
> <setting not supported>
> <polling disabled>
> state:                   ok
> temperature:             94 C
> critical (S5):           105 C
> <setting not supported>
> <polling disabled>
> state:                   active[1]
> temperature:             76 C
> critical (S5):           105 C
> active[0]:               100 C: devices=C36F
> active[1]:               70 C: devices=C36A
> active[2]:               60 C: devices=C36B
> active[3]:               55 C: devices=C36C
> active[4]:               45 C: devices=C36D
> active[5]:               35 C: devices=C36E
> <setting not supported>
> <polling disabled>
> state:                   ok
> temperature:             61 C
> critical (S5):           105 C
> passive:                 95 C: tc1=1 tc2=2 tsp=300 devices=CPU0 CPU1
> <setting not supported>
> <polling disabled>
> state:                   ok
> temperature:             28 C
> critical (S5):           105 C
> passive:                 60 C: tc1=1 tc2=2 tsp=300 devices=CPU0 CPU1
> <setting not supported>
> <polling disabled>
> state:                   ok
> temperature:             100 C
> critical (S5):           110 C

Are the fan(s) running? What does /proc/acpi/fan/*/* show?


  reply	other threads:[~2008-12-20  6:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 16:32 Problem with thermal control: ACPI: Critical trip point - Critical temperature reached - shutting down Alessandro Bono
2008-12-20  6:06 ` Robert Hancock [this message]
2008-12-20 11:50   ` Alessandro Bono
     [not found]   ` <1229770623.8215.82.camel@champagne.cantina>
2008-12-21 18:08     ` Robert Hancock
2008-12-21 20:48       ` Matthew Garrett
2008-12-22 21:53       ` Alessandro Bono

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=494C8B5B.8020606@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.