[Bug 84903] New: [BSW] System fail to enter S3 with system hang up after load i915 driver

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 84903
           Summary: [BSW] System fail to enter S3 with system hang up
                    after load i915 driver
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: critical
          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

==System Environment==
--------------------------
Regression: No. 
It's first run tests on BSW

Non-working platforms: BSW

==kernel==
--------------------------
origin/drm-intel-nightly:
BOOT_IMAGE=kernels//nightly_parents/2014_10_11/drm-intel-nightly/ea4bec8e96ea8b33b49a7892c1c7f20041a56da6/bzImage_x86_64
root=/dev/sda4 drm.debug=0xe
modules_path=kernels//nightly_parents/2014_10_11/drm-intel-nightly/ea4bec8e96ea8b33b49a7892c1c7f20041a56da6/modules_x86_64/lib/modules/3.17.0_drm-intel-nightly_ea4bec_20141011+
acpi_rsdp=0x7b729014 kexec_jump_back_entry=0x5434a8e8

==Bug detailed description==
-----------------------------
1. With i915 driver loaded and boot system 
2. execute command as root "echo mem > /sys/power/state", system will hang up
with board debug LED shows"000A"
The serial port error log has not been captured, will upload once we got it. 

Isolation:
1. disable i915 driver and boot system, execute command as root "echo mem >
/sys/power/state"
2. System will enter S3 quickly check from dmesg and resume back automatically.

-- 
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/20141011/91437045/attachment.html>