[Bug 86697] New: [BSW] System fail to enter S4 at the second cycle to execute "echo disk > /sys/power/state" command

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Nov 25 03:11:45 PST 2014


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

            Bug ID: 86697
           Summary: [BSW] System fail to enter S4 at the second cycle to
                    execute "echo disk > /sys/power/state" command
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: wendy.wang at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 109999
  --> https://bugs.freedesktop.org/attachment.cgi?id=109999&action=edit
s4-fail-dmesg

==System Environment==
BSW RVP FAB1 with B1 CPU
BIOS: V41.0
KSC: 1.05

==Failed Kernel==
BSW alpha release kernel: tag: drm-intel-testing 2014-11-21

==Bug detailed description==
-----------------------------
With i915 driver loaded the fail symptom as below:
1. 1st cycle to execute "echo disk > /sys/power/state"
2. test machine will enter S4 successfully, then automatically resume back from
S4.
3. Second time to try executing "echo disk > /sys/power/state", system will
fail to enter into S4 
s4-fail-dmesg log file attached.

if disable i915 display with "modprobe.blacklist=i915" parameter, do not have
this S4 issue, which mean second time still can put system into S4, and system
will not automatically wake up.
Attached one good dmesg file for compare: s4-good-dmesg-i915-disable log

-- 
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/20141125/51053c07/attachment.html>


More information about the intel-gfx-bugs mailing list