I assumed this fix was already picked up. The fix that I point to in the first comment, is required and fixes a legit bug, also the fix has been in mainline for quite a few kernel versions, so I don't think there is any risk associated with it. The fix is pretty straight forward, so I don't think you have to wait for any test confirmations.
I have seen quite a few people complaining because of this bug related to VMI on this thread, http://ubuntuforums.org/showthread.php?t=882246&page=2 maybe all of them have started using "clocksource=" commandline parameter as a result no one is complaining anymore, but the VMI clock should work too and given that it is more efficient on those releases we should use that, whenever possible.
If the 8.04 release is still maintained, I would recommend that this fix should be picked for the next update. Thanks.
I assumed this fix was already picked up. The fix that I point to in the first comment, is required and fixes a legit bug, also the fix has been in mainline for quite a few kernel versions, so I don't think there is any risk associated with it. The fix is pretty straight forward, so I don't think you have to wait for any test confirmations.
I have seen quite a few people complaining because of this bug related to VMI on this thread, ubuntuforums. org/showthread. php?t=882246& page=2 maybe all of them have started using "clocksource=" commandline parameter as a result no one is complaining anymore, but the VMI clock should work too and given that it is more efficient on those releases we should use that, whenever possible.
http://
If the 8.04 release is still maintained, I would recommend that this fix should be picked for the next update. Thanks.