Description of problem: During Boot after the "fedora"-icon was completely loaded. Additional info: reporter: libreport-2.1.10 WARNING: CPU: 1 PID: 1148 at drivers/gpu/drm/i915/i915_irq.c:1001 i965_irq_handler+0x572/0x640 [i915]() Received HPD interrupt although disabled Modules linked in: ip6t_REJECT fuse 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 bnep dm_crypt iTCO_wdt arc4 iTCO_vendor_support iwldvm mac80211 iwlwifi snd_hda_codec_conexant cfg80211 coretemp kvm_intel kvm snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device microcode uvcvideo videobuf2_vmalloc snd_pcm videobuf2_memops serio_raw videobuf2_core videodev media qcserial lpc_ich usb_wwan i2c_i801 mfd_core btusb bluetooth shpchp snd_page_alloc snd_timer e1000e mei_me ptp mei pps_core wmi thinkpad_acpi snd soundcore rfkill tpm_tis tpm tpm_bios acpi_cpufreq i915 i2c_algo_bit drm_kms_helper drm i2c_core video CPU: 1 PID: 1148 Comm: iptables Not tainted 3.12.6-300.fc20.x86_64 #1 Hardware name: LENOVO 7458WCC/7458WCC, BIOS 6DET71WW (3.21 ) 12/13/2011 0000000000000009 ffff88023bc83d88 ffffffff816630c1 ffff88023bc83dd0 ffff88023bc83dc0 ffffffff810691dd 0000000000020000 0000000000000004 ffffffffa00f7100 ffff88022dac4030 ffff88022dac4000 ffff88023bc83e20 Call Trace: <IRQ> [<ffffffff816630c1>] dump_stack+0x45/0x56 [<ffffffff810691dd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8106924c>] warn_slowpath_fmt+0x4c/0x50 [<ffffffffa008ee92>] i965_irq_handler+0x572/0x640 [i915] [<ffffffff810ba5ce>] handle_irq_event_percpu+0x3e/0x1e0 [<ffffffff810ba7ad>] handle_irq_event+0x3d/0x60 [<ffffffff810bd555>] handle_edge_irq+0x85/0x150 [<ffffffff810145c2>] handle_irq+0xc2/0x150 [<ffffffff8106e92d>] ? irq_enter+0x4d/0x90 [<ffffffff816742cd>] do_IRQ+0x4d/0xc0 [<ffffffff81669fad>] common_interrupt+0x6d/0x6d <EOI> [<ffffffff81551500>] ? sk_common_release+0x10/0xf0 [<ffffffff815c7a3e>] raw_close+0x1e/0x30 [<ffffffff815d4757>] inet_release+0x77/0x80 [<ffffffff8154cdaf>] sock_release+0x1f/0x80 [<ffffffff8154ce22>] sock_close+0x12/0x20 [<ffffffff811aff81>] __fput+0xe1/0x230 [<ffffffff811b011e>] ____fput+0xe/0x10 [<ffffffff81087d07>] task_work_run+0xa7/0xe0 [<ffffffff81012a21>] do_notify_resume+0x61/0xa0 [<ffffffff816723e2>] int_signal+0x12/0x17
Created attachment 847786 [details] File: dmesg
*** Bug 1062496 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.