Comment 12 for bug 1726061

But that bisection may be leading toward a dead end or at least a moot point. The behavior which I am calling "bad" there is different from what I am currently seeing in later RCs and in 4.14.0.

In, for example, my last "bad" commit 126f760ca94, upon suspend the machine does actually suspend but can't wake.

In 4.14rc6, 4.14rc8, and 4.14, now upon suspend I am seeing the display power off and everything spins down but only for a moment -- then it immediately resumes. wifi and graphics seem to work OK at that point. The main remaining problem is just failure to remain suspended.

That is true at least upon first suspend. In one of those builds I did see a case where a second suspend would spin down, try to spin up, but although the display backlight did come back on the machine remained unresponsive.

I am not sure why the later RCs and in particular rc6 switched to this new failure mode. In my earlier notes it's clear that they used to be failing more like the way 126f760ca94 still behaves.