Comment 11 for bug 36014

Revision history for this message
Constantine Evans (cevans) wrote :

The severity was probably bumped because:

* The bug now affects both the 386 and 686 kernels. Thus there is no workaround listed in the bug.
* Instead of having the frequency stuck at the *highest* value, the frequency is stuck at the *lowest* value on affected machines. In my case that means I am always running at 600MHz instead of 1.6GHz, which causes a very noticeable performance hit.