On 11/1/10, Philip Guenther <[email protected]> wrote: ... > I mean, come on, "worked before, stopped working, still doesn't work" > gives us nothing to go on for what broke your box. That last commit > was what broke resume on _my_ thinkpad...
...or not. Further testing on my T60 (running i386) and T510 (running amd64) seems to indicate that Jordan's commit was just fine. My suspend problems appear to have been elsewhere as I'm now suspending and resuming just fine with the reverted commit back in my tree. So, while that change hasn't been recommitted yet, if you're running into problems with suspend or resume on a box that it worked fine on before, some sort of "worked with kernel from <date1>, failed on kernel from <date2>" really would assist in tracking this down. And build from a clean directory. Philip Guenther
