Description of problem: It appears on system start up Additional info: reporter: libreport-2.1.10 WARNING: CPU: 2 PID: 669 at drivers/gpu/drm/i915/intel_display.c:8810 check_crtc_state+0x628/0xc30 [i915]() pipe state doesn't match! Modules linked in: nf_defrag_ipv4 nf_nat_ipv4(+) nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep snd_hda_codec_realtek snd_hda_intel uvcvideo coretemp snd_hda_codec videobuf2_vmalloc arc4 iwldvm videobuf2_memops kvm snd_hwdep mac80211 videobuf2_core snd_seq videodev snd_seq_device snd_pcm i2c_i801 iTCO_wdt iwlwifi r8169 snd_page_alloc samsung_laptop btusb media mii iTCO_vendor_support snd_timer cfg80211 bluetooth snd microcode lpc_ich serio_raw rfkill mfd_core soundcore acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc i915 i2c_algo_bit drm_kms_helper drm i2c_core video CPU: 2 PID: 669 Comm: X Not tainted 3.12.5-302.fc20.i686+PAE #1 Hardware name: SAMSUNG ELECTRONICS CO., LTD. NC210/NC110 /NC210/NC110 , BIOS 01VG.M013.20110704.RHU 07/04/2011 00000000 00000000 f2549a2c c09ac511 f2549a6c f2549a5c c04554de f8146090 f2549a88 0000029d f813d11c 0000226a f80f2088 f80f2088 f5153000 00000003 f515364c f2549a74 c0455533 00000009 f2549a6c f8146090 f2549a88 f2549ce4 Call Trace: [<c09ac511>] dump_stack+0x41/0x52 [<c04554de>] warn_slowpath_common+0x7e/0xa0 [<f80f2088>] ? check_crtc_state+0x628/0xc30 [i915] [<f80f2088>] ? check_crtc_state+0x628/0xc30 [i915] [<c0455533>] warn_slowpath_fmt+0x33/0x40 [<f80f2088>] check_crtc_state+0x628/0xc30 [i915] [<f80fd663>] intel_modeset_check_state+0x2a3/0x770 [i915] [<f80fdbc0>] intel_set_mode+0x30/0x40 [i915] [<f80fe449>] intel_crtc_set_config+0x789/0x970 [i915] [<f7f5461b>] drm_mode_set_config_internal+0x4b/0xc0 [drm] [<f7f56d4f>] drm_mode_setcrtc+0xdf/0x620 [drm] [<f7f56c70>] ? drm_mode_setplane+0x400/0x400 [drm] [<f7f49822>] drm_ioctl+0x472/0x500 [drm] [<f7f56c70>] ? drm_mode_setplane+0x400/0x400 [drm] [<c06864a2>] ? blk_throtl_drain+0x62/0xd0 [<c040f8b8>] ? __switch_to+0x2b8/0x340 [<f7f493b0>] ? drm_copy_field+0x70/0x70 [drm] [<c0572566>] do_vfs_ioctl+0x2e6/0x4d0 [<c063b312>] ? inode_has_perm.isra.30+0x32/0x40 [<c063b42f>] ? file_has_perm+0x7f/0x90 [<c063bdec>] ? selinux_file_ioctl+0x4c/0xf0 [<c05727b0>] SyS_ioctl+0x60/0x80 [<c06864a2>] ? blk_throtl_drain+0x62/0xd0 [<c06864a2>] ? blk_throtl_drain+0x62/0xd0 [<c09b964d>] sysenter_do_call+0x12/0x28 [<c06864a2>] ? blk_throtl_drain+0x62/0xd0 [<c06864a2>] ? blk_throtl_drain+0x62/0xd0 Potential duplicate: bug 1044724
Created attachment 840636 [details] File: dmesg
*** Bug 1048492 has been marked as a duplicate of this bug. ***
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.