[Bug 97965] New: [BSW] External HDMI monitor suddenly shows solid color when playing Youtube video at 1080p

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 97965
           Summary: [BSW] External HDMI monitor suddenly shows solid color
                    when playing Youtube video at 1080p
           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: ykku16dev2 at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 126837
  --> https://bugs.freedesktop.org/attachment.cgi?id=126837&action=edit
dmesg captured with drm.debug=0x1e log_buf_len=1M

Steps to reproduce the issue:
=============================
1.  Boot BSW-based machine
2.  Plug in external HDMI monitor at 1920x1080 resolution in extended mode
3.  Play Youtube video at 1080p and at full screen on the HDMI monitor (I did
not route audio to the HDMI monitor.)

The problem usually happens within 30 to 40 minutes.  Video playback will be
fine most of the time.  However, you will see intermittent flicker or tearing. 
The HDMI monitor will suddenly display a solid color (usually dark purple). 
The only way I know to recover from this is to reboot the machine.

Reproducibility:
================
The rate of occurrence is roughly 80%.

Information about my system:
============================
system architecture: x86_64
kernel version: 4.8.0-rc8-02558-g6fa2afd-dirty (built from drm-intel-nightly on
9/28/2016)

-- 
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160928/50fa536b/attachment.html>