Red Hat Bugzilla – Bug 1029704
[abrt] open-vm-tools-9.4.0-1.fc20: Hostinfo_TouchBackDoor: Process /usr/bin/vmtoolsd was killed by signal 11 (SIGSEGV)
Last modified: 2015-10-26 07:56:44 EDT
Version-Release number of selected component:
cmdline: /usr/bin/vmtoolsd -n vmusr
runlevel: N 5
Thread no. 1 (4 frames)
#0 Hostinfo_TouchBackDoor at hostinfoHV.c:521
#1 VmCheckSafe at vmcheck.c:150
#2 VmCheck_IsVirtualWorld at vmcheck.c:267
#3 ToolsCore_Setup at mainLoop.c:405
Potential duplicate: bug 969688
Created attachment 823199 [details]
Created attachment 823200 [details]
Created attachment 823201 [details]
Created attachment 823202 [details]
Created attachment 823203 [details]
Created attachment 823204 [details]
Created attachment 823205 [details]
Created attachment 823206 [details]
Created attachment 823207 [details]
Created attachment 823208 [details]
Created attachment 823209 [details]
It is same as bug 969688.
Could you please check and confirm if removing Nvidia driver helps in avoiding this bug as mentioned by Mirko in https://bugzilla.redhat.com/show_bug.cgi?id=969688#c19?
*** This bug has been marked as a duplicate of bug 969688 ***
I have not been able to reproduce this bug. I have since gone through many rebuilds of the system, and have stopped loading VirtualBox. I do not receive this error when using VMware.
I just received the same error, just as you mentioned, immediately upon booting into F20. While you have not been able to reproduce it, many others have-- over 2000 counts according to the ABRT Server. I'm not sure if it's relevant but I did install kernel-tools-debuginfo, kernel-tools-libs-devel, and redhat-lsb (all seperately) before the system was shutdown.
I received the error message a second time, which is concerning since I assumed(hoped) I'd have "trouble reproducing it" just as Dan did. I wonder if the SELinux fcontext changes I had made recently to my server's DocumentRoot folder; I saw this in my journal log during the most recent event:
>type=1701 audit(1389891464.950:2211): auid=1000 uid=1000 gid=1000 ses=18 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=9780 comm="vmtoolsd" re
ason="memory violation" sig=11
ILMostro, could you please provide little more details about your environment? Are you running on physical or on a virtual machine? If it is running in a virtual machine, what is the hypervisor you are using? Also, it would help a lot if you could isolate the issue to a specific system change you have made.
I would appreciate if you could also verify the Nvidia driver issue as mentioned in my comment #12.
This was a while ago; IIRC, I was running on baremetal HW when I received those messages. Fairly certain that the nvidia-related resolution had no noticeable affect. I wonder how/where to proceed from here w/this bug, as there doesn't seem to have been any activity in 2 yrs.
(In reply to ILMostro from comment #17)
> This was a while ago; IIRC, I was running on baremetal HW when I received
> those messages. Fairly certain that the nvidia-related resolution had no
> noticeable affect. I wonder how/where to proceed from here w/this bug, as
> there doesn't seem to have been any activity in 2 yrs.
Do you still see this issue with latest Fedora?