Comment 549 for bug 359392

No Ubuntu developers are saying that users who want stable systems should have stayed with intrepid, nor that users who want a fixed system should upgrade to the karmic alpha. However, Launchpad Bugs is not a discussion forum, it is a tool for developers and users to communicate in order to *get bugs fixed*. If you're not prepared to help with this process by testing (including, if it comes down to it, testing with karmic alpha packages), that's ok, but then please refrain from commenting on this bug so that the communication channel can be kept clear for those who *are* in a position to help get this bug fixed.

As it stands, with 548 comments this bug log is already pretty much useless for tracking the actual freeze bug in question. One factor here appears to be that there are a number of different freezes happening, each with a different cause, but it's very difficult to distinguish between them because of the nature of the symptom in question.

Some of these freezes are fixed for people using the intel driver from jaunty-proposed; others require kernel changes which are still in the process of being prepared for jaunty; others are still present even in karmic. To be able to make sense of these bugs, we really need everyone to do the following:

1. File a separate bug report for your issue, and post the bug number here. If you already filed your own bug and it was marked as a duplicate of this one, then you don't need to do this again; but please send your follow-up comments to your individual bug report, so that as we begin to distinguish between these multiple freeze bugs, your comments stay with the right bug.
2. Follow the directions at https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test/ to capture the information needed to diagnose your freeze, and send it to the bug report. Note that you will need to be able to ssh in from another machine in order to capture this information, so be sure you have openssh-server installed before trying to reproduce the bug!
3. If the freeze is not reproducible for you after upgrading to the 2.6.30-rc5 kernel needed for capturing the debugging information, please note that in the bug as well.
4. For *each subsequent freeze on your machine*, repeat step 2. This ensures that we don't mistakenly end up trying to debug two separate kinds of freezes on a single machine without realizing it.

Your cooperation here will go a long way towards helping us break this confused bug down into manageable chunks.