Red Hat Bugzilla – Bug 204245
overheat shutdown: 2.6.17-1.2142-FC4, unable to get SMM BIOS version
Last modified: 2007-11-30 17:11:41 EST
Description of problem:
Dell laptop Latitude D400, FC4: I upgraded the kernel with yum, from
2.6.15-1.1833_FC4 to 2.6.17-1.2142_FC4; overnight the laptop shut itself down
unexpectedly. I found in /var/log/messages:
moby kernel: Critical temperature reached (100 C), shutting down.
and then, after some research, found earlier in the log:
moby kernel: i8k: unable to get SMM BIOS version
moby kernel: Dell laptop SMM driver v1.14 21/02/2005 Massimo Dal Zotto
I returned to the earlier kernel and all appears well.
Version-Release number of selected component (if applicable):
The only think I know is to upgrade the kernel and reboot, then wait for the
Steps to Reproduce:
Created attachment 135005 [details]
This is either a kernel bug, if the laptop now really overheats for some reason,
or a i8k kernel module bug, if it is wrong about the laptop's temperature. Both
ways, I don't think this has anything to do with the userspace tools...
One thing that would be interesting to know is if your laptop really reaches
100°C when it gets shut down, i.e. if it's REALLY hot. Maybe you've got a
screensaver taking 100% CPU or maybe the latest i8k kernel module doesn't
control the fans properly...
I set up a heavy load (AC power, while : ; do sha1sum bigfile ; done) and
watched the temperature (cat /proc/acpi/thermal_zone/THM/temperature and running
i8kmon). It topped out at 97C, fan went on as I thought it should, and
stabilized at 95C (94C according to i8kmon). The laptop was quite hot; I
believe the log message about 100C.
/proc/acpi/fan/ has no entry, I think the BIOS is responsible for the fan in a
Latitude D400? Is there an initialization that could leave the BIOS unsure
about the fan speed, and lead to overheating, perhaps something about
dual-booting back and forth between FC4 and WinXP?
I'll leave the machine on overnight in the new kernel and see what happens. Is
there more I should look at?
Reassigning to correct owner, kernel-maint.
Update: I have kept the laptop configured to use the new kernel since posting
the bug, and have not seen the failure, I have no idea at this point how to
reproduce the problem.
Lacking better information and experience, I will leave it to the kernel
maintainers whether to close this as non-reproducible, or whether to leave it
open for further work.
I'd be happy to look further at the problem, given some advice how to proceed.
[This comment added as part of a mass-update to all open FC4 kernel bugs]
FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel. As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
Please retest with Fedora Core 5.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
Thank you for your attention, I have tested FC5 and now FC6, as well as leaving
the FC4 kernel in place. Under none of these conditions have I seen overheating
again, so I conclude that this bug should be closed.
As a point of information, though, I *did* recently see overheating when running
under WindowsXP/pro SP2 (in a looping MSWord macro), so I think there's probably
a hardware or BIOS bug involved. (Dell Latitude D400 A03 bios, 3 years old)