[Bug 104228] New: [CNL] HDMI video doesn't come back after S3 state , only with HDMI connected

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Dec 12 16:34:15 UTC 2017


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

            Bug ID: 104228
           Summary: [CNL] HDMI video doesn't come back after S3 state ,
                    only with HDMI connected
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: elio.martinez.monroy at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 136118
  --> https://bugs.freedesktop.org/attachment.cgi?id=136118&action=edit
dmesg log

System Environment
 =======
 Ubuntu 17.04 
 4.15.0-rc2-drm-intel-qa-ww49-commit-bdf9b36+
 Default graphic configuration from Ubuntu 17.04 without any kind of firmware
(No DMC GuC or HuC)
 Regression?
 =======
 No

Bug detailed description
 =======
 After booting up without any background process, the system is not able to
recover image on Acer HDMI monitor after a S3 instruction "#echo mem >
/sys/power/state"
 Reproduce Steps
 ==============
 login in to your linux account
 open terminal and execute as sudo "echo mem > /sys/power/state"
 Expected Result
 =============
 The system should recover getting back image on HDMI monitor
 Actual Result
 ===========
 No screen available but system is up through ssh
 Analysis & Root Cause
 ===================
 This problem is not present with eDP

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171212/6e03d171/attachment.html>


More information about the intel-gfx-bugs mailing list