It seems the heating problem is a red herring, a false lead, an unrelated distraction.
It seems that the 2.6.22 and 2.6.24 kernels running the machine hot is not connected to this issue. I ran the 2.6.25-1 kernel during today, just doing normal office work, and constantly logging my CPU core temperature. It took until now in early afternoon, but the 2.6.25-1 kernel finally froze as well, while I was just doing some writing in gvim. SIgnificantly, the temperature log file shows the machine steadily at about 65-68 degrees, well within the normal operating temperature (it's temperature limited at 88 degrees). So it seems the crashes are no connected to temperature after all. In hindsight it's kind of obvious: if the 22 and 24 kernels always make the computer run hot, it will be hot when it crashes whether it's connected or not. Elod, my highscore on medium is about 7800 points. I've been doing a lot of.. um... testing to find this bug - yes, that's it, testing. That's all. Not addicted or anything; nope, not me. I'm hesitant to run cpuburn (the warning is rather scary), but I have used this system for development and testing of simulations, which are pegging both cores at 100% whenever I test. This I have done for the entire Gutsy six-month cycle without ever crashing. And as I wrote above, heating seems to be a false lead in any case. -- Hardy kernel causes overheating https://bugs.launchpad.net/bugs/223081 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
