<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Call Trace when resume from S3" href="https://bugs.freedesktop.org/show_bug.cgi?id=63454#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Call Trace when resume from S3" href="https://bugs.freedesktop.org/show_bug.cgi?id=63454">bug 63454</a> from <a class="email" href="mailto:yangweix.shui@intel.com" title="shui yangwei <yangweix.shui@intel.com>"> shui yangwei</a> <pre>Created <a href="attachment.cgi?id=77968" name="attach_77968" title="S3 call trace dmesg">attachment 77968</a> <a href="attachment.cgi?id=77968&action=edit" title="S3 call trace dmesg">[details]</a> S3 call trace dmesg (In reply to <a href="show_bug.cgi?id=63454#c1">comment #1</a>) > Self-checks gone wrong, should be fixed with > > commit f8100b182d06fe1c576cb0602adc15450ddb460a > Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> > Date: Thu Apr 11 20:22:50 2013 +0200 > > drm/i915: don't check inconsistent modeset state when force-restoring > > which is in latest dinq. Can you please test and confirm? I tried this commit, and the "Call Trace" still exists. I attached the dmesg here. In this round testing S3 & S4 blocked our tests. Each platform has different appearances. I will send you a table to describe all of the issues by email.</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>