Bug 428488 - Receive invalid opcode: 0000 [1] SMP while running VirtualBox
Receive invalid opcode: 0000 [1] SMP while running VirtualBox
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
7
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-11 20:19 EST by Arc C.
Modified: 2008-01-16 00:03 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-16 00:03:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Arc C. 2008-01-11 20:19:46 EST
Every time starting VM in VirtualBox I get the following in /var/log/messages
and not able to use the VirtualBox anymore:
---------------------
Jan  9 13:20:37 rambam kernel: invalid opcode: 0000 [1] SMP
Jan  9 13:20:37 rambam kernel: CPU 1
Jan  9 13:20:37 rambam kernel: Modules linked in: vboxdrv(U) lp parport_pc ppdev
parport ipt_MASQUERADE iptable_nat
 nf_nat nfsd exportfs lockd nfs_acl auth_rpcgss tun autofs4 hidp rfcomm l2cap
bluetooth sunrpc bridge nf_conntrack_
netbios_ns nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink ipt_REJECT
iptable_filter ip_tables xt_tcpudp ip6t_REJ
ECT ip6table_filter ip6_tables x_tables cpufreq_ondemand acpi_cpufreq dm_mirror
dm_multipath dm_mod video output sb
s battery ac ipv6 snd_usb_audio snd_usb_lib snd_rawmidi snd_hwdep snd_hda_intel
snd_seq_dummy snd_seq_oss snd_seq_m
idi_event snd_seq snd_seq_device firewire_ohci 3c59x iTCO_wdt snd_pcm_oss
snd_mixer_oss atl1 snd_pcm i2c_i801 iTCO_
vendor_support usb_storage pcspkr firewire_core crc_itu_t mii nvidia(P)(U)
floppy usblp snd_timer snd soundcore but
ton sr_mod i2c_core snd_page_alloc cdrom sg ahci pata_jmicron ata_piix
ata_generic libata sd_mod scsi_mod raid456 a
sync_xor async_memcpy async_tx xor raid1 ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd
Jan  9 13:20:38 rambam kernel: Pid: 8475, comm: VirtualBox Tainted: P       
2.6.23.12-52.fc7 #1
Jan  9 13:20:38 rambam kernel: RIP: 0010:[<ffffffff88c94e4b>] 
[<ffffffff88c94e4b>] :vboxdrv:g_abExecMemory+0x2320b
/0x180000
Jan  9 13:20:38 rambam kernel: RSP: 0018:ffff810010129d30  EFLAGS: 00010046
Jan  9 13:20:38 rambam kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX:
0000000000000203
Jan  9 13:20:38 rambam kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI:
0000000000004824
Jan  9 13:20:39 rambam kernel: RBP: ffff810010129dc8 R08: 0000000000000602 R09:
ffff810010129c60
Jan  9 13:20:39 rambam kernel: R10: 0000000000000001 R11: 00002aaab0b6d0f0 R12:
0000000000000001
Jan  9 13:20:39 rambam kernel: R13: ffff810010129d88 R14: ffffc20000c1a980 R15:
ffffc20000c1a000
Jan  9 13:20:39 rambam kernel: FS:  0000000041626950(0063)
GS:ffff810037cb9300(0000) knlGS:0000000000000000
Jan  9 13:20:39 rambam kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jan  9 13:20:39 rambam kernel: CR2: 00002aaad2117408 CR3: 000000000bf22000 CR4:
00000000000026e0
Jan  9 13:20:39 rambam kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
Jan  9 13:20:39 rambam kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
Jan  9 13:20:39 rambam kernel: Process VirtualBox (pid: 8475, threadinfo
ffff810010128000, task ffff810028b11040)
Jan  9 13:20:39 rambam kernel: Stack:  ffffffff88c75e62 ffff810001605b98
ffffffff00000003 1389600000000000
Jan  9 13:20:39 rambam kernel:  0000006780000b0e 0000000000000000
ffffffff81086927 0000000000000006
Jan  9 13:20:39 rambam kernel:  0000000000000000 0000000000000000
0000000000000699 0000000000000000
Jan  9 13:20:39 rambam kernel: Call Trace:
Jan  9 13:20:39 rambam kernel:  [<ffffffff88c75e62>]
:vboxdrv:g_abExecMemory+0x4222/0x180000
Jan  9 13:20:39 rambam kernel:  [<ffffffff81086927>] can_share_swap_page+0x2d/0x6a
Jan  9 13:20:39 rambam kernel:  [<ffffffff88c74761>]
:vboxdrv:g_abExecMemory+0x2b21/0x180000
Jan  9 13:20:39 rambam kernel:  [<ffffffff88c74871>]
:vboxdrv:g_abExecMemory+0x2c31/0x180000
Jan  9 13:20:39 rambam kernel:  [<ffffffff88c949ed>]
:vboxdrv:g_abExecMemory+0x22dad/0x180000
Jan  9 13:20:39 rambam kernel:  [<ffffffff88c72194>]
:vboxdrv:g_abExecMemory+0x554/0x180000
Jan  9 13:20:39 rambam kernel:  [<ffffffff88c6c9c3>]
:vboxdrv:supdrvIOCtlFast+0x42/0x56
Jan  9 13:20:39 rambam kernel:  [<ffffffff88c6c065>]
:vboxdrv:VBoxSupDrvIOCtl+0x38/0x1c0
Jan  9 13:20:39 rambam kernel:  [<ffffffff8102d026>] update_curr+0xf8/0x11a
Jan  9 13:20:39 rambam kernel:  [<ffffffff810a3181>] do_ioctl+0x21/0x6b
Jan  9 13:20:39 rambam kernel:  [<ffffffff810a340e>] vfs_ioctl+0x243/0x25c
Jan  9 13:20:40 rambam kernel:  [<ffffffff810a3480>] sys_ioctl+0x59/0x79
Jan  9 13:20:40 rambam kernel:  [<ffffffff8100bd35>] tracesys+0xd5/0xda
Jan  9 13:20:40 rambam kernel:
Jan  9 13:20:40 rambam kernel:
Jan  9 13:20:40 rambam kernel: Code: 0f 79 fe 73 06 b8 5f f0 ff ff c3 75 05 b8
60 f0 ff ff c3 cc
Jan  9 13:20:40 rambam kernel: RIP  [<ffffffff88c94e4b>]
:vboxdrv:g_abExecMemory+0x2320b/0x180000
Jan  9 13:20:40 rambam kernel:  RSP <ffff810010129d30>
------------
After that I'm unable to unload vboxdrv module:
root# lsmod|grep vboxdrv
vboxdrv              1647616  1
root# rmmod -f vboxdrv
ERROR: Removing 'vboxdrv': Resource temporarily unavailable
root# modprobe -r vboxdrv
FATAL: Module vboxdrv is in use.

The vboxdrv module is compiled with every kernel update and can be re-compiled
if necessary. The current kernel version is:
root# uname -a
Linux rambam 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64 x86_64
x86_64 GNU/Linux
Comment 1 Christopher Brown 2008-01-16 00:03:11 EST
I note your bug filed at:

http://www.virtualbox.de/ticket/1059

As this is a Virtualbox issue (and not a kernel bug as the module is not
included in the kernel) I am closing as such. Please re-open should the above
ticket re-direct you back to seek a resolution here. Thank you for taking the
time to file the report.

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