[Bug 93578] Intel HD 520 failed to train DP when connected with a external monitor

[bugzilla-daemon at freedesktop.org]

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

--- Comment #5 from Igor Krivenko <igor.s.krivenko at gmail.com> ---
I can confirm this (or a similar?) issue with my Dell XPS 13 9350 laptop and a
USB-C adapter DA200.

With the latest BIOS update, USB, Ethernet and VGA ports on the adapter work
like a charm. A FullHD external monitor connected via HDMI cannot detect input
signal. It is remarkable that the same monitor connected to the same laptop
through another USB-C-to-HDMI adapter (Cable Matters) works properly.

Here is a fragment of dmesg (Gentoo, the latest kernel 4.4.0):

[ 2084.708909] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR*
5.4 Gbps link rate without HBR2/TPS3 support
[ 2084.721795] ------------[ cut here ]------------
[ 2084.721803] WARNING: CPU: 3 PID: 1917 at
drivers/gpu/drm/i915/intel_pm.c:3597 skl_update_other_pipe_wm+0x1bd/0x1d0
[i915]()
[ 2084.721804] WARN_ON(!wm_changed)
[ 2084.721805] Modules linked in:
[ 2084.721806]  cmac rfcomm bnep btusb i915 btbcm btintel bluetooth dcdbas
x86_pkg_temp_thermal kvm_intel kvm uvcvideo videobuf2_vmalloc videobuf2_memops
videobuf2_v4l2 r8152 videobuf2_core mii irqbypass brcmfmac input_leds led_class
brcmutil intel_gtt efivarfs
[ 2084.721818] CPU: 3 PID: 1917 Comm: X Tainted: G        W      
4.4.0-gentoo-r1 #12
[ 2084.721819] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.1.9
12/18/2015
[ 2084.721820]  ffffffffc03f0bc0 ffff88006815f788 ffffffff812a0a69
ffff88006815f7d0
[ 2084.721822]  ffff88006815f7c0 ffffffff81058958 ffff8802759c1000
ffff88006815f8ec
[ 2084.721823]  ffff8802759c4000 0000000000000000 ffff88006815f858
ffff88006815f820
[ 2084.721825] Call Trace:
[ 2084.721829]  [<ffffffff812a0a69>] dump_stack+0x4b/0x72
[ 2084.721831]  [<ffffffff81058958>] warn_slowpath_common+0x78/0xb0
[ 2084.721833]  [<ffffffff810589d7>] warn_slowpath_fmt+0x47/0x50
[ 2084.721836]  [<ffffffff81070000>] ? task_active_pid_ns+0x10/0x30
[ 2084.721853]  [<ffffffffc034587d>] skl_update_other_pipe_wm+0x1bd/0x1d0
[i915]
[ 2084.721857]  [<ffffffffc0345aa4>] skl_update_wm+0x214/0x710 [i915]
[ 2084.721860]  [<ffffffff8108da90>] ? wake_atomic_t_function+0x60/0x60
[ 2084.721865]  [<ffffffffc0349d99>] intel_update_watermarks+0x19/0x20 [i915]
[ 2084.721872]  [<ffffffffc039d7cb>] haswell_crtc_enable+0x36b/0x860 [i915]
[ 2084.721879]  [<ffffffffc039951f>] intel_atomic_commit+0x46f/0x13b0 [i915]
[ 2084.721886]  [<ffffffff813847b9>] ? drm_atomic_check_only+0x189/0x580
[ 2084.721887]  [<ffffffff8138409b>] ?
drm_atomic_set_crtc_for_connector+0x1b/0x80
[ 2084.721889]  [<ffffffff81384be2>] drm_atomic_commit+0x32/0x50
[ 2084.721900]  [<ffffffff813643a1>] drm_atomic_helper_set_config+0x71/0xb0
[ 2084.721902]  [<ffffffff8137569d>] drm_mode_set_config_internal+0x5d/0xf0
[ 2084.721904]  [<ffffffff81379949>] drm_mode_setcrtc+0x3b9/0x4d0
[ 2084.721906]  [<ffffffff8136c0fd>] drm_ioctl+0x14d/0x530
[ 2084.721907]  [<ffffffff81379590>] ? drm_mode_setplane+0x1a0/0x1a0
[ 2084.721910]  [<ffffffff8124f1c7>] ? selinux_file_ioctl+0xf7/0x1c0
[ 2084.721912]  [<ffffffff811547f3>] do_vfs_ioctl+0x283/0x460
[ 2084.721914]  [<ffffffff81246dfe>] ? security_file_ioctl+0x3e/0x60
[ 2084.721915]  [<ffffffff81154a44>] SyS_ioctl+0x74/0x80
[ 2084.721917]  [<ffffffff810f5be8>] ? context_tracking_enter+0x18/0x20
[ 2084.721920]  [<ffffffff81667bdb>] entry_SYSCALL_64_fastpath+0x16/0x6e
[ 2084.721921] ---[ end trace 06dab2c20a0a06d0 ]---

Maybe, this issue has something to do with 92932.

-- 
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/20160128/c45e7cab/attachment.html>