<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Hardware freeze after resume from suspend" href="https://bugs.freedesktop.org/show_bug.cgi?id=67878#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Hardware freeze after resume from suspend" href="https://bugs.freedesktop.org/show_bug.cgi?id=67878">bug 67878</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="show_bug.cgi?id=67878#c18">comment #18</a>) > Linux commit 992956189de58cae9f2be40585bc25105cd7c5ad is bad. That seems thoroughly unlikely. commit 992956189de58cae9f2be40585bc25105cd7c5ad Author: Eric W. Biederman <<a href="mailto:ebiederm@xmission.com">ebiederm@xmission.com</a>> Date: Mon Dec 17 17:19:36 2012 -0800 efi: Fix the build with user namespaces enabled. This doesn't apply to your situation on many levels... this is a build fix... to efi vars... I bet if you checkout to 992956189de58cae9f2be40585bc25105cd7c5ad^ then you will still have a bad kernel. You should probably redo the bisect, but look at the bisect log (git bisect log) and keep all your "bad" commits, since they are likely indeed bad. But you may have been a bit too eager in calling out the "good" kernels. (See git help bisect for how to start with a bunch of bad commits.) While you're at it, you may want to re-test whether 3.7 really is good.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>