<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit" href="https://bugs.freedesktop.org/show_bug.cgi?id=103277#c26">Comment # 26</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit" href="https://bugs.freedesktop.org/show_bug.cgi?id=103277">bug 103277</a> from <a class="email" href="mailto:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> dwagner</a> <pre>(In reply to Harry Wentland from <a href="show_bug.cgi?id=103277#c25">comment #25</a>) > Is this fixed on recent kernels? If so, can we close this one? The fix seems to be included in 4.17.2. Remaining issue mentioned above: System will still crash on S3-resume if I use the "drm.edid_firmware=edid/LG_EG9609_edid.bin" kernel command line option. (Not as severe as the "crashes under all conditions" issue originally reported.) Should this be covered by a separate bug report? Just for reference, a different S3 resume issue on which I just posted a different bug report: <a class="bz_bug_link bz_status_NEW " title="NEW - "BUG: unable to handle kernel paging request at 0000000000002000" at amdgpu_vm_cpu_set_ptes at S3 resume" href="show_bug.cgi?id=107065">https://bugs.freedesktop.org/show_bug.cgi?id=107065</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>