<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [SNB] Suspend-to-disk occasionally fails to suspend." href="https://bugs.freedesktop.org/show_bug.cgi?id=48913#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [SNB] Suspend-to-disk occasionally fails to suspend." href="https://bugs.freedesktop.org/show_bug.cgi?id=48913">bug 48913</a> from <a class="email" href="mailto:da_fox@mad.scientist.com" title="Da Fox <da_fox@mad.scientist.com>"> Da Fox</a> <pre>(In reply to <a href="show_bug.cgi?id=48913#c2">comment #2</a>) > Looks like i915 is getting suspended (the "suspend of devices complete after > 1128.954 msecs" seems to indicate that at least). > > We can try to be sure though by removing the i915 device. Can you try using > a stress script like > <a href="http://ubuntu.5.n6.nabble.com/PATCH-0-1-Jaunty-suspend-resume-stress-test">http://ubuntu.5.n6.nabble.com/PATCH-0-1-Jaunty-suspend-resume-stress-test</a>- > scripts-td368223.html and isolate which module might be breaking things? It > could also be an ACPI bug, in which case a BIOS upgrade may help... I don't have any modules, except for 'bbswitch'. This is because everything is compiled into the kernel. Would doing a hibernate-stresstest without X running be of any help in pin-pointing the problem? The BIOS is at the the second-to-last version (at least, it was the second-to-last version the last time I checked). This is because of a power-management bug, which is (hopefully) almost resolved. After that I will test the newer version of the BIOS again, however it appeared that windows might also have had a higher power consumption under that BIOS, in which case I will need stick with my current BIOS version.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>