<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW desktop] Resume from s4 causes call trace and system hang, with cool boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=63586#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW desktop] Resume from s4 causes call trace and system hang, with cool boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=63586">bug 63586</a> from <a class="email" href="mailto:cancan.feng@intel.com" title="cancan,feng <cancan.feng@intel.com>"> cancan,feng</a> <pre>(In reply to <a href="show_bug.cgi?id=63586#c10">comment #10</a>) > So just to check: This failure after 95 resume cycles was on a kernel > previously considered good? I.e. do we need to assume that this bug has > always been there and this is not a regression, just some timing changes > made it more likely? Hi, I have double checked this issue, and found it is a regression, and I have bisected it. Here is bisect information: 88adfff1ad5019f65b9d0b4e1a4ac900fb065183 is the first bad commit commit 88adfff1ad5019f65b9d0b4e1a4ac900fb065183 Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> Date: Thu Mar 28 10:42:01 2013 +0100 drm/i915: hw readout support for ->has_pch_encoders Now we can ditch the checks in the Haswell disable code. v2: add support for Haswell Reviewed-by: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>> Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> :040000 040000 3680d704a4f13869e0e5094699a9c96dcf7dc45b 78d850e8e904670ad377fc92b75993dfec59933a M drivers</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>