Bug 1150103 - [abrt] BUG: unable to handle kernel paging request at ffffebe000001000
Summary: [abrt] BUG: unable to handle kernel paging request at ffffebe000001000
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:4d3243e5f11b50815a5bbd458cd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-07 12:43 UTC by Dan Lascu
Modified: 2015-06-29 22:49 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:49:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (66.52 KB, text/plain)
2014-10-07 12:44 UTC, Dan Lascu
no flags Details

Description Dan Lascu 2014-10-07 12:43:57 UTC
Additional info:
reporter:       libreport-2.2.3
BUG: unable to handle kernel paging request at ffffebe000001000
IP: [<ffffffff811d5676>] kfree+0x56/0x140
PGD 0 
Oops: 0000 [#1] SMP 
Modules linked in: vfat fat xfs libcrc32c btrfs xor raid6_pq uas usb_storage fuse ipt_MASQUERADE xt_CHECKSUM ip6t_rpfilter ip6t_REJECT xt_conntrack cfg80211 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 mmc_block ppdev iTCO_wdt dell_wmi iTCO_vendor_support sparse_keymap dell_laptop dcdbas coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic ghash_clmulni_intel microcode serio_raw i2c_i801 intel_ips btusb snd_hda_intel snd_hda_controller bluetooth
snd_hda_codec joydev rfkill snd_hwdep cdc_ether snd_seq usbnet snd_seq_device mii cdc_wdm cdc_acm snd_pcm sdhci_pci sdhci snd_timer mmc_core lpc_ich snd mfd_core soundcore shpchp wmi parport_pc parport tpm_tis tpm dell_smo8800 acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc i915 i2c_algo_bit drm_kms_helper drm firewire_ohci e1000e ptp i2c_core firewire_core yenta_socket crc_itu_t pps_core video
CPU: 1 PID: 867 Comm: X Not tainted 3.16.3-200.fc20.x86_64 #1
Hardware name: Dell Inc. Latitude E6510/02K3Y4, BIOS A16 12/05/2013
task: ffff8800d2aab160 ti: ffff8800d66a0000 task.ti: ffff8800d66a0000
RIP: 0010:[<ffffffff811d5676>]  [<ffffffff811d5676>] kfree+0x56/0x140
RSP: 0018:ffff8800d66a3cf0  EFLAGS: 00010286
RAX: ffffebe000001000 RBX: 0000000000040000 RCX: 0000000000000000
RDX: ffffea0000000000 RSI: ffff88021376c8d8 RDI: 0000000000040000
RBP: ffff8800d66a3d08 R08: ffff880212a90800 R09: 000000010040001a
R10: ffffea00084aa400 R11: ffffffffa00ca764 R12: 0000000000001000
R13: ffffffffa01429ee R14: ffff880036a50000 R15: ffff88021376c918
FS:  00007f71f0d499c0(0000) GS:ffff88021fc40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffebe000001000 CR3: 00000000cf92f000 CR4: 00000000000007e0
Stack:
ffff88021376c8c0 0000000000001000 ffff88021376c980 ffff8800d66a3d50
ffffffffa01429ee ffff880036a50000 0000000000000000 ffff88021376c8c0
ffff8800d5700060 00000000000000fc ffff8800d5700000 ffff8800d6e15a38
Call Trace:
[<ffffffffa01429ee>] i915_gem_free_object+0x1be/0x390 [i915]
[<ffffffffa00b1fd7>] drm_gem_object_free+0x27/0x30 [drm]
[<ffffffffa00b263a>] drm_gem_object_handle_unreference_unlocked+0xda/0x110 [drm]
[<ffffffffa00b2712>] drm_gem_handle_delete+0xa2/0xf0 [drm]
[<ffffffffa00b2cd5>] drm_gem_close_ioctl+0x25/0x30 [drm]
[<ffffffffa00b0a6c>] drm_ioctl+0x1ec/0x660 [drm]
[<ffffffff81059d6c>] ? __do_page_fault+0x21c/0x540
[<ffffffff8120a23c>] ? __dentry_kill+0x14c/0x1c0
[<ffffffff812068a0>] do_vfs_ioctl+0x2e0/0x4a0
[<ffffffff811f550e>] ? ____fput+0xe/0x10
[<ffffffff81206ae1>] SyS_ioctl+0x81/0xa0
[<ffffffff81125ed6>] ? __audit_syscall_exit+0x1f6/0x2a0
[<ffffffff8170e6e9>] system_call_fastpath+0x16/0x1b
Code: 00 00 00 80 ff 77 00 00 48 01 d8 48 0f 42 15 b2 29 a4 00 48 01 d0 48 ba 00 00 00 00 00 ea ff ff 48 c1 e8 0c 48 c1 e0 06 48 01 d0 <48> 8b 10 80 e6 80 0f 85 c0 00 00 00 49 89 c2 49 8b 02 a8 80 0f 
RIP  [<ffffffff811d5676>] kfree+0x56/0x140
RSP <ffff8800d66a3cf0>

Comment 1 Dan Lascu 2014-10-07 12:44:02 UTC
Created attachment 944578 [details]
File: dmesg

Comment 2 Fedora End Of Life 2015-05-29 13:02:13 UTC
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.

Comment 3 Fedora End Of Life 2015-06-29 22:49:03 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.