lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 20 Dec 2008 00:06:19 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	linux-kernel@...r.kernel.org
Subject:  Re: Problem with thermal control: ACPI: Critical trip point - Critical
   temperature reached  - shutting down.

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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ