This issue also impacts use of VMware on certain CPUs. See, for example, http://www.phocean.net/?p=10 http://ubuntuforums.org/showthread.php?t=769948 and https://help.ubuntu.com/community/VMware/Workstation
I find that with Hardy this problem is much less severe than it was in Edgy, Feisty and Gutsy, but it is still present. In those other releases is completely solved by setting max_cstate to 1 while vmware is running. The usual recommendation is to set it to 1 while vmware is running, and back to whatever it had been before when exiting vmware so that the idling can work when it isn't causing problems. That is no longer possible. Setting a low max_cstate at boot time is a very poor substitute for on-the-fly manipulation in this instance. I add my plea that this useful function be restored. -- Unable to set max_cstate on hardy kernel https://bugs.launchpad.net/bugs/206864 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
