Bug 459043
| Summary: | ACPI: Critical trip point - Critical temperature reached, shutting down. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frode Tennebø <frodet> |
| Component: | kernel | Assignee: | John Feeney <jfeeney> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | chris.brown, dominik, james, kernel-maint |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 2.6.26.3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-14 17:11:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Frode Tennebø
2008-08-13 21:26:50 UTC
I'm reopening this as I see exactly the same behaviour with identical hardware as before, but with updated kernel: [root@luke ~]# cat /var/log/messages | grep temp Aug 12 22:48:07 luke kernel: Critical temperature reached (3343 C), shutting down. Aug 12 22:48:37 luke kernel: Critical temperature reached (63 C), shutting down. Aug 13 21:47:49 luke kernel: Critical temperature reached (3341 C), shutting down. Aug 13 21:48:19 luke kernel: Critical temperature reached (60 C), shutting down. [root@luke ~]# uname -a Linux luke 2.6.25.11-60.fc8 #1 SMP Mon Jul 21 02:06:29 EDT 2008 i686 i686 i386 GNU/Linux It just happened again: Aug 21 03:58:46 luke kernel: Critical temperature reached (3340 C), shutting dow n. Aug 21 03:58:46 luke shutdown[31566]: shutting down for system halt Aug 21 03:58:50 luke gconfd (ft-3506): Received signal 15, shutting down cleanly Aug 21 03:58:51 luke gconfd (ft-3506): Exiting Aug 21 03:58:56 luke smartd[2758]: smartd received signal 15: Terminated Aug 21 03:58:56 luke smartd[2758]: smartd is exiting (exit status 0) Aug 21 03:59:01 luke kernel: Critical temperature reached (65 C), shutting down. Aug 21 03:59:01 luke acpid: client has disconnected Aug 21 03:59:01 luke acpid: client has disconnected : [root@luke ~]# uname -a Linux luke 2.6.25.11-60.fc8 #1 SMP Mon Jul 21 02:06:29 EDT 2008 i686 i686 i386 GNU/Linux This also just happened after a F9 upgrade:
[root@luke init.d]# uname -a
Linux luke 2.6.25.14-108.fc9.i686 #1 SMP Mon Aug 4 14:08:11 EDT 2008 i686 i686 i386 GNU/Linux
[root@luke livna]#
Message from syslogd@luke at Aug 22 18:14:50 ...
kernel:Critical temperature reached (3342 C), shutting down.
Broadcast message from root@luke
(unknown) at 18:14 ...
The system is going down for power off NOW!
kernel-2.6.26.3-12.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/kernel-2.6.26.3-12.fc8 kernel-2.6.26.3-14.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/kernel-2.6.26.3-14.fc8 kernel-2.6.26.3-14.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. I can confirm that it persists for 2.6.25.14-108 F9. I have therefore move this bug to that release. I can also note that it appears that adding the kernel parameter "acpi=no" seems to stop this behaviour as I now have an uptime of 6 days - normally it shuts down withing 10 hours, usually within 2. "noacpi" had no effect... (In reply to comment #7) > I can confirm that it persists for 2.6.25.14-108 F9. I have therefore move > this bug to that release. > It is fixed in the 2.6.26.3 kernels on both F8 and F9. I can confirm that 2.6.26.3 did NOT fix this problem: Oct 3 21:13:25 luke kernel: imklog 3.18.1, log source = /proc/kmsg started. Oct 3 21:13:25 luke kernel: Initializing cgroup subsys cpuset Oct 3 21:13:25 luke kernel: Linux version 2.6.26.3-29.fc9.i686 (mockbuild@) (gcc version 4.3.0 2 0080428 (Red Hat 4.3.0-8) (GCC) ) #1 SMP Wed Sep 3 03:42:27 EDT 2008 : : Oct 3 21:18:01 luke ntpd[2448]: synchronized to 193.120.142.71, stratum 2 Oct 3 21:18:01 luke ntpd[2448]: time correction of -7201 seconds exceeds sanity limit (1000); se t clock manually to the correct UTC time. Oct 3 19:22:31 luke ntpd[6042]: ntpd 4.2.4p4 Mon Jul 28 11:12:44 UTC 2008 (1) : : Oct 3 19:40:41 luke kernel: ACPI: Critical trip point Oct 3 19:40:41 luke kernel: Critical temperature reached (3343 C), shutting down. Nor is it fixed in 2.6.26.5
[ft@luke ~]$ uname -a
Linux luke 2.6.26.5-45.fc9.i686 #1 SMP Sat Sep 20 03:45:00 EDT 2008 i686 i686 i386 GNU/Linux
[root@luke ~]#
Message from syslogd@luke at Oct 6 03:15:19 ...
kernel:Critical temperature reached (4983 C), shutting down.
Broadcast message from root@luke
(unknown) at 3:15 ...
The system is going down for power off NOW!
Connection to luke closed by remote host.
Connection to luke closed.
Since today, I experience temperature-initiated shutdowns while booting, the first message appears immediately before the disk initialization, then the system tries to shut down. This results in many errors, as nothing is mounted yet but tries to get unmounted, etc. The critical temperature is always 144C, even it the laptop is powered on after being off for a day or so, if it boots, the sensors show 35-50 degrees. May it have something to do with the latest initscripts-update? It also happens with older kernels, like 2.6.26.5-45.fc9.i686, but only since today! [root@illuminati ~]# uname -a Linux illuminati.dadadom.lan 2.6.26.6-79.fc9.i686 #1 SMP Fri Oct 17 14:52:14 EDT 2008 i686 i686 i386 GNU/Linux [root@illuminati ~]# tail -n 25 /var/log/yum.log Oct 24 11:32:10 Installed: phonon-backend-xine-4.1.2-5.fc9.i386 Oct 24 11:32:14 Updated: kdesvn-1.2.1-1.fc9.i386 Oct 24 11:32:16 Updated: git-email-1.5.6.5-1.fc9.i386 Oct 24 11:32:16 Updated: git-svn-1.5.6.5-1.fc9.i386 Oct 24 11:32:17 Updated: git-arch-1.5.6.5-1.fc9.i386 Oct 24 11:32:18 Updated: emacs-git-1.5.6.5-1.fc9.i386 Oct 24 11:32:19 Updated: git-cvs-1.5.6.5-1.fc9.i386 Oct 24 11:32:20 Updated: git-gui-1.5.6.5-1.fc9.i386 Oct 24 11:32:21 Updated: gitk-1.5.6.5-1.fc9.i386 Oct 24 11:32:21 Updated: git-all-1.5.6.5-1.fc9.i386 Oct 24 11:32:39 Erased: kmod-gspca-2.6.25.14-108.fc9.i686 Oct 24 11:33:19 Installed: kernel-2.6.26.6-79.fc9.i686 Oct 26 01:44:29 Updated: logwatch-7.3.6-25.fc9.noarch Oct 26 01:44:38 Updated: php-pear-Image-GraphViz-1.2.1-4.fc9.noarch Oct 26 01:44:47 Updated: file-libs-4.23-6.fc9.i386 Oct 26 01:44:50 Updated: Xaw3d-1.5E-12.fc9.i386 Oct 26 01:44:52 Updated: file-4.23-6.fc9.i386 Oct 26 01:44:54 Updated: xorg-x11-drv-synaptics-0.15.1-3.fc9.i386 Oct 26 01:45:05 Updated: initscripts-8.76.4-1.i386 Oct 26 01:54:23 Updated: 2:opera-9.61-2456.gcc4.shared.qt3.i386 Oct 26 09:35:36 Erased: flash-plugin Oct 26 10:09:29 Installed: gc-devel.i386 7.0-7.fc9 Oct 26 10:20:37 Installed: boost-devel.i386 1.34.1-15.fc9 Oct 26 10:42:27 Installed: gsl-devel.i386 1.10-10.fc9 Oct 26 11:27:59 Installed: AdobeReader_deu-8.1.2_SU1-1.i486 I downgraded to: [ft@luke STP]$ uname -a Linux luke 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686 i686 i386 GNU/Linux And everything has been shiny for: [ft@luke STP]$ uptime 19:21:10 up 14 days, 51 min, 5 users, load average: 0.08, 0.03, 0.00 This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |