Additional info: reporter: libreport-2.1.6 BUG: unable to handle kernel paging request at 0000000000001038 IP: [<ffffffffa01403d3>] i915_gem_unmap_dma_buf+0x33/0x70 [i915] PGD 0 Oops: 0000 [#1] SMP Modules linked in: nf_nat_ftp iptable_nat nf_nat_ipv4 xt_REDIRECT nf_nat iptable_mangle nf_conntrack_ftp xt_LOG xt_limit xt_multiport dummy bnep bluetooth xt_length nf_conntrack_ipv4 nf_defrag_ipv4 xt_hashlimit xt_conntrack nf_conntrack dm_crypt acpi_cpufreq mperf coretemp arc4 kvm_intel kvm snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm rtl8192cu rtlwifi rtl8192c_common snd_page_alloc snd_timer mac80211 snd soundcore iTCO_wdt dell_wmi iTCO_vendor_support sparse_keymap ppdev cfg80211 dell_laptop dcdbas rfkill microcode intel_ips i2c_i801 tg3 ptp lpc_ich pps_core mfd_core mei_me mei parport_pc parport binfmt_misc uinput hid_logitech_dj udl drm_usb i915 crc32c_intel i2c_algo_bit drm_kms_helper drm firewire_ohci sdhci_pci sdhci firewire_core mmc_core crc_itu_t i2c_core wmi video CPU: 0 PID: 598 Comm: X Not tainted 3.10.10-100.fc18.x86_64 #1 Hardware name: Dell Inc. Latitude E5410/00K2MH, BIOS A05 09/03/2010 task: ffff880190ea3560 ti: ffff880191686000 task.ti: ffff880191686000 RIP: 0010:[<ffffffffa01403d3>] [<ffffffffa01403d3>] i915_gem_unmap_dma_buf+0x33/0x70 [i915] RSP: 0018:ffff880191687c38 EFLAGS: 00010293 RAX: 0000000000001000 RBX: ffff880151876990 RCX: 0000000000000000 RDX: 0000000000000500 RSI: ffff880171513000 RDI: ffff880151844430 RBP: ffff880191687c48 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff81ce7a90 R11: 0000000000000003 R12: ffff880151876990 R13: 0000000000000000 R14: 0000000000000003 R15: ffff880191687d28 FS: 00007fa2eb139940(0000) GS:ffff88019bc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000001038 CR3: 0000000001c0c000 CR4: 00000000000007f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Stack: ffff880124c9d780 ffff880124c96a40 ffff880191687c78 ffffffff813ff1f9 ffff880191ae5b08 ffff880124c96a40 ffff88018dec2020 ffff88018dec2000 ffff880191687c98 ffffffffa0097b9b ffff880124ce3840 ffff88018dec2020 Call Trace: [<ffffffff813ff1f9>] dma_buf_unmap_attachment+0x49/0x80 [<ffffffffa0097b9b>] drm_prime_gem_destroy+0x2b/0x50 [drm] [<ffffffffa0045ba9>] udl_gem_free_object+0x39/0x70 [udl] [<ffffffffa0081aaa>] drm_gem_object_free+0x2a/0x30 [drm] [<ffffffffa0081df8>] drm_gem_object_release_handle+0xa8/0xd0 [drm] [<ffffffff812f75d6>] idr_for_each+0xb6/0x110 [<ffffffffa0081d50>] ? drm_gem_vm_close+0x80/0x80 [drm] [<ffffffffa00828e4>] drm_gem_release+0x24/0x40 [drm] [<ffffffffa0080e82>] drm_release+0x552/0x5f0 [drm] [<ffffffff811b33b6>] ? d_kill+0xb6/0x110 [<ffffffff8121aa17>] ? ext4_release_file+0x17/0xc0 [<ffffffff8119f31c>] __fput+0xec/0x240 [<ffffffff8119f47e>] ____fput+0xe/0x10 [<ffffffff8107f535>] task_work_run+0xc5/0xe0 [<ffffffff81063106>] do_exit+0x2b6/0xa30 [<ffffffff8119f47e>] ? ____fput+0xe/0x10 [<ffffffff8107f51c>] ? task_work_run+0xac/0xe0 [<ffffffff8106390f>] do_group_exit+0x3f/0xa0 [<ffffffff81063987>] SyS_exit_group+0x17/0x20 [<ffffffff81664d19>] system_call_fastpath+0x16/0x1b Code: 48 89 e5 53 48 89 f3 48 83 ec 08 48 8b 7f 08 8b 56 08 48 8b 36 48 85 ff 74 3e 48 8b 87 08 02 00 00 48 85 c0 74 32 83 f9 02 77 36 <48> 8b 40 38 48 85 c0 74 05 45 31 c0 ff d0 48 89 df e8 57 6d 1c RIP [<ffffffffa01403d3>] i915_gem_unmap_dma_buf+0x33/0x70 [i915] RSP <ffff880191687c38> CR2: 0000000000001038
Created attachment 796597 [details] File: dmesg
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
Reopening as this is still happening in Fedora 20. Bug 1005006 and bug 951240 seem to be related. Attaching full dmesg output, though it looks very similar to the earlier attachment. FWIW, I'm fairly certain it is the use of the DisplayLink (to have 3 monitor output) that is causing the issue.
Created attachment 871929 [details] dmesg output
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.