<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [PATCH] Fix_stuck_on_bsd_ring for Clarkdale/Ironlake and kernel 4.4.x" href="https://bugs.freedesktop.org/show_bug.cgi?id=99737#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [PATCH] Fix_stuck_on_bsd_ring for Clarkdale/Ironlake and kernel 4.4.x" href="https://bugs.freedesktop.org/show_bug.cgi?id=99737">bug 99737</a> from <a class="email" href="mailto:jrf@mailbox.org" title="Rainer Fiebig <jrf@mailbox.org>"> Rainer Fiebig</a> <pre>(In reply to Carlos Jimenez from <a href="show_bug.cgi?id=99737#c1">comment #1</a>) > dont work with latest kernel > > it hibernates > but dont resume at all > just black screen and reboot . > > have you tried with newer kernels of the 4.4 branch ? Cursorily tested it with 4.4.59: the patch applied well like before, kernel compiled without error-messages, s2disk/s2both/resume all well, no problems so far. So it works nicely here but probably needs improvement. I also have not tested it with newer Intel-CPUs. The sad thing is that obviously non of the Intel-devs took a look. It shouldn't take a pro too long (5 minutes?) to see whether the patch is worth improving on or simply total crap (not here, though). Or provide a better solution at long last! I had even sent it directly to the guy who had written the a/m committs and the kernel-maintainer but got no response. So be it, I've done enough in this matter. The problems for older Intel CPUs/GPUs started with 4.2 and lasted up to and including 4.7. That's 6 kernels, including a long-term-kernel that is used by quite a few distributions, stands at .59 and is still not fixed. Nothing to be proud of, imo.</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>