Activity log for bug #207919

Date Who What changed Old value New value Message
2008-03-27 19:41:56 Dave Shaw bug added bug
2008-03-28 16:09:08 Leann Ogasawara linux: status New Incomplete
2008-03-31 02:33:45 Dave Shaw bug added attachment 'dmesg.log' (dmesg output)
2008-03-31 02:39:22 Dave Shaw bug added attachment 'lspci-vvnn.log' (lspci -vvnn output)
2008-03-31 02:40:28 Dave Shaw bug added attachment 'version.log' (/proc/version_signature output)
2008-03-31 02:42:13 Dave Shaw bug added attachment 'uname-a.log' (uname -a output)
2008-04-09 18:07:35 Leann Ogasawara linux: importance Undecided Medium
2008-04-09 18:07:35 Leann Ogasawara linux: assignee ubuntu-kernel-team
2008-04-09 18:07:35 Leann Ogasawara linux: status Incomplete Triaged
2008-09-06 09:39:37 Leann Ogasawara linux: status Triaged Fix Released
2008-09-06 09:39:37 Leann Ogasawara linux: statusexplanation 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.