Comment 32 for bug 209342

Hi Everyone,

Thanks for testing and the feedback. I'm glad at least the Intrepid kernel is working for you. Now the tricky part is to narrow down the exact patch(es) which resolved this issue. There are a vast amount of changes between the 2.6.24 and 2.6.25 kernels. Is anyone here familiar with (and willing to perform) a git bisect to try and isolate the fix? This is typically not something we expect you as bug reporters to know how to do. However it is helpful to the kernel team, especially since you would be able to confirm the fix. We could then try to get this into Hardy's 8.04.1 point release. I'll post some links to some docs which may help if you're interested. But again, this is completely at your own comfort level:

http://www.kernel.org/doc/local/git-quick.html#bisect
https://help.ubuntu.com/community/Kernel/Compile

Also note, that for the bisect you'll have to switch the meanings of "good" and "bad" as the bisection searches for the patch which caused a regression, not the patch which fixes an issue.

Additionally, you can grab the Intrepid kernel source git tree from by performing:

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

Hope that helps. Thanks.