[Bug 105655] New: GeminiLake HDMI hotplug between 4K at 60 and 4K at 30 monitors

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 21 10:41:41 UTC 2018


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

            Bug ID: 105655
           Summary: GeminiLake HDMI hotplug between 4K at 60 and 4K at 30
                    monitors
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: antonychen at qnap.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Environment:
Mainboard: Intel RVB
BIOS: AMI
OS: Ubuntu 17.10
Monitors: ViewSonic VP2780-4K (A), ASUS PB287Q (B)
TV: LG 49UJ630T (C)

A and C support 4K at 60, B support 4K at 30

My steps:
1. Plug A or C and bootup
2. After OS finishes booting, unplug HDMI cable in console mode
Then dmesg shows the error messages:
[drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] *ERROR* Failed to
read TMDS config: -6
[drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS ratio failed

3. Plug B
Then there is not signal to B, and dmesg shows the error messages above again.

4. Unplug B and Plug A or C, then A or C display normally.


I also do some tests when I start X:
1. Plug A and bootup
2. sudo xinit
3. unplug HDMI cable and plug B, there is not signal to B
4. xrandr --output HDMI1 --off
Then dmesg shows the error messages:
[drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] *ERROR* Failed to
read TMDS config: -6
[drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS ratio failed

5. xrandr --output HDMI1 --auto
Then there is not signal to B, and dmesg shows the error messages above again.

In the second testing, if I use C to replace A, then there IS signal to B in
the 5th step.

-- 
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/20180321/054f8a27/attachment-0001.html>


More information about the intel-gfx-bugs mailing list