<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [HSW] resume from s4 sporadically causes call trace and system hang, with warm boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=65496#c36">Comment # 36</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [HSW] resume from s4 sporadically causes call trace and system hang, with warm boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=65496">bug 65496</a> from <a class="email" href="mailto:przanoni@gmail.com" title="Paulo Zanoni <przanoni@gmail.com>"> Paulo Zanoni</a> <pre>Hi I did some more investigation and I discovered the following: - It seems that, after resuming, if you run "slabinfo -v" (from tools/vm/), there's a good chance you'll see dmesg messages saying we detected corruption on our slabs. It seems to me that it is much much easier to reproduce the bug with "hibernate, resume, run slabinfo -v, check dmesg, hibernate, resume, etc" than with just "hibernate, resume". Can you confirm that? - It also seems that the bug goes away if the kernel that resumes the machine doesn't load i915.ko. So an experiment you can try is: boot the machine normally, with i915.ko loaded, tell it to hibernate. Then make the machine wake-up, and use the "modprobe.blacklist=i915" option when loading the kernel that will resume the machine. After it resumes, check if the bug is there (possibly with slabinfo -v). The bug should be gone. Can you please confirm that? Thanks, Paulo</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>