Created attachment 860435 [details] bootup with monitor already attached to display port connector Description of problem: When booting the system with a display connected through the display port there is no picture Version-Release number of selected component (if applicable): dmesg-3.12.9-301.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. Boot system with monitor connected through display port 2. No picture 3. Actual results: Black screen and this message in dmesg: [ 1.607415] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [ 1.670888] [drm] HPD interrupt storm detected on connector DP-2: switching from hotplug detection to polling Expected results: Working monitor through displayport Additional info: System is Intel haswell i4771 with HD4600. When the monitor is attached after system is booted up I see: [ 13.756488] ------------[ cut here ]------------ [ 13.756512] WARNING: CPU: 3 PID: 572 at drivers/gpu/drm/i915/intel_display.c:6015 hsw_disable_lcpll+0x514/0x640 [i915]() [ 13.756513] Power well on [ 13.756514] Modules linked in: ip6t_rpfilter ip6t_REJECT xt_conntrack bnep bluetooth cfg80211 rfkill ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_ security iptable_raw snd_hda_codec_realtek snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support vfat fat x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel snd_hda_intel snd_hda_codec ghash_clmulni_intel snd_hwdep snd_seq snd_seq_device snd_pcm microcode serio_raw i2c_i801 lpc_ich mfd_core e1000e shpchp ptp pps_core snd_page_alloc snd_timer mei_me snd mei soundcore nfs d auth_rpcgss [ 13.756534] nfs_acl lockd sunrpc hid_logitech_dj i915 i2c_algo_bit drm_kms_helper drm i2c_core video [ 13.756539] CPU: 3 PID: 572 Comm: kworker/3:2 Not tainted 3.12.9-301.fc20.x86_64 #1 [ 13.756540] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z87E-ITX, BIOS P1.90 07/05/2013 [ 13.756548] Workqueue: events hsw_enable_pc8_work [i915] [ 13.756549] 0000000000000009 ffff88003f85bd28 ffffffff81667af7 ffff88003f85bd70 [ 13.756551] ffff88003f85bd60 ffffffff8106918d ffff8804054c4000 ffff8804067d5448 [ 13.756553] 0000000000000001 0000000000000001 ffff8804067d5450 ffff88003f85bdc0 [ 13.756555] Call Trace: [ 13.756560] [<ffffffff81667af7>] dump_stack+0x45/0x56 [ 13.756563] [<ffffffff8106918d>] warn_slowpath_common+0x7d/0xa0 [ 13.756565] [<ffffffff810691fc>] warn_slowpath_fmt+0x4c/0x50 [ 13.756574] [<ffffffffa00be264>] hsw_disable_lcpll+0x514/0x640 [i915] [ 13.756582] [<ffffffffa00be941>] hsw_enable_pc8_work+0x81/0xc0 [i915] [ 13.756584] [<ffffffff810835a6>] process_one_work+0x176/0x430 [ 13.756586] [<ffffffff810841db>] worker_thread+0x11b/0x3a0 [ 13.756587] [<ffffffff810840c0>] ? rescuer_thread+0x350/0x350 [ 13.756590] [<ffffffff8108b080>] kthread+0xc0/0xd0 [ 13.756592] [<ffffffff8108afc0>] ? insert_kthread_work+0x40/0x40 [ 13.756595] [<ffffffff816769fc>] ret_from_fork+0x7c/0xb0 [ 13.756596] [<ffffffff8108afc0>] ? insert_kthread_work+0x40/0x40 [ 13.756597] ---[ end trace da66e5e4a50e77f0 ]---
Created attachment 860436 [details] dmesg for monitor attached after bootup
I've tried the patch from: https://bugs.freedesktop.org/show_bug.cgi?id=73694 this does not help, the issue stays the same. No display with the monitor connected through display port. The monitor only has a display port connection.
Created attachment 860438 [details] dmesg output, boot with monitor attached to display port, drm.debug=0xe dmesg output for bootup with drm.debug = 0xe. Kernel has patch from https://bugs.freedesktop.org/show_bug.cgi?id=73694 included. Does not help.
How can we move this forward? System is not usable without a working display. I have tried with a recent 3.14 snapshot (3.14.0-0.rc2.git1.1). Still no luck. dmesg shows: [ 22.609789] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.619504] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.629136] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.638759] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.648498] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.657944] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.667995] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.668646] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [ 22.683388] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.693016] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.720376] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.729852] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.739620] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.749352] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.759178] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.768716] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.778223] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.778764] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [ 22.790958] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.800595] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.810796] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 22.820495] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 23.174495] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 23.816416] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
ping. I'll repeat my previous question. What can I do to move this forward?
Since my last kernel upgrade I started seeing a similar sequence of messages when switching on my DisplayPort connected ASUS 27" monitor using the power-on button on the monitor. Eventually (after about 10 sec), the monitor starts to work, despite the 'failed to train' DP' error so this may be a different symptom with similar cause. Example of a log spam sequence. Note the two back-to-back sequences ending with 'fail to train DP' all within the same second. Apr 26 09:36:04 xx kernel: [431359.863532] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.870682] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.877555] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.884470] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.891387] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.898328] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.905304] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.905496] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting Apr 26 09:36:04 xx kernel: [431359.961752] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.968715] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.975629] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.982569] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.989545] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431359.996473] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431360.003428] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Apr 26 09:36:04 xx kernel: [431360.003621] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting
Hello, I have the same issue with my Dell LATITUDE E7240 and a docking station with a monitor connected through DisplayPort. Thus I can't use my Dell U2410 monitor with my labtop. I think the issue is also discussed here: https://bugs.freedesktop.org/show_bug.cgi?id=73694 Regards, Jerome
Hello, Any activity about this issue ? Best regards, Jerome
I face the same issue using a 2K acer monitor with a lenovo T530.
> What can I do to move this forward? The quickest way to get bugs like this fixed is to verify that the bug is still present in a recent kernel (preferably the latest mainline git or intel-drm-nightly) and if it is then report it upstream: https://01.org/linuxgraphics/documentation/how-report-bugs Intel's developers are very responsive to bug reports.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.