Comment 30 for bug 207919

Hi Dave,

Thanks for the update. I'm glad to hear this appears to be resolved. I'll tentatively mark this "Fix Released" for Intrepid. Obviously if you notice any regressions prior to Intrepid final coming out, please reopen this report by setting the status back to "New".

Now trying to describe to you what technically changed between two versions of the kernel is a rather tall order to ask. The reason I say this is because there can be literally thousands of patches that go into the kernel between just a single release (for ex from 2.6.26 to 2.6.27). This is mainly because we are constantly rebasing our kernel with what is upstream. If you only examined the Ubuntu kernel change log you'd have only seen what we've done to the kernel since we rebased. To get the full amount of changes you'd also have to examine the upstream kernel change log. And with out the stack trace of the kernel panic to help diagnose what went wrong, it's even more difficult to guess what may have resulted in the fix. The only likely way to find out exactly what fixed the issue would to do a git bisect. Sorry I couldn't be more specific here. Hope that helped a little. Thanks.