Description of problem: only one application was running -firefox unexpectedly kernell dumped Additional info: reporter: libreport-2.2.2 kernel BUG at include/drm/drm_mm.h:105! invalid opcode: 0000 [#1] SMP Modules linked in: fuse bnep bluetooth 6lowpan_iphc ip6t_rpfilter ip6t_REJECT cfg80211 rfkill 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 coretemp gpio_ich kvm_intel kvm iTCO_wdt iTCO_vendor_support microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore lpc_ich ppdev i2c_i801 serio_raw parport_pc parport acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc i915 video ata_generic i2c_algo_bit pata_acpi drm_kms_helper drm r8169 mii i2c_core CPU: 1 PID: 523 Comm: X Not tainted 3.14.5-200.fc20.i686 #1 Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080015 02/03/2010 task: f0dc19f0 ti: f1536000 task.ti: f1536000 EIP: 0060:[<f7e0d8bb>] EFLAGS: 00013246 CPU: 1 EIP is at drm_mm_insert_node_in_range_generic+0x25b/0x270 [drm] EAX: eb5b5e48 EBX: eb5b5e40 ECX: 0df3a000 EDX: 00000000 ESI: 0df46000 EDI: f6fe168c EBP: f1537dcc ESP: f1537d9c DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 80050033 CR2: f98bf420 CR3: 3150e000 CR4: 000407d0 Stack: f1537db8 de8f4240 00000000 00000000 ffffffff 00100000 0df3a000 0df46000 59356a46 f6d9ff00 00100000 f6fe168c f1537e28 f7f2a979 00100000 00000000 00000000 10000000 00000000 f6fe0000 f1537e00 00100000 00100000 f6fe0000 Call Trace: [<f7f2a979>] i915_gem_object_pin+0x3a9/0x690 [i915] [<f7f2cb30>] i915_gem_fault+0x100/0x260 [i915] [<f7f2c830>] ? i915_gem_pwrite_ioctl+0x890/0x890 [i915] [<c053c28b>] __do_fault+0x6b/0x500 [<c053f40f>] handle_mm_fault+0x14f/0xa70 [<c0544abc>] ? mmap_region+0x15c/0x4e0 [<c09f3edc>] __do_page_fault+0x19c/0x510 [<c057e37a>] ? do_vfs_ioctl+0x2ea/0x4b0 [<c06523dc>] ? selinux_file_ioctl+0x4c/0xf0 [<c09f4250>] ? __do_page_fault+0x510/0x510 [<c09f426a>] do_page_fault+0x1a/0x20 [<c09f136b>] error_code+0x67/0x6c Code: 8b 45 14 89 45 ec e9 28 ff ff ff 90 8d 74 26 00 8b 0f 89 d8 89 fa e8 95 48 8b c8 8b 45 d4 80 48 10 01 eb 8b b8 e4 ff ff ff eb 86 <0f> 0b e8 be f7 ff ff 0f 0b 0f 0b 0f 0b 0f 0b e8 01 ef 63 c8 90
Created attachment 903278 [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.