+++ This bug was initially created as a clone of Bug #431494 +++ Description of problem: Same problem as Bug #431494, under F9 on IBM X60 (model 1706-GMG). Running CPU intensive things (in my case the nightly amanda backup (laptop is a client) makes the machine go into thermal shutdown mode Version-Release number of selected component (if applicable): 2.6.25.14-108.fc9.x86_64 How reproducible: machine does thermal shutdown every night Steps to Reproduce: 1. Have machine on and happy all day with light CPU load 2. backup runs at night 3. Machine is off in the morning and logs show thermal shutdown was initiated
Created attachment 314518 [details] /var/log/dmesg from this morning's boot
from /var log messages: Aug 18 07:05:15 x60-pcfe xinetd[2622]: START: amanda pid=20527 from=::ffff:192.168.50.9 Aug 18 07:05:45 x60-pcfe xinetd[2622]: EXIT: amanda status=0 pid=20527 duration=30(sec) Aug 18 07:05:45 x60-pcfe xinetd[2622]: START: amanda pid=20578 from=::ffff:192.168.50.9 Aug 18 07:06:15 x60-pcfe xinetd[2622]: EXIT: amanda status=0 pid=20578 duration=30(sec) Aug 18 07:06:15 x60-pcfe xinetd[2622]: START: amanda pid=20625 from=::ffff:192.168.50.9 Aug 18 07:06:45 x60-pcfe xinetd[2622]: EXIT: amanda status=0 pid=20625 duration=30(sec) Aug 18 07:06:45 x60-pcfe xinetd[2622]: START: amanda pid=20673 from=::ffff:192.168.50.9 Aug 18 07:07:15 x60-pcfe xinetd[2622]: EXIT: amanda status=0 pid=20673 duration=30(sec) Aug 18 07:07:22 x60-pcfe xinetd[2622]: START: amanda pid=20729 from=::ffff:192.168.50.9 Aug 18 07:07:53 x60-pcfe xinetd[2622]: EXIT: amanda status=0 pid=20729 duration=31(sec) Aug 18 07:11:23 x60-pcfe xinetd[2622]: START: amanda pid=20954 from=::ffff:192.168.50.9 Aug 18 07:14:20 x60-pcfe kernel: ACPI: Critical trip point Aug 18 07:14:20 x60-pcfe kernel: Critical temperature reached (128 C), shutting down. and the next night: Aug 19 06:10:38 x60-pcfe xinetd[2623]: START: amanda pid=21961 from=::ffff:192.168.50.9 Aug 19 06:15:23 x60-pcfe kernel: ACPI: Critical trip point Aug 19 06:15:23 x60-pcfe kernel: Critical temperature reached (128 C), shutting down.
FWIW: last evening I did: echo 'level 7' > /proc/acpi/ibm/fan to nail the fan at high speed, machine still shut down. (and, yes, I do have "options thinkpad_acpi fan_control=1" so that this actually does control the fan speed)
Could be http://lkml.org/lkml/2008/8/12/217 ? I don't have an F9 tree handy.
This bug is new in upstream 2.6.25.14 and is fixed in 2.6.26.2-14.fc9 Upstream commit is 9f497bcc695fb828da023d74ad3c966b1e58ad21 Fedora patch is linux-2.6-acpi-processor-use-signed-int.patch This is not fixed in either upstream 2.6.25.16 or 2.6.26.3 ...
kernel-2.6.26.3-17.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/kernel-2.6.26.3-17.fc9
kernel-2.6.26.3-27.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/kernel-2.6.26.3-27.fc9
2.6.26.3-27.fc9.x86_64 does not solve the problem for me. To test I enabled boinc-client (hogs the CPU massively) and the machine went to Critical trip point within 30 minutes.
kernel-2.6.26.3-29.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/kernel-2.6.26.3-29.fc9
kernel-2.6.26.3-29.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
Just to be complete I have mixed results with 2.6.26.3-29.fc9 - my nightly amanda run completed fine, so may main concern is solved (and hence not reopening bug) - if I force 100% CPU usage (again with boinc) the machine will thermal shutdown, but this seems warranted as it does run so hot that it will refuse to power up immediately after this (x60 1706-GMG does have sub-par cooling capabilities it seems) and running boinc is just a test on this notebook
problem is back :-( running F10 updated, kernel 2.6.27.19-170.2.35.fc10.x86_64 machine will again go into thermal shutdown during nightly amanda run.
FWIW: a week ago I cleaned out my fan assembly with compressed air, since then I have not had the machine go into thermal shutdown. While this helps, it is not perfect as in the times it did thermal shutdown, I never once saw a temp over 90 Celsius, either there is a point where temp goes up really fast or the counting in hardware is bad. But, at least for me (ambient air temperature is seldom over 20 Celsius), the problem is resolved and considering the age of my x60 (it's 2.5 years old now), this solution is sufficient. For those that want to clean; be sure to immobilise the fan with a pen or screwdriver, before blowing air through it.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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
Problem remains fixed. Laptop will be out of warranty in February and F10 is nearinf EOL, so closing.