I decided not to worry about it, and just get used to it. I _think_ the old lower temps were more sensible, and I would only worry about my machine if the "old" temp got really high.
If anything in the CPU really is as hot as the "new" readings indicate, it doesn't seem to be a problem. And I don't really think anything is that hot. I looked at what the authors of the change were saying, and they weren't confident that these were accurate or anything, just that they were going to do it this way, and might update it if further information on what the numbers mean on an absolute scale was forthcoming from Intel. Probably all these reports coming in from diverse hardware saying that the old readings matched the BIOS will encourage them to go back to the old calibration. (I don't believe that the internal temp is actually always 15C hotter than the sensor the BIOS uses, since I've checked the BIOS temp right after a reboot with a hot CPU, and with an idle CPU. If the internal temp sensor was reading differently, I would expect bigger differences when the CPU was hotter.) There is no config option to control this. You'd have to change some kernel code in coretemp.c and recompile. -- linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive https://bugs.launchpad.net/bugs/264290 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
