Comment 187 for bug 226279

Hi All,

I'm closing the Intrepid nomination because there has been no reference that this is an issue with the 2.6.27 Intrepid kernel. This bug should have been resolved in Hardy. If this is not the case for you please open a new report. Additionally, if your bug was marked a duplicate of this report and your bug is not yet resolved, please undup your bug from this one.

Another thing to note about suspend/resume issues is that even though you may be experiencing the same symptom as everyone else, it really is usually hardware specific. For that reason, it's helpful that when subscribing to existing bug reports, or marking bugs as a duplicate of another, you should make sure you have the same hardware as the original bug reporter. If this is not the case it is best to open a new bug report (or not mark a bug as a duplicate). Otherwise bug reports become bloated and hard to follow with subscribers reporting against multiple pieces of hardware which are likely running different drivers and will be requiring different fixes. Thanks again for your cooperation, we really appreciate it.