Created attachment 1521233 [details] dmesg 1. Please describe the problem: Dell 7490 hooked up to Dell TB16 dock and boot. Some time after boot, monitors flicker, the computer freezes some seconds. After a while everything seems OK again. Excerpt from dmesg [ 132.546752] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [ 132.815055] [drm:intel_encoders_pre_enable.isra.104 [i915]] *ERROR* failed to allocate vcpi [ 133.185527] ------------[ cut here ]------------ [ 133.185532] vblank wait timed out on crtc 1 [ 133.185669] WARNING: CPU: 0 PID: 1954 at drivers/gpu/drm/drm_vblank.c:1084 drm_wait_one_vblank+0x161/0x170 [drm] 2. What is the Version-Release number of the kernel: 4.19.15-300.fc29.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Also present in 4.19.13-300 and 4.19.14-300 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Happens on just about every boot. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.20.5-200.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Still present in 4.20.5-200.fc29.x86_64 No "cut here" and "vblank wait timed out on crtc 1" in dmesg though From dmesg: [ 104.248949] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [ 104.517559] [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate vcpi
Created attachment 1524893 [details] dmesg-4.20.5-200.fc29.x86_64
Does this also relate to https://bugzilla.redhat.com/show_bug.cgi?id=1392528
I'm seeing this error on my T480s when I try to use a Lenovo USB-C Travel Hub to connect my devices at home. I'm running Fedora 29 - Kernel 5.1.20-200.fc29.x86_64 Sample error from the system logs Aug 08 09:56:47 t480s kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training Aug 08 09:56:47 t480s kernel: [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate vcpi Aug 08 09:56:47 t480s kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Aug 08 09:56:47 t480s kernel: [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate vcpi Once this happens I can only run a single display - Joined displays don't work - Mirroring doesn't work I'm still running Xorg due to some other Wayland issues and I can see the following in my logs when I try and enable my normal joined display Aug 08 11:24:31 t480s /usr/libexec/gdm-x-session[2657]: (II) modeset(0): Allocate new frame buffer 3840x1200 stride Aug 08 11:24:31 t480s /usr/libexec/gdm-x-session[2657]: (EE) modeset(0): failed to set mode: Invalid argument Currently my only fix is to reboot the system. At work I've got a larger full USB-C Lenovo Dock and once this issue occurs I have secondary issues with that dock and multi-display
Intel xorg driver version - xorg-x11-drv-intel-2.99.917-42.20180618.fc29.x86_64 This has been happening for several updates, particularly since I moved to Fedora 29.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 5.2.9-100.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
I can confirm the issue still occurs with 5.2.18-100.fc29.x86_64 I'll be upgrading to Fedora 31 in the next couple of weeks and I'll re-test then
I have upgraded to fc30 and don't have this problem anymore
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.