Additional info: reporter: libreport-2.1.9 WARNING: CPU: 0 PID: 781 at drivers/gpu/drm/i915/intel_display.c:8255 intel_modeset_check_state+0x653/0x7a0 [i915]() encoder's hw state doesn't match sw tracking (expected 1, found 0) Modules linked in: fuse ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_CHECKSUM iptable_mangle tun ebtable_nat ebtables bridge stp llc rfcomm bnep ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack nf_conntrack ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_idt iTCO_wdt arc4 iTCO_vendor_support brcmsmac cordic brcmutil b43 mac80211 cfg80211 ssb hp_wmi sparse_keymap ppdev x86_pkg_temp_thermal coretemp kvm_intel kvm crc32_pclmul crc32c_intel ghash_clmulni_intel btusb bluetooth microcode uvcvideo rfkill videobuf2_vmalloc videobuf2_memops videobuf2_core snd_hda_intel snd_hda_codec videodev serio_raw lpc_ich snd_hwdep mfd_core media snd_seq snd_seq_device bcma sdhci_pci snd_pcm sdhci mmc_core e1000e snd_page_alloc snd_timer shpchp snd mei_me ptp soundcore mei pps_core wmi parport_pc parport hp_accel lis3lv02d input_polldev mperf uinput binfmt_misc i915 i2c_algo_bit drm_kms_helper firewire_ohci drm firewire_core crc_itu_t i2c_core video CPU: 0 PID: 781 Comm: Xorg Not tainted 3.11.9-200.fc19.x86_64 #1 Hardware name: Hewlett-Packard HP ProBook 6560b/1619, BIOS 68SCE Ver. F.29 01/04/2013 0000000000000009 ffff8802272a5c48 ffffffff8164764b ffff8802272a5c90 ffff8802272a5c80 ffffffff8106715d 0000000000000001 ffff8802272a5d0c ffff880231044460 ffff8802310f2800 ffff880231044000 ffff8802272a5ce0 Call Trace: [<ffffffff8164764b>] dump_stack+0x45/0x56 [<ffffffff8106715d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff810671cc>] warn_slowpath_fmt+0x4c/0x50 [<ffffffffa00df303>] intel_modeset_check_state+0x653/0x7a0 [i915] [<ffffffffa00df48e>] intel_connector_dpms+0x3e/0x50 [i915] [<ffffffffa0047f68>] drm_mode_obj_set_property_ioctl+0x308/0x320 [drm] [<ffffffffa0047fb0>] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] [<ffffffffa0037122>] drm_ioctl+0x512/0x640 [drm] [<ffffffff8114464a>] ? __free_pages+0x4a/0x80 [<ffffffff811c593e>] ? mntput_no_expire+0x3e/0x120 [<ffffffff811b9fcd>] do_vfs_ioctl+0x2dd/0x4b0 [<ffffffff811a9dee>] ? ____fput+0xe/0x10 [<ffffffff81085334>] ? task_work_run+0xa4/0xe0 [<ffffffff811ba221>] SyS_ioctl+0x81/0xa0 [<ffffffff81656859>] system_call_fastpath+0x16/0x1b
Created attachment 833468 [details] File: dmesg
*** Bug 1047107 has been marked as a duplicate of this bug. ***
*** Bug 1122170 has been marked as a duplicate of this bug. ***
*** Bug 1130403 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.