Comment 24 for bug 86099

Leann:
Sorry, I REALLY don't want to retest this until the next "major" (2.6.x) kernel revision change or final Hardy release. I have seen nothing that suggests this is going to have changed so arbitrarily retesting minor kernel revisions just isn't worth the effort I'm afraid.

What I should have also noted is that I have tried everything on http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-advanced.html (which includes trying to using pm_trace - when the system restarts no hash is ever matched). I can also assure you that there is nothing of interest in dmesg... because the system reboots when you try to resume. The output of the post suspend boot from later kernels is pretty similar to the kern.log that was posted earlier in this bug.