<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HSW i915 MSI-7817] S4 resume on Haswell causes memory corruption (OOM, ext4_, ...)" href="https://bugs.freedesktop.org/show_bug.cgi?id=82864#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HSW i915 MSI-7817] S4 resume on Haswell causes memory corruption (OOM, ext4_, ...)" href="https://bugs.freedesktop.org/show_bug.cgi?id=82864">bug 82864</a> from <a class="email" href="mailto:jens-bugs.freedesktop.org@spamfreemail.de" title="Jens <jens-bugs.freedesktop.org@spamfreemail.de>"> Jens</a> <pre>Summary: 1) I could not reproduce the above corruption error with "nomodeset" and only using the console (no X) after about 10 suspend/resume cycles during a parallel make -j4. 2) Upon restarting lightdm and logging in, this is printed to the console when using "nomodeset": [+21.57s] WARNING: Error activating login1 session: GDBus.Error:org.freedesktop.DBus.Error.Failed: Operation not supported I do not get this when not using this boot parameter. Full boot command line: BOOT_IMAGE=/vmlinuz-3.18.0-rc1+ root=/dev/mapper/ubuntu--vg-root ro quiet splash no_console_suspend=1 <a href="mailto:netconsole=6666@192.168.178.59">netconsole=6666@192.168.178.59</a>/eth0,<a href="mailto:6666@192.168.178.62">6666@192.168.178.62</a>/ crashkernel=384M-:128M vt.handoff=7 3) After console freezes, there is nothing strange in the logs (at least no backtrace, oops or anything obvious.)</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>