Comment 10 for bug 221213

Hi Radu,

Thanks for testing and the feedback. I'm glad to hear this is at least resolved for now with the upcoming Intrepid kernel. So the tricky part now would be to narrow down the exact patch(es) which have resolved this issue. That unfortunately is a difficult task if you are unfamiliar with how to perform a git bisect. This is obviously something we don't expect you as a bug reporter to know how to do. The decision is really up to you at this point. Are you fine with running the Intrepid kernel which resolves your issue, or would you like to try to locate the patch and try to get it into the 8.04.1 Hardy point release. If you would like to try to shoot for the 8.04.1 point release, please refer to the information below which regards how to build your own kernel and perform a git bisection:

https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
  * Instead use git://kernel.ubuntu.com/ubuntu/ubuntu-intrepid.git when you clone the tree
  * Also, the above wiki will walk you through the old way of building the Ubuntu kernel, for the more up to date way, refer to: https://help.ubuntu.com/community/Kernel/Compile

http://www.kernel.org/doc/local/git-quick.html#bisect

The only other thing with performing the git bisect is that you'll have to reverse the meanings of "good" and "bad" when performing the git bisect since it assumes you are searching for the patch which caused the regression rather than the patch which fixed the issue.

Again, this is completely at your own comfort level. Let us know with how you'll want to proceed.

Also, with the new bugs you are seeing with the Intrepid kernel, care to open separate bug reports for each of those. It is helpful to the kernel team if bug reports are about one specific issue and a specific set of hardware.

Hope that helped. Thanks.