Hide Forgot
Description of problem: Errors in log during boot Version-Release number of selected component (if applicable): kernel-4.8.6-300.fc25.x86_64 How reproducible: Steps to Reproduce: 1. 2 external monitors are connected with DP and DVI 2. 3. Actual results: [drm] Initialized i915 1.6.0 20160711 for 0000:00:02.0 on minor 0 [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training Expected results: No errors Additional info: Dell Latitude E7440 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device 05cb Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at f7800000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 filename: /lib/modules/4.8.6-300.fc25.x86_64/kernel/drivers/gpu/drm/i915/i915.ko.xz license: GPL and additional rights description: Intel Graphics author: Intel Corporation author: Tungsten Graphics, Inc. firmware: i915/bxt_dmc_ver1_07.bin firmware: i915/skl_dmc_ver1_26.bin firmware: i915/kbl_dmc_ver1_01.bin firmware: i915/kbl_guc_ver9_14.bin firmware: i915/bxt_guc_ver8_7.bin firmware: i915/skl_guc_ver6_1.bin depends: drm_kms_helper,drm,video,i2c-algo-bit intree: Y vermagic: 4.8.6-300.fc25.x86_64 SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4
I can confirm this on a Thinkpad T450 on Fedora 25 same kernel. I am getting the same two messages without any external display during boot: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training
Hello, On a lenovo T440 I got also this issue and worst. If I start the laptop with the DisplayPort connected, it crash. I attach the kernel.crash.txt to this issue. If I do some stuff like going into setting (just going to settings ! ) screen blink and screen is disabled. I need to shutdown / startup my screen (95% of success) to be able to use it. Also, I got 2 screen linked each other with DP, the second one is not detected every time... It make the setup very unstable... Also note that I had to disable wayland, else as soon as the screen get connected fedora crash...
Created attachment 1225910 [details] kernel.crash.txt : from journalctl -k -b -1 after a crash.
met exactly the same problem in 4.8.14-300.fc25.x86_64. using a thinkpad x1 carbon laptop.
I'm also have this problem on HP ProBook 430 G1.
me too, lenovo t440s. $ dmesg | grep ERROR [ 3.740470] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training [ 3.902072] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link trainin with multiple screens attached, they blink on and off. same behaviour under x11 and weyland. no crash though. also have weird slowness on wake from sleep under fc25 - not sure if that is related at all.
*** Bug 1400113 has been marked as a duplicate of this bug. ***
*** Bug 1397894 has been marked as a duplicate of this bug. ***
The same issue, lenove thinkpad T440s with fedora 25. I am getting the same two messages without any external display during boot: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. 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 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
On my end, the warning have disappeared when upgrading to 4.9.3. I'm able to enable wayland but now I have to test connecting my linked DP screens.
I confirm, no more issue with this. linked DP screens are working fine, wayland enable and running fine too.
(In reply to edward Grey from comment #11) > On my end, the warning have disappeared when upgrading to 4.9.3. > I'm able to enable wayland but now I have to test connecting my linked DP > screens. Me too, with 4.9.3, the warning disappeared.
My FC 25 crashes on occasion while watching videos or playing a flash game. While booting, I get this radeon 0000:01:00.0: failed VCE resume (-110). but it boots anyways, with no problem. only problem is system freezes on occasion. uname -a Linux lynnx.home 4.9.10-200.fc25.x86_64 #1 SMP Wed Feb 15 23:28:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ----- $ dmesg | egrep -i 'vce' [ 2.984419] [drm] Found VCE firmware/feedback version 50.0.1 / 17! [ 3.101463] radeon 0000:01:00.0: failed VCE resume (-110). ----- $ sudo lspci -vnk | grep -iA20 vga Flags: bus master, VGA palette snoop, 66MHz, medium devsel, latency 64, NUMA node 0 Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=64 00:14.5 0c03: 1002:4399 (prog-if 10 [OHCI]) Subsystem: 1002:4399 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18, NUMA node 0 Memory at feb06000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci-pci 00:16.0 0c03: 1002:4397 (prog-if 10 [OHCI]) Subsystem: 1002:4397 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 22, NUMA node 0 Memory at feb05000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci-pci 00:16.2 0c03: 1002:4396 (prog-if 20 [EHCI]) Subsystem: 1002:4396 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 23, NUMA node 0 Memory at feb04000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 -- 01:00.0 0300: 1002:6613 (prog-if 00 [VGA controller]) Subsystem: 1682:7240 Flags: bus master, fast devsel, latency 0, IRQ 61, NUMA node 0 Memory at d0000000 (64-bit, prefetchable) [size=256M] Memory at fea00000 (64-bit, non-prefetchable) [size=256K] I/O ports at e000 [size=256] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] #19 Kernel driver in use: radeon Kernel modules: radeon 01:00.1 0403: 1002:aab0 Subsystem: 1682:aab0 Flags: bus master, fast devsel, latency 0, IRQ 63, NUMA node 0 Memory at fea60000 (64-bit, non-prefetchable) [size=16K] ----- $ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family: 21 Model: 2 Model name: AMD FX(tm)-9590 Eight-Core Processor Stepping: 0 CPU MHz: 4716.085 BogoMIPS: 9432.17 Virtualization: AMD-V L1d cache: 16K L1i cache: 64K L2 cache: 2048K L3 cache: 8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold --- lspci|grep -i radeon 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
Same two messages on Fedora 25: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link training Kernel in use: uname -a Linux Fedora.localdomain 4.10.10-200.fc25.x86_64 #1 SMP Thu Apr 13 01:11:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Hardware: Dell laptop with CPU Core i5 Also random freezes of the system. Don't know if it's related to this bur or not.
https://bugzilla.redhat.com/show_bug.cgi?id=1444556 This too is a mistake that should be given serious consideration given the time at which you may experience!!
Sending /var/tmp/oops-2017-04-21-23:12:28-832-0.tar.gz https://retrace.fedoraproject.org Successfully created https://retrace.fedoraproject.org/faf/dumpdirs/new/oops-2017-04-21-23:12:28-832-0.tar.gz
https://bugzilla.redhat.com/show_bug.cgi?id=1444556 See the related link repeatedly please
No more such error on f27
failed VCE resume (-110). Fedora 26 nagging bug still present with 4.13.4 kernel
Fedora 26 nagging bug still present with 4.13.4 kernel failed VCE resume (-110).
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.