Bug 1069733

Summary: [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000293
Product: [Fedora] Fedora Reporter: Emmett Culley <lst_manage>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gansalmon, itamar, jonathan, kernel-maint, lst_manage, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b938c26b9f24443f3d4093b6ef3b58537a8f56ba
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-17 18:43:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description Emmett Culley 2014-02-25 15:09:54 UTC 
Additional info:
reporter:       libreport-2.1.12
BUG: unable to handle kernel NULL pointer dereference at 0000000000000293
IP: [<0000000000000293>] 0x293
PGD 1c458c067 PUD 18aef2067 PMD 0 
Oops: 0010 [#1] SMP 
Modules linked in: bnep bluetooth rfkill ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_CHECKSUM iptable_mangle tun ip6table_filter ip6_tables ebtable_nat ebtables rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache bridge stp llc snd_hda_codec_realtek kvm_amd kvm snd_usb_audio snd_hda_intel snd_hda_codec snd_usbmidi_lib snd_hwdep snd_rawmidi nouveau snd_seq snd_seq_device snd_pcm mxm_wmi uvcvideo wmi tg3 snd_page_alloc snd_timer video i2c_algo_bit ttm drm_kms_helper drm videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd nv_tco ptp media microcode pps_core usblp i2c_nforce2 shpchp edac_core i2c_core edac_mce_amd soundcore serio_raw k10temp acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc raid1 hid_logitech_dj usb_storage ata_generic firewire_ohci pata_acpi firewire_core sata_sil24 crc_itu_t sata_nv pata_amd
CPU: 4 PID: 23968 Comm: plugin-containe Not tainted 3.13.3-201.fc20.x86_64 #1
Hardware name: ASUSTek Computer INC. KFN5-D SLI/KFN5-D SLI, BIOS 0404    07/02/2008
task: ffff8800be6c2b20 ti: ffff88009d3f4000 task.ti: ffff88009d3f4000
RIP: 0010:[<0000000000000293>]  [<0000000000000293>] 0x293
RSP: 0018:ffff88009d3f5f90  EFLAGS: 00010286
RAX: ffffffffffffffea RBX: 00007f31df1ba040 RCX: 00007f31d2aef9c0
RDX: 0000000000000000 RSI: 00007f31d2aef9c0 RDI: ffff88009d3f5f68
RBP: ffffffff81695b29 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000010 R11: 0000000000000293 R12: 00007f31d2aefa90
R13: 0000000000000000 R14: 0000000000000000 R15: 00007f31df1ba320
FS:  00007f31d2af0700(0000) GS:ffff88022fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000293 CR3: 00000001ba75c000 CR4: 00000000000007e0
Stack:
 00007f31defe6000 0000000000000000 0000000000000000 0000000000000023
 000000314180efbd 0000000000000000 0000000000000000 00007f31d2aef9c0
 0000000000000023 000000314180efbd 0000000000000033 0000000000000206
Call Trace:
Code:  Bad RIP value.
RIP  [<0000000000000293>] 0x293
 RSP <ffff88009d3f5f90>
CR2: 0000000000000293
Comment 1 Emmett Culley 2014-02-25 15:09:57 UTC 
Created attachment 867463 [details]
File: dmesg
Comment 2 Josh Boyer 2014-02-25 15:38:48 UTC 
There's really not much we can do about this one.  The stack trace doesn't contain any information we can use to determine what exactly went wrong.  It looks like either a stack overflow error where the wrong thing was popped off on return, or a dereference of a function pointer from a NULL table.

Without knowing where the kernel was at, we can't really begin to debug.  If this recreates easily, please install kernel-debug and see if you can get some additional information out of that.
Comment 3 Justin M. Forbes 2014-03-17 18:43:52 UTC 
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.
Comment 4 Emmett Culley 2014-06-24 23:51:43 UTC 
This problem has not repeated since I reported it.