<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [Intel-gfx] As of kernel 4.3-rc1 system will not stay in S3 suspend [REGRESSION][BISECTED]" href="https://bugs.freedesktop.org/show_bug.cgi?id=92414#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [Intel-gfx] As of kernel 4.3-rc1 system will not stay in S3 suspend [REGRESSION][BISECTED]" href="https://bugs.freedesktop.org/show_bug.cgi?id=92414">bug 92414</a> from <a class="email" href="mailto:dsmythies@telus.net" title="Doug Smythies <dsmythies@telus.net>"> Doug Smythies</a> <pre>While in <a href="show_bug.cgi?id=92414#c19">comment 19</a> above, I mentioned that this issue no longer occurred on my computer, I did try to go back and re-install an older version of my distribution (Ubuntu) on another partition in an attempt to re-create the issue. I was unsuccessful. I tried without success again today. My original work and kernel bisection was good and repeatable. I do not understand why I can not re-create the failure scenario now. I can only assume it is because I did not install from the exact same iso starting point. The only hardware change was the hard disk that had failed. In <a href="show_bug.cgi?id=92414#c13">comment 13</a> there is a reference to a bug with similar symptoms (<a class="bz_bug_link bz_status_NEW " title="NEW - [SNB]System fails to suspend from second time in "drm_suspend_s3" test" href="show_bug.cgi?id=90253">https://bugs.freedesktop.org/show_bug.cgi?id=90253</a>). However it can not be the same root issue, because, if I understand the dates correctly, the commit that this was isolated to did not exist when that bug report was entered.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>