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

Fri Feb 3 22:48:18 UTC 2017

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

--- Comment #87 from smz <smz at mailfence.com> ---
I think I'm having a related problem. I have a laptop (Dell Precision 5510)
with two graphics cards (nvidia and Intel):

00:02.0 VGA compatible controller: Intel Corporation Skylake Integrated
Graphics (rev 06)
01:00.0 3D controller: NVIDIA Corporation GM107GLM [Quadro M1000M] (rev a2)

The Intel GPU is currently the one in use.

This laptop has a 4K display, and I have two external monitors (1920x1080)
connected via a USB-C docking station. The docking station has both a
DisplayPort and an HDMI port, which is how the monitors are connected. I've set
the laptop monitor to 1920x1080 since my desktop environment doesn't support
different DPIs on different monitors.

Frequently, when I plug or unplug the USB-C docking station, the whole machine
just hangs. I can't change to a tty, and I have to hard reset to use the
machine again.

When the machine freezes, similar looking kernel messages are left in the log:

Feb  3 13:29:51 hostname kernel: [73609.775796] Hardware name: Dell Inc.
Precision 5510/0N8J4R, BIOS 1.2.18 12/01/2016
Feb  3 13:29:51 hostname kernel: [73609.775802] Workqueue: events
drm_dp_destroy_connector_work [drm_kms_helper]
Feb  3 13:29:51 hostname kernel: [73609.775804]  0000000000000286
000000003697ffc2 ffff8802240f7a28 ffffffff813f7c63
Feb  3 13:29:51 hostname kernel: [73609.775805]  ffff8802240f7a70
ffffffffc02ee9a0 ffff8802240f7a60 ffffffff810812d2
Feb  3 13:29:51 hostname kernel: [73609.775807]  ffff8804a37ae000
ffff8804a2d0a148 ffff8804a37af000 ffff8804a349a378
Feb  3 13:29:51 hostname kernel: [73609.775809] Call Trace:
Feb  3 13:29:51 hostname kernel: [73609.775813]  [<ffffffff813f7c63>]
dump_stack+0x63/0x90
Feb  3 13:29:51 hostname kernel: [73609.775816]  [<ffffffff810812d2>]
warn_slowpath_common+0x82/0xc0
Feb  3 13:29:51 hostname kernel: [73609.775818]  [<ffffffff8108136c>]
warn_slowpath_fmt+0x5c/0x80
Feb  3 13:29:51 hostname kernel: [73609.775831]  [<ffffffffc020ffec>]
skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
Feb  3 13:29:51 hostname kernel: [73609.775843]  [<ffffffffc0210185>]
skl_update_wm+0x185/0x610 [i915_bpo]
Feb  3 13:29:51 hostname kernel: [73609.775855]  [<ffffffffc0213f0e>]
intel_update_watermarks+0x1e/0x30 [i915_bpo]
Feb  3 13:29:51 hostname kernel: [73609.775873]  [<ffffffffc027f3f8>]
intel_atomic_commit+0x448/0x14a0 [i915_bpo]
Feb  3 13:29:51 hostname kernel: [73609.775887]  [<ffffffffc00d1bde>] ?
drm_atomic_check_only+0x18e/0x590 [drm]
Feb  3 13:29:51 hostname kernel: [73609.775898]  [<ffffffffc00d2017>]
drm_atomic_commit+0x37/0x60 [drm]
Feb  3 13:29:51 hostname kernel: [73609.775903]  [<ffffffffc0146dc6>]
drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
Feb  3 13:29:51 hostname kernel: [73609.775921]  [<ffffffffc02a2bf5>]
intel_dp_destroy_mst_connector+0x65/0x100 [i915_bpo]
Feb  3 13:29:51 hostname kernel: [73609.775925]  [<ffffffffc0142a0f>]
drm_dp_destroy_connector_work+0xaf/0x150 [drm_kms_helper]
Feb  3 13:29:51 hostname kernel: [73609.775928]  [<ffffffff8109a515>]
process_one_work+0x165/0x480
Feb  3 13:29:51 hostname kernel: [73609.775930]  [<ffffffff8109a87b>]
worker_thread+0x4b/0x4c0
Feb  3 13:29:51 hostname kernel: [73609.775932]  [<ffffffff8109a830>] ?
process_one_work+0x480/0x480
Feb  3 13:29:51 hostname kernel: [73609.775933]  [<ffffffff8109a830>] ?
process_one_work+0x480/0x480
Feb  3 13:29:51 hostname kernel: [73609.775935]  [<ffffffff810a0ba8>]
kthread+0xd8/0xf0
Feb  3 13:29:51 hostname kernel: [73609.775937]  [<ffffffff810a0ad0>] ?
kthread_create_on_node+0x1e0/0x1e0
Feb  3 13:29:51 hostname kernel: [73609.775939]  [<ffffffff8183898f>]
ret_from_fork+0x3f/0x70
Feb  3 13:29:51 hostname kernel: [73609.775941]  [<ffffffff810a0ad0>] ?
kthread_create_on_node+0x1e0/0x1e0
Feb  3 13:29:51 hostname kernel: [73609.775942] ---[ end trace e63971e069cb2256
]---

I will attach a more complete log with the above error.

I'm running Linux Mint MATE 18.1, currently with kernel version
4.4.0-62-generic. I have tried using the nVidia GPU instead (with the official
nvidia driver package, version 378.09), but the machine still freezes with
similar Intel-related kernel errors. I will attach a log for this too.

Is this the same bug? If so, can I do anything about it? Thanks.

-- 
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/20170203/1bc0f918/attachment-0001.html>