<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#c6">Comment # 6</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:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> Imre Deak</a> <pre>(In reply to Jens from <a href="show_bug.cgi?id=82864#c3">comment #3</a>) > In response to the comment posted at bugzilla.kernel.org: > > > Jens, have you seen the problem since your last report (with or w/o the fixes)? > > No. > > > Could you still try if you can reproduce the problem with the latest -nightly > > kernel and the same tree with the fixes reverted (resetting to 598ae05fd937 - > > "drm/i915: Emit even number of dwords when emitting LRIs"). > > I have checked out the linux-drm-nightly tree as of yesterday (3.18rc1, > 88a443f45) and have tried several suspend/resume on one machine during "make > -j4". Except for one watchdog timeout (networking) I have not experienced > any problems except for the fact that the resume seems to take a little > longer(?) than with 3.17rc1. Ok. Not sure about the extra delay. Perhaps connected to the network timeout? But for me the important now is that with -nightly you don't see the original (more serious) problem. > Regarding 598ae05fd937, "git show" does not find it, but I found this: > <a href="http://cgit.freedesktop.org/drm-intel/commit/">http://cgit.freedesktop.org/drm-intel/commit/</a> > ?id=22a916aaa187946e8df724ab7838a0c13b45a9f4 > Is this the same commit? Do you want me to reverse patch it onto > 598ae05fd937 and retest? Yes that's the right commit, just before the suspend-fix patchset went in. Maybe, I gave the wrong SHA1, or -nightly got rebased (it gets rebased regularly). It would help if you could git reset to that commit and see if you can reproduce the problem. I think I will close this bug in any case, but it would help to know if it got fixed by the suspend-fix patchset (that you revert with the git reset), or something else since 3.17rc1. Thanks!</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>