Description of problem: I docked the laptop (Lenovo Thinkpad T470s) to a docking station with 2 monitors connected - one via DVI and one via DisplayPort. From dmesg I can see the logs are flooded with a message "[drm:intel_ddi_prepare_link_retrain [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit". I basically have no way to re-dock the laptop without rebooting at this point. What happens is that when I dock the laptop the screen freezes and I can only move the mouse but cannot click anything, and the connected external monitors are not turned on. I believe this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1470960, except it doesn't happen 'rarely' but rather almost always. It only works properly on a fresh reboot. Additional info: reporter: libreport-2.9.5 WARNING: CPU: 2 PID: 2221 at drivers/gpu/drm/i915/intel_display.c:1055 intel_disable_pipe+0x13e/0x150 [i915] Modules linked in: fuse ccm thunderbolt xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT devlink ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables bnep binfmt_misc sunrpc arc4 intel_rapl iwlmvm snd_soc_skl iTCO_wdt x86_pkg_temp_thermal iTCO_vendor_support snd_soc_skl_ipc intel_powerclamp snd_hda_ext_core snd_soc_sst_dsp mei_wdt coretemp mac80211 snd_soc_sst_ipc snd_hda_codec_hdmi kvm_intel wmi_bmof snd_soc_acpi intel_wmi_thunderbolt kvm snd_soc_core snd_hda_codec_realtek iwlwifi snd_hda_codec_generic irqbypass snd_compress snd_pcm_dmaengine intel_cstate ac97_bus intel_uncore snd_hda_intel intel_rapl_perf snd_hda_codec cfg80211 snd_usb_audio snd_hda_core i2c_i801 uvcvideo snd_usbmidi_lib btusb snd_hwdep snd_rawmidi btrtl snd_seq videobuf2_vmalloc btbcm btintel videobuf2_memops joydev snd_seq_device shpchp videobuf2_v4l2 videobuf2_common snd_pcm bluetooth videodev thinkpad_acpi mei_me snd_timer mei media ecdh_generic intel_pch_thermal ucsi_acpi typec_ucsi typec snd wmi soundcore rfkill acpi_pad dm_crypt hid_logitech_hidpp hid_logitech_dj uas usb_storage i915 i2c_algo_bit crct10dif_pclmul drm_kms_helper crc32_pclmul crc32c_intel nvme ghash_clmulni_intel drm e1000e serio_raw nvme_core video CPU: 2 PID: 2221 Comm: Xorg Not tainted 4.17.5-200.fc28.x86_64 #1 Hardware name: LENOVO 20HGS22D0W/20HGS22D0W, BIOS N1WET46W (1.25 ) 03/16/2018 RIP: 0010:intel_disable_pipe+0x13e/0x150 [i915] RSP: 0018:ffff9837492e3af0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff8b46e51b0000 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff8b46fe516930 RBP: 0000000000072008 R08: 0000000000000028 R09: 00000000000009ea R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000002 R13: ffff8b441b0c8800 R14: 00000000fffffffe R15: ffff8b455aef9028 FS: 00007f17a9ed7ac0(0000) GS:ffff8b46fe500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb8767f8300 CR3: 0000000469308006 CR4: 00000000003606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: haswell_crtc_disable+0xf4/0x140 [i915] intel_atomic_commit_tail+0x1e8/0xcb0 [i915] intel_atomic_commit+0x2a9/0x2e0 [i915] ? drm_mode_getcrtc+0x160/0x160 [drm] drm_atomic_helper_set_config+0x80/0x90 [drm_kms_helper] __drm_mode_set_config_internal+0x67/0x110 [drm] drm_mode_setcrtc+0x3f5/0x5b0 [drm] ? drm_mode_getcrtc+0x160/0x160 [drm] drm_ioctl_kernel+0x5b/0xb0 [drm] drm_ioctl+0x1b3/0x370 [drm] ? drm_mode_getcrtc+0x160/0x160 [drm] ? selinux_file_ioctl+0x161/0x200 do_vfs_ioctl+0xa4/0x610 ksys_ioctl+0x60/0x90 ? ksys_write+0x9c/0xb0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x5b/0x160 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f17a7158e17 RSP: 002b:00007ffd98067518 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 00007f17a7158e17 RDX: 00007ffd98067550 RSI: 00000000c06864a2 RDI: 000000000000000d RBP: 00007ffd98067550 R08: 0000000000000000 R09: 0000000000000001 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c06864a2 R13: 000000000000000d R14: 00000000009c5d50 R15: 00000000009c58a0 Code: b9 01 00 00 00 5b 89 c2 5d 41 5c 41 5d e9 5b 98 78 e1 5b 31 f6 5d 41 5c 41 5d e9 4e de ff ff 48 c7 c7 35 f6 51 c0 e8 9c 30 c3 e0 <0f> 0b eb c5 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
Created attachment 1459434 [details] File: dmesg
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.