Additional info: reporter: libreport-2.2.2 WARNING: CPU: 0 PID: 15058 at drivers/gpu/drm/i915/intel_display.c:9457 intel_modeset_check_state+0x688/0x7d0 [i915]() encoder's hw state doesn't match sw tracking (expected 1, found 0) Modules linked in: binfmt_misc bnep bluetooth 6lowpan_iphc cfg80211 ip6t_rpfilter rfkill ip6t_REJECT xt_conntrack 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_analog snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep coretemp kvm_intel kvm snd_seq snd_seq_device iTCO_wdt snd_pcm snd_timer snd gpio_ich serio_raw iTCO_vendor_support ppdev parport_pc i2c_i801 lpc_ich microcode soundcore mfd_core parport mei_me acpi_cpufreq tpm_tis tpm wmi mei nfsd auth_rpcgss nfs_acl lockd sunrpc i915 i2c_algo_bit e1000e drm_kms_helper drm ptp pps_core ata_generic i2c_core pata_acpi video CPU: 0 PID: 15058 Comm: kworker/u8:26 Not tainted 3.14.4-200.fc20.x86_64 #1 Hardware name: LENOVO 7484CTO/LENOVO, BIOS 5CKT69AUS 01/10/2011 Workqueue: events_unbound async_run_entry_fn 0000000000000000 0000000064272675 ffff88005b711b28 ffffffff816ef1d2 ffff88005b711b70 ffff88005b711b60 ffffffff8108a1bd 0000000000000001 ffff88005b711bf0 ffff880036ad72e8 ffff880036a2e000 ffff880036ad7000 Call Trace: [<ffffffff816ef1d2>] dump_stack+0x45/0x56 [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a23c>] warn_slowpath_fmt+0x5c/0x80 [<ffffffffa0121558>] intel_modeset_check_state+0x688/0x7d0 [i915] [<ffffffffa012484e>] intel_modeset_setup_hw_state+0x98e/0xc40 [i915] [<ffffffffa00e62e3>] __i915_drm_thaw+0x163/0x220 [i915] [<ffffffffa00e63fc>] i915_resume+0x5c/0x90 [i915] [<ffffffffa00e6536>] i915_pm_resume+0x16/0x20 [i915] [<ffffffff81395744>] pci_pm_resume+0x64/0xb0 [<ffffffff813956e0>] ? pci_pm_thaw+0xa0/0xa0 [<ffffffff8146d1d9>] dpm_run_callback+0x49/0xa0 [<ffffffff8146d336>] device_resume+0xc6/0x1f0 [<ffffffff8146d47d>] async_resume+0x1d/0x50 [<ffffffff810b4469>] async_run_entry_fn+0x39/0x120 [<ffffffff810a6886>] process_one_work+0x176/0x430 [<ffffffff810a74db>] worker_thread+0x11b/0x3a0 [<ffffffff810a73c0>] ? rescuer_thread+0x370/0x370 [<ffffffff810ae211>] kthread+0xe1/0x100 [<ffffffff810ae130>] ? insert_kthread_work+0x40/0x40 [<ffffffff816ff4bc>] ret_from_fork+0x7c/0xb0 [<ffffffff810ae130>] ? insert_kthread_work+0x40/0x40
Created attachment 909777 [details] File: dmesg
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.