Comment 8 for bug 220013

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Luke,

Thanks for testing and the feedback. The Intrepid kernel definitely sounds promising here. As you know we're still in the early stages for the Intrepid kernel so it may be a few weeks before it actually hits the archives. But for now I'll go ahead and mark this fix released against Intrepid. Obviously if you notice any regressions feel free to reopen this (ie set the Intrepid task from "Fix Released" to "New").

It might be nice to try and narrow down the patch which will resolve the panics on the Hardy kernel. We could then possibly try to get it in the Hardy 8.04.1 point release. However, isolating the fix would require performing a git bisect and doing some kernel builds. This is not something we expect bug reporters to know how to do. But if you're feeling adventurous, the following links may help:

http://www.kernel.org/doc/local/git-quick.html#bisect
https://wiki.ubuntu.com/KernelCustomBuild

There are a few things to note however. When performing the git bisect you will have to switch the meanings of "good" and "bad" as the bisection is looking for the patch which caused a regression rather than the patch which provides a fix. Also, you can get the git tree for the Intrepid kernel by doing:

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

Again, doing the above this completely voluntary on your part. Thanks :)