Additional info: reporter: libreport-2.2.2 WARNING: CPU: 0 PID: 649 at drivers/gpu/drm/i915/i915_gem.c:1403 i915_gem_fault+0x1fb/0x260 [i915]() unhandled error in i915_gem_fault: -22 Modules linked in: vfat fat usb_storage pppoe pppox ppp_generic slhc fuse bnep bluetooth ip6t_rpfilter 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 arc4 coretemp kvm snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device ath5k ath mac80211 cfg80211 thinkpad_acpi snd_pcm e1000e rfkill snd_page_alloc snd_timer snd iTCO_wdt microcode soundcore iTCO_vendor_support joydev serio_raw i2c_i801 of_i2c lpc_ich ptp pps_core wmi tpm_tis tpm tpm_bios acpi_cpufreq mperf binfmt_misc firewire_ohci firewire_core crc_itu_t i915 ata_generic pata_acpi yenta_socket i2c_algo_bit drm_kms_helper drm i2c_core video CPU: 0 PID: 649 Comm: X Not tainted 3.11.10-301.fc20.i686 #1 Hardware name: LENOVO 76591GJ/76591GJ, BIOS 7LETD0WW (2.30 ) 02/27/2012 00000000 00000000 f266bd18 c09795ee f266bd58 f266bd48 c0447b0e f7f5ec70 f266bd74 00000289 f7f5e970 0000057b f7f0a59b f7f0a59b 00000000 b74b0000 e93def00 f266bd60 c0447b63 00000009 f266bd58 f7f5ec70 f266bd74 f266bd9c Call Trace: [<c09795ee>] dump_stack+0x41/0x52 [<c0447b0e>] warn_slowpath_common+0x7e/0xa0 [<f7f0a59b>] ? i915_gem_fault+0x1fb/0x260 [i915] [<f7f0a59b>] ? i915_gem_fault+0x1fb/0x260 [i915] [<c0447b63>] warn_slowpath_fmt+0x33/0x40 [<f7f0a59b>] i915_gem_fault+0x1fb/0x260 [i915] [<c0522daa>] __do_fault+0x5a/0x500 [<c0976a73>] ? nohz_balance_exit_idle.part.47+0x10/0x2b [<c06832fa>] ? number.isra.2+0x33a/0x350 [<c0525e8b>] handle_pte_fault+0x8b/0x8d0 [<c06822c0>] ? timerqueue_add+0x50/0xb0 [<c0526785>] handle_mm_fault+0xb5/0x110 [<c0982bc1>] __do_page_fault+0x181/0x4d0 [<c0982f10>] ? __do_page_fault+0x4d0/0x4d0 [<c0982f1d>] do_page_fault+0xd/0x10 [<c097ff7b>] error_code+0x67/0x6c [<c054007b>] ? validate_slab+0xcb/0x170 [<c069c080>] ? strncpy_from_user+0x50/0xe0 [<c055a598>] getname_flags+0x98/0x140 [<c055a651>] getname+0x11/0x20 [<c0550246>] do_sys_open+0xe6/0x1f0 [<c0550e8c>] ? vfs_read+0xdc/0x150 [<c0550372>] SyS_open+0x22/0x30 [<c098690d>] sysenter_do_call+0x12/0x28
Created attachment 939924 [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.