Hide Forgot
Created attachment 1110602 [details] dmesg Description of problem: When I try to activate (or just connect it) monitor (dell u2414h) through DP from Intel nuc 5i5 my system freezes for some seconds, in dmesg crash traces appears: WARNING: CPU: 0 PID: 1280 at drivers/gpu/drm/i915/intel_display.c:12302 check_crtc_state+0x970/0xf80 [i915]() crtc's computed enabled state doesn't match tracked enabled state (expected 0, found 1) Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_filter ebtable_broute bridge stp llc ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_n at_ipv6 ip6table_mangle ip6table_raw ip6table_security ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw ipt able_security intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi arc4 snd_hda_intel uvcvideo snd_hda_codec iwlmvm snd_soc_rt5640 snd_soc_rl6231 crct10dif_pclmul videobuf2_vmalloc videobuf2_core iTCO_wdt iTCO_vendor_support snd_hda_core btusb snd_soc_core snd_compress videobuf2_memops v4l2_common video dev snd_pcm_dmaengine ac97_bus snd_usb_audio snd_seq mac80211 crc32_pclmul media crc32c_intel snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device btrtl iwlwifi joydev cfg80211 btbcm snd_pcm btintel ir_lirc_codec ir_mce_kbd_decoder i r_xmp_decoder lirc_dev ir_sanyo_decoder ir_sharp_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_nec_decoder ir_rc5_decoder bluetooth rc_rc6_mce rfkill snd_timer nuvoton_cir i2c_de signware_platform snd soundcore rc_core i2c_designware_core i2c_i801 tpm_tis acpi_als tpm kfifo_buf lpc_ich mei_me mei snd_soc_sst_acpi dw_dmac shpchp industrialio dw_dmac_core acpi_pad hid _logitech_hidpp hid_logitech_dj i915 i2c_algo_bit drm_kms_helper e1000e drm serio_raw ptp pps_core sdhci_acpi sdhci mmc_core video i2c_hid CPU: 0 PID: 1280 Comm: Xorg Tainted: G W 4.2.8-300.fc23.x86_64 #1 Hardware name: /NUC5i5RYB, BIOS RYBDWi35.86A.0352.2015.1130.1011 11/30/2015 0000000000000000 00000000a40aee1a ffff880089fe7788 ffffffff817738ca 0000000000000000 ffff880089fe77e0 ffff880089fe77c8 ffffffff8109e4c6 ffff880089fe7870 ffff880451bc7b50 ffff880451bf9000 ffff880451bc7800 Call Trace: [<ffffffff817738ca>] dump_stack+0x45/0x57 [<ffffffff8109e4c6>] warn_slowpath_common+0x86/0xc0 [<ffffffff8109e555>] warn_slowpath_fmt+0x55/0x70 [<ffffffffa01cb7b2>] ? intel_ddi_get_config+0xe2/0x1f0 [i915] [<ffffffffa01a04c0>] check_crtc_state+0x970/0xf80 [i915] [<ffffffffa00721ba>] ? drm_calc_vbltimestamp_from_scanoutpos+0x17a/0x330 [drm] [<ffffffffa01b3756>] intel_modeset_check_state+0x216/0xb50 [i915] [<ffffffffa01adc9c>] ? __intel_set_mode+0x92c/0xb60 [i915] [<ffffffffa01b4d97>] intel_crtc_set_config+0x4c7/0x580 [i915] [<ffffffffa007c306>] drm_mode_set_config_internal+0x66/0x100 [drm] [<ffffffffa0080819>] drm_mode_setcrtc+0x3e9/0x500 [drm] [<ffffffffa0071365>] drm_ioctl+0x125/0x610 [drm] [<ffffffff810aa2e1>] ? __set_task_blocked+0x41/0xa0 [<ffffffffa0080430>] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [<ffffffff81231475>] do_vfs_ioctl+0x295/0x470 [<ffffffff810aa2e1>] ? __set_task_blocked+0x41/0xa0 [<ffffffff812316c9>] SyS_ioctl+0x79/0x90 [<ffffffff810acf2e>] ? SyS_rt_sigprocmask+0x8e/0xc0 [<ffffffff8177a2ae>] entry_SYSCALL_64_fastpath+0x12/0x71 Version-Release number of selected component (if applicable): kernel-4.2.8-300.fc23.x86_64 xorg-x11-drv-intel-2.99.917-16.20150729.fc23.x86_64 How reproducible: always Steps to Reproduce: 1. connect monitor through DP 2. after freeze try to activate it through xrandr --output DP1-1 --auto 3. Actual results: plasma crashes, abrt unreportable oops Expected results: see output on monitor Additional info: booting with the monitor connected makes it "working", but only with 1024x768 resolution, using it through the HDMI works absolutely fine. /var/log/messages is empty abrt duphash:ba62864197a0ef090ae748c4df9616c0173b7785
It seems to be happening when the monitor has Daisy Chaining enabled.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.