[Bug 94822] System hangs when some video output is disabled/enabled on Skylake platform in double/triple display configuration

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed May 4 20:58:13 UTC 2016


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

Jim Bride <jim.bride at linux.intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #3 from Jim Bride <jim.bride at linux.intel.com> ---
There are a couple of odd things that I’ve seen while looking over the first
dmesg log.  The first is that the sink devices advertise that they only support
up to 2.7Gbps transfer rate, which makes me suspect that they are older models.
Could you please tell us the make and model numbers of the displays in
question?  The second is that there are quite a number of watermark WARNs.  The
kernel log lists the version as 4.6.999, so I really don’t have a clue
specifically how recent this is, and I have to assume that it’s based on the
kernel.org kernel.  There have been some fixes in the watermarking area
recently, so it would be helpful to try and reproduce this issue using the same
hardware and drm-intel-nightly (assuming this is not drm-intel with the version
info changed.) Finally, although the stated reason for the patches referenced
in the thread is DP MST, it might be worth trying the two attached patches on
top of drm-intel-nightly, assuming the problem reproduces against that kernel. 
The issue being fixed is exacerbated by MST, but it is a general racy problem
with the frame buffer connector counting if I’m interpreting the information
correctly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact 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/20160504/923edd23/attachment-0001.html>


More information about the intel-gfx-bugs mailing list