Comment 5 for bug 269248

Hi Ryan,

Thanks for the bug report, lets see if we can try to get this resolved. You mention testing the latest kernel available for Intrepid. I suspect as you do that this might be a bug in the upstream kernel as well since we just rebased the Ubuntu kernel with upstream. If you would be intersted in testing the upstream kernel just to verify, try taking a look at the following:

https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

Building the upstream kernel is obviously not something we expect you to know how to do so proceeding with doing this is completely voluntary and at your own comfort level. We appreciate all the help you can give. If you do happen to test the upstream kernel and can verify this is an issue upstream, it's likely we'll want to escalate this in an upstream bug report at bugzilla.kernel.org. The next step after that would likely be to perform a git bisect to try and narrow down the patch which is causing the regression. Again, this is competely at your own comfort level if you want to do this but will be extremely helpful to both us and upstream to narrow down this bug. Information regarding performing a git bisect can be found at:

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

You can perform the git bisect using the upstream kernel git tree or the Ubuntu kernel git tree. If you want to use the Ubuntu kernel git tree I'd suggest looking at the following:

https://help.ubuntu.com/community/Kernel/Compile => discussing building the Ubuntu kernel
https://wiki.ubuntu.com/KernelGitGuide => information regarding where to get the Ubuntu kernel git tree - You'll likely want to grab the Hardy git tree to reduce the number of bisections you'd need to perform.

Definitely let us know if you have any questions. I realize this might be a bit overwhelming with all this information I just gave you. But again, we really appreciate all the help you can provide. Thanks.