This bug has been solved with the 2.6.22 kernel in all the distros I've tried that had the problem before. So if you are using any kernel that is older than that (gutsy is the first to carry it in the ubuntu line), then you are still going to experience the problem. AFAIK, no backporting was done on this fix. Meaning, either someone will need to backport it to feisty, or you'll have to upgrade to gutsy as soon as it's released.
This bug has been solved with the 2.6.22 kernel in all the distros I've tried that had the problem before. So if you are using any kernel that is older than that (gutsy is the first to carry it in the ubuntu line), then you are still going to experience the problem. AFAIK, no backporting was done on this fix. Meaning, either someone will need to backport it to feisty, or you'll have to upgrade to gutsy as soon as it's released.