Comment 14 for bug 219657

Hi Erik,

Thanks for testing the Intrepid Alpha release. From you comments it sounds promising. I'm going to tentatively mark this Fix Release for Intrepid.

Now the bigger issue is trying to narrow down the patch(es) which resolved this in Intrepid and see if they will qualify at a Stable Release Update for Hardy. That's a rather difficult task as the Hardy kernel is a 2.6.24 kernel and the Intrepid kernel is a 2.6.26 kernel. The amount of patches that went into between the two versions is quite large. How comfortable would you be performing a git bisect ? It will require some knowledge of building the kernel. This is obviously something we do not expect bug reporters to know how to do and it is completely at your own comfort level if you are willing to give it a try. The git bisect basically helps narrow down the exact patch that can cause a regression or resolve a bug. The only reason I ask for your help with this is because this issue really is hardware specific and since you have the hardware to reproduce the issue, you're likely the best candidate to help with performing the git bisect. But again, this is completely your choice. More information regarding how to perform a git bisect can be found here:

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

The only small change is that you'll have to switch the meanings of "Good" and "Bad" since you are trying to isolate the patch which resolved the bug, not caused the regression.

Information regarding the Ubuntu git kernel tree for Intrepid can be found at:

https://wiki.ubuntu.com/KernelGitGuide

And finally information about building the Ubuntu kernel is here:

https://help.ubuntu.com/community/Kernel/Compile

Again I completely understand if this is a bit overwhelming and not something you'd be willing to do. But given the limited kernel resources we have, we really do appreciate all the help we can get from community members like yourself. Thanks.