This problem persists in Intrepid and in Jaunty. In fact, in Jaunty you can't even use the /etc/modprobe.d/options method anymore. Is this going to be addressed or are we left with to deal with whining CPUs?
There should be some way that the user can set the max_cstate, whether that is at run-time using /proc or statically by setting the modprobe options. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
