[Bug 88843] New: [BDW-Y Regression] S3 will call trace for the third or more time and can't do S3 any more

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 88843
           Summary: [BDW-Y Regression] S3 will call trace for the third or
                    more time and can't do S3 any more
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Keywords: bisect_pending
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: li.l.xu at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 112902
  --> https://bugs.freedesktop.org/attachment.cgi?id=112902&action=edit
call trace

System Environment:
--------------------------

Regression:  
good commit:   
cd52471999ef08bca35568525c1d85d883ffedb6





Platform: BDW-Y


Kernel: 
--------------------------

-nightly latest 9438dec1c7538fdd3b356a59ca929632fcb57132



Bug detailed description:
-----------------------------
I have tried S3 on BDW-Y with the night-latest kernel. And the first S3 can
work normally.The second and third times, it has write error: Resource
temporarily unavailable. 
If any more ,it will call trace and can’t S3 any more.
Since the machine doesn't have any serial port or built-in network card, we
can't catch the dmesg. And the call trace message seen as the attached picture.

Steps:
---------------------------
echo mem>/sys/power/state for several times.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list 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/20150128/353cf038/attachment.html>