[Bug 63454] Call Trace when resume from S3

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Apr 14 19:22:07 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=63454

--- Comment #2 from shui yangwei <yangweix.shui at intel.com> ---
Created attachment 77968
  --> https://bugs.freedesktop.org/attachment.cgi?id=77968&action=edit
S3 call trace dmesg

(In reply to comment #1)
> Self-checks gone wrong, should be fixed with
> 
> commit f8100b182d06fe1c576cb0602adc15450ddb460a
> Author: Daniel Vetter <daniel.vetter at ffwll.ch>
> 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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130415/a55ceb4e/attachment.html>


More information about the intel-gfx-bugs mailing list