Bug 756734 - [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at 00000054
Summary: [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at 00000054
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ec43a82e19fc53be84e98b8a3a6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-24 11:53 UTC by Reinier Balt
Modified: 2011-11-24 13:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-24 13:49:14 UTC
Type: ---


Attachments (Terms of Use)
File: smolt_data (4.08 KB, text/plain)
2011-11-24 11:54 UTC, Reinier Balt
no flags Details
File: backtrace (2.08 KB, text/plain)
2011-11-24 11:54 UTC, Reinier Balt
no flags Details

Description Reinier Balt 2011-11-24 11:53:58 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        BOOT_IMAGE=/vmlinuz-3.1.1-2.fc16.i686 root=/dev/mapper/vg_vmlinux16-lv_root ro rd.md=0 rd.dm=0 quiet SYSFONT=latarcyrheb-sun16 rhgb rd.lvm.lv=vg_vmlinux16/lv_swap rd.luks=0 rd.lvm.lv=vg_vmlinux16/lv_root KEYTABLE=us-acentos LANG=en_US.UTF-8
comment:        just installed vmware tools and the trace was there on reboot
kernel:         3.1.1-2.fc16.i686
reason:         BUG: unable to handle kernel NULL pointer dereference at 00000054
time:           Thu 24 Nov 2011 01:50:30 PM CET

backtrace:      Text file, 2133 bytes
smolt_data:     Text file, 4183 bytes

Comment 1 Reinier Balt 2011-11-24 11:54:01 UTC
Created attachment 535871 [details]
File: smolt_data

Comment 2 Reinier Balt 2011-11-24 11:54:03 UTC
Created attachment 535872 [details]
File: backtrace

Comment 3 Josh Boyer 2011-11-24 13:49:14 UTC
This is a problem in the vmhgfs, which Fedora does not provide and does not support.  You'll need to take this up with VMWare.


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