Bug 868962 - general protection fault caused by conflict with VMWare 9?
general protection fault caused by conflict with VMWare 9?
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-22 11:03 EDT by Luc Lalonde
Modified: 2012-10-22 11:22 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-10-22 11:22:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Luc Lalonde 2012-10-22 11:03:51 EDT
I am unable to use this version of the kernel:

kernel-3.6.2-4.fc17.x86_64

The system locks up everytime I boot up...  Here's what I have in the logs:

Oct 22 10:40:32 aeneas kernel: [  110.023916] general protection fault: 0000 [#1] SMP
Oct 22 10:40:32 aeneas kernel: [  110.023920] Modules linked in: vmnet(O) fuse lockd vsock(O) vmci(O) vmmon(O) sunrpc xt_recent nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack raid0 nvidia(PO) snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd i2c_i801 soundcore coretemp i7core_edac i2c_core e1000e iTCO_wdt iTCO_vendor_support lpc_ich mfd_core edac_core ppdev parport_pc mei kvm_intel parport kvm serio_raw microcode uinput crc32c_intel ata_generic pata_acpi video
Oct 22 10:40:32 aeneas kernel: [  110.023949] CPU 4
Oct 22 10:40:32 aeneas kernel: [  110.023953] Pid: 2089, comm: vmware-hostd Tainted: P           O 3.6.2-4.fc17.x86_64 #1 Larue Info Inc. Ordi PolyMtl/DH55TC
Oct 22 10:40:32 aeneas kernel: [  110.023955] RIP: 0010:[<ffffffffa0d5b21f>]  [<ffffffffa0d5b21f>] HostIF_SafeRDMSR+0xf/0x30 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.023963] RSP: 0018:ffff880416b1db88  EFLAGS: 00010246
Oct 22 10:40:32 aeneas kernel: [  110.023964] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000491
Oct 22 10:40:32 aeneas kernel: [  110.023966] RDX: 0000000000000000 RSI: ffff880413c45110 RDI: 0000000000000491
Oct 22 10:40:32 aeneas kernel: [  110.023967] RBP: ffff880416b1db88 R08: ffff88042fc96a60 R09: ffffffffa0d59882
Oct 22 10:40:32 aeneas kernel: [  110.023969] R10: 0000000005c4ccd4 R11: 0000000000000246 R12: 0000000000000000
Oct 22 10:40:32 aeneas kernel: [  110.023970] R13: ffff880413c45100 R14: ffff880413c45100 R15: 00007fff4d2479f0
Oct 22 10:40:32 aeneas kernel: [  110.023972] FS:  00007f6c1d947740(0000) GS:ffff88042fc80000(0000) knlGS:0000000000000000
Oct 22 10:40:32 aeneas kernel: [  110.023974] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 22 10:40:32 aeneas kernel: [  110.023975] CR2: 0000000000db93e0 CR3: 0000000414a1c000 CR4: 00000000000007e0
Oct 22 10:40:32 aeneas kernel: [  110.023977] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 22 10:40:32 aeneas kernel: [  110.023978] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct 22 10:40:32 aeneas kernel: [  110.023980] Process vmware-hostd (pid: 2089, threadinfo ffff880416b1c000, task ffff880416eedc40)
Oct 22 10:40:32 aeneas kernel: [  110.023981] Stack:
Oct 22 10:40:32 aeneas kernel: [  110.023982]  ffff880416b1dbb8 ffffffffa0d5bc33 ffffffffa0d5bbb0 ffff880416b1dbe8
Oct 22 10:40:32 aeneas kernel: [  110.023986]  ffff880413c45100 0000000000000000 ffff880416b1dbd8 ffffffffa0d5a990
Oct 22 10:40:32 aeneas kernel: [  110.023989]  ffff880413c45100 00000000fffffff4 ffff880416b1dc08 ffffffffa0d5da2c
Oct 22 10:40:32 aeneas kernel: [  110.023992] Call Trace:
Oct 22 10:40:32 aeneas kernel: [  110.023997]  [<ffffffffa0d5bc33>] Vmx86GetMSR+0x83/0xd0 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.024002]  [<ffffffffa0d5bbb0>] ? Vmx86GetUnavailPerfCtrsOnCPU+0x150/0x150 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.024007]  [<ffffffffa0d5a990>] HostIF_CallOnEachCPU+0x20/0x40 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.024012]  [<ffffffffa0d5da2c>] Vmx86_GetAllMSRs+0x2c/0x50 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.024016]  [<ffffffffa0d586df>] LinuxDriver_Ioctl+0x70f/0xd40 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.024021]  [<ffffffff8112a0e1>] ? unlock_page+0x31/0x50
Oct 22 10:40:32 aeneas kernel: [  110.024024]  [<ffffffff81150889>] ? __do_fault+0x3e9/0x550
Oct 22 10:40:32 aeneas kernel: [  110.024027]  [<ffffffff811534e5>] ? handle_pte_fault+0x95/0xb10
Oct 22 10:40:32 aeneas kernel: [  110.024030]  [<ffffffff81154869>] ? handle_mm_fault+0x259/0x320
Oct 22 10:40:32 aeneas kernel: [  110.024034]  [<ffffffff8161e27c>] ? do_page_fault+0x1bc/0x4b0
Oct 22 10:40:32 aeneas kernel: [  110.024039]  [<ffffffff8119ed71>] ? do_filp_open+0x41/0xa0
Oct 22 10:40:32 aeneas kernel: [  110.024042]  [<ffffffffa0d58d28>] LinuxDriver_UnlockedIoctl+0x18/0x20 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.024046]  [<ffffffff811a0cd9>] do_vfs_ioctl+0x99/0x580
Oct 22 10:40:32 aeneas kernel: [  110.024051]  [<ffffffff81179559>] ? kmem_cache_free+0x39/0x130
Oct 22 10:40:32 aeneas kernel: [  110.024053]  [<ffffffff811a1259>] sys_ioctl+0x99/0xa0
Oct 22 10:40:32 aeneas kernel: [  110.024055]  [<ffffffff816227e9>] system_call_fastpath+0x16/0x1b
Oct 22 10:40:32 aeneas kernel: [  110.024056] Code: 83 c4 01 e8 44 ce 3d e0 44 89 e0 48 3b 43 08 72 e9 48 89 df e8 f3 e4 41 e0 eb 9e 90 55 48 89 e5 66 66 66 66 90 31 c0 89 c2 89 f9 <0f> 32 31 ff 41 89 c0 48 c1 e2 20 89 f8 4c 09 c2 48 89 16 5d c3
Oct 22 10:40:32 aeneas kernel: [  110.024071] RIP  [<ffffffffa0d5b21f>] HostIF_SafeRDMSR+0xf/0x30 [vmmon]
Oct 22 10:40:32 aeneas kernel: [  110.024074]  RSP <ffff880416b1db88>
Oct 22 10:40:32 aeneas kernel: [  110.024082] ---[ end trace fdf267645e5119cc ]---
Comment 1 Josh Boyer 2012-10-22 11:22:36 EDT
VMWare problem.  You'll need to take it up with them.

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