[Bug 92826] New: [BSW] Using multiple DP, can cause second output to blank until reboot by quickly transition cursor across screen border

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 92826
           Summary: [BSW] Using multiple DP, can cause second output to
                    blank until reboot by quickly transition cursor across
                    screen border
           Product: DRI
           Version: XOrg 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: max at warheads.net
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 119412
  --> https://bugs.freedesktop.org/attachment.cgi?id=119412&action=edit
4.3.0 -drm-intel-nightly dmesg, drm info, intel_reg dump, vbios, xrandr verbose

On the Braswell NUC NUC5CPYB (and another Lenovo platform) while using multiple
connected outputs, one can cause the second output (DP2/HDMI2) to go to a solid
color and/blank until reboot.

On this NUC, the HDMI is port 2, on Lenovo hardware I can interchange all
output types on both ports and produce this result as well (DP,HDMI,VGA,DVI)

Attached are debug information from Arch Linux kernels 4.2.5, 4.3.0 and 4.3.0
built from drm-intel-nightly

To reproduce:
- Attached both outputs
- boot into X/desktop
- configure monitors as separate displays
- move cursor across screen borders between the two monitors at a high rate
(wiggle the mouse fast)

You will see:
- At first, a slight flicker of the display, or a tarnish of the coloring of
DP2
- DP2's output will eventually block into a single color
- dmesg will have an output regarding drm:intel_cpu_fifo_underrun

Attached will be a tarball of the information requested for all three kernels.

-- 
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/20151104/c42b7c6f/attachment.html>