acpi does not report correct temperature on Intel Pentium 4 CPU

[Sly Marbo]

Binary package hint: linux-source-2.6.22

No matter what temperature the processor is running at, acpi always reports it as being 22 degrees Celcius, meaning that if the CPU begins to overheat, the fan speed is not increased accordingly so the CPU continues to heat up until the BIOS shuts down the PC automatically. This threshold appears to be around 65 degrees Celcius. As a precaution, I have removed one side of the box and placed a large desk fan facing the PC and set it to run, but this is noisy and takes up a lot of space. The problem developed some time within the last week and I do not know why or how it has occured.

[Cristian Aravena Romero (caravena)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please run the command "sudo dmidecode > dmidecode.log" and attach the resulting file "dmidecode.log" to this bug report.

Read: https://wiki.ubuntu.com/DebuggingACPI

For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[Sly Marbo (the.sly.marbo)]

1. Linux PC5 2.6.22-14-386 #1 Tue Dec 18 07:34:24 UTC 2007 i686 GNU/Linux

[Leann Ogasawara (leannogasawara)]

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. Thanks.

[Nick B. (futurepilot)]

Bug still exists on Hardy final.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Nick B. (futurepilot)]

Still exists with 2.6.27 for me. acpi -t shows 40.0C and it never changes.

[panos (distratios)]

Same for me. Kubuntu 8.04, 2.6.24-21-generic. acpi shows constant temperature of 16 C, which causes thermal shutdows on heavy cpu loads. Tested the Intrepid live cd without success.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Nick B. (futurepilot)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Problem still exists on Karmic.

status new
done
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJLnBu4AAoJEIltSrFpUGte+I4IALa4MrH+rzHsCMU/GJ61724X
6ztMrTZrlBIU810k8LgwfR+rwX/oRRA2IU8CcQnxPIO4Mi+T4xm0ncyhTofAMn9Y
dNyhKVkd0xjlonoPazdEzv/Q+V6QHMq8JeoMdHASeo//QQX2Cbn6klc7A84TWJJc
JKfh+j4rt+wB5GPb1JziufKAG2k4bIPfnvhO9mTroNfH+fzWUcrqydLaBiaHJc0B
NmD4Oc3AXVC4MJ/Pee6NyIbIk/ngug80Bz5bnq5q9PYFfInIL7MoPnGeJIReLxG0
p4qHNgySLgXhE1jt9hV/6ZCDRhZPKAqW1QaKyU385SdqFznq6yFYU1N0x18GK9Q=
=kLll
-----END PGP SIGNATURE-----

[Jeremy Foshee (jeremyfoshee)]

Nick B.,
     would you mind testing against the latest daily live build of Lucid?

Thanks!

~JFo

[Nick B. (futurepilot)]

On 03/13/2010 08:14 PM, Jeremy Foshee wrote:
> Nick B.,
> would you mind testing against the latest daily live build of Lucid?
>
> Thanks!
>
> ~JFo
>
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>
Still reproducible on Lucid.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Nick B. (futurepilot)]

I guess no one saw my comment? See #14.

[Jeremy Foshee (jeremyfoshee)]

Nick, in this case the bug was expired due to lack of response from the original reporter. Would you mind opening a new bug so that we can work through your issue?

Thanks!

~JFo