Comment 48 for bug 213081

Hi Brian,

The best approach to isolating patches which resolved the issue for Intrepid would be to do a git bisect. This is obviously not something we expect you to know how to do so this is completely at your own discretion if you'd like to try. The following link describes how to perform a git bisect:

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

The only tricky issue is you're going to have to reverse the meanings of good and bad since you're trying to isolate a patch which fixed the issue, and not caused a regression. You can get the Intrepid git tree by doing:

git clone git://kernel.ubuntu.com/ubuntu/ubuntu-intrepid.git ubuntu-intrepid

In the process of performing the git bisect, you will also need to perform some kernel builds of your own. Again, not something we expect you to know how to do, but if you're willing to try that's great. Information regarding how to build the Ubuntu kernel can be found at https://help.ubuntu.com/community/Kernel/Compile .

I realize this can be quite a bit of information to digest and could be overwhelming. It's completely at your own comfort level if you'd like to give all this a try. We definitely already appreciate all the help you've given by testing. Thanks.