Comment 4 for bug 213988

I found the attached commit in upstream, applied it to 2.6.24-19.41. Six suspend/resume cycles haven't shown the problem yet. I'll continue testing.

(By the way, the kernel my machine was actually running most recently was 2.6.24-21, not 2.6.24-19, but an apt-get source of linux-image-2.6.24-21-generic gets me a linux-2.6.24/ with a debian/changelog whose most recent entry is for 2.6.24-19.41. I'm a little confused as to how to get the latest source....)