<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Warnings after resume in i915" href="https://bugs.freedesktop.org/show_bug.cgi?id=65497#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Warnings after resume in i915" href="https://bugs.freedesktop.org/show_bug.cgi?id=65497">bug 65497</a> from <a class="email" href="mailto:zboszor@pr.hu" title="Zoltán Böszörményi <zboszor@pr.hu>"> Zoltán Böszörményi</a> <pre>(In reply to <a href="show_bug.cgi?id=65497#c11">comment #11</a>) > That the BIOS lit up a pipe, also means that it probably scribbled over > quite a few of our data structures in device memory. I see. Does it mean that my other bug reported at <a href="https://bugzilla.kernel.org/show_bug.cgi?id=59401">https://bugzilla.kernel.org/show_bug.cgi?id=59401</a> is a consequence of this (supposedly BIOS) bug? The bug is about immediate resuming in about 40% of the suspend attempts. Also how can it be worked around? Windows (XP and 7) must keep its data somewhere else otherwise it wouldn't be able to suspend the machine reliably.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>