<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#c10">Comment # 10</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#c8">comment #8</a>) > Created <a href="attachment.cgi?id=108530" name="attach_108530" title="dmesg output of "preload: Corrupted page table at address 1dd4146"">attachment 108530</a> <a href="attachment.cgi?id=108530&action=edit" title="dmesg output of "preload: Corrupted page table at address 1dd4146"">[details]</a> > dmesg output of "preload: Corrupted page table at address 1dd4146" > > Unforunately I have just experienced another error upon resume. This > prevented the machine from shutting down cleanly (although it was still > working when I resumed). This is the first time this happened, though. > > [32938.478751] video LNXVIDEO:00: Restoring backlight state > [32993.327894] preload: Corrupted page table at address 1dd4146 > [32993.327919] PGD 36141067 PUD c66a8067 PMD 4341434143414341 BAD > [32993.327936] Bad pagetable: 000b [#1] SMP > ... (see attachment) Ok, this doesn't look good. Could you try if you can reproduce it with the same kernel booting with nomodeset? (In reply to Jens from <a href="show_bug.cgi?id=82864#c9">comment #9</a>) > With 3.17rc5+ (the above commit) I can not reproduce the same error as > above, but after a couple attempts the system simply refuses to suspend - > the 'pm-hibernate' process freezes. Also it is not possible to shut down > cleanly any more. > > There is nothing in the logs or in dmesg to hint at what might be happning > (that I could recognize). > > I will try again tomorrow to see if I can reproduce this. Actually now trying this commit is less important, since even -nightly has the problem, so let's try to narrow down things in -nightly.</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>