acpi misreports temperature, shuts down laptop

[Colin Cooper]

Binary package hint: acpi

Feisty 7.0.4: Laptop shut itself down.
After reboot, I found this in kern.log:

May 1 11:25:46 colin-laptop kernel: [ 8038.532153] ACPI: Critical trip point
May 1 11:25:46 colin-laptop kernel: [ 8038.532158] Critical temperature reached (1154 C), shutting down.

I don't think this is a duplicate since the other related acpi bugs (#94862 #22336) happen as startup or show "reasonable" temperatures.
... and I think I'd have noticed if it actually passed 1000 deg C.

I suspect that somewhere the temp value is getting corrupted.

I haven't seen this before on this laptop - I've been running dapper/edgy/feisty on it for about 9 months.

[millenium-hand (yairgordon)]

I've been getting the same thing.

Ubuntu install went fine, but when I use the system, after about 20 minutes(?) of doing even memory-non-intensive things, the system just stops, and shuts down. I get a glimpse of a message similar to Colin's above back in the terminal screen.

Temperature values vary, but they are clearly bogus, as it's physically impossible that my laptop actually got that hot. I would have known.

I'm running Ubuntu Feisty 7.04, on an HP omnibook xe4500.
I've also never had this problem since a few days ago, I think since I installed Feisty (it might also have happened once or twice in Edgy, just a few days ago. I'm not sure).
 I booted Edgy Live CD just to check, put on some continuous tasks to run, and it's been going fine for hours.

[James Valentine (jamesdavidvalentine)]

I'll try not to make this a me-too post, but my Clevo M121W has exhibited this fault from Breezy to Gutsy. Some kernel upgrades solve it, but most of the time, I recompile the kernel without the THERMAL acpi module. This, I assume, leaves the thermal protection up the BIOS.

Here is a forum post I started a long time ago: http://ubuntuforums.org/showthread.php?t=88432

Here is an Open Question I've started asking about recent Gutsy kernel ACPI changes, as the bug went when I installed Gutsy and came back when the latest kernel upgrade came around: https://answers.launchpad.net/ubuntu/+question/13735

If anyone could flesh this out more, the three of us at least would be grateful!

[barlennan (barlennan)]

I saw a post somewhere (sorry, I can't remember where) that said the wrong temperatures were from the temperature readings being converted from tenths of a degree Celsius to Fahrenheit twice. It had some ACPI microcode to fix the problem, but it only worked for the case of the temperature appearing colder than it really was. Unfortunately I have the other problem (appears hotter than reality), and the problem is still there in Hardy Heron.

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[barlennan (barlennan)]

Hi,

On Tue, Aug 25, 2009 at 9:08 PM, Andreas
Moog<email address hidden> wrote:
> You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an issue
> for you. Can you try with the latest Ubuntu release? Thanks in advance.

The main problem (random shutdowns) went away when I disabled acpi.
Now with Intrepid acpi is back, and fortunately I am not getting
unrequested shutdowns. The temperature sensor does not seem to be
updated after boot, though. I can make the fan speed change by
working the CPU, but the temperature stays at 31 C.

So I don't think it's completely fixed, but it's certainly not serious anymore.

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed the package your bugging is updated in Maverick. Does this occur in it? If so, please feel free to mark this bug as new. Thanks in advance!

[Launchpad Janitor (janitor)]

[Expired for acpi (Ubuntu) because there has been no activity for 60 days.]