[PlanetCCRMA] oracle vbox 3.2.8 and 2.6.31 RT x86_64 = kernel bug

Luc Tanguay lucus at sympatico.ca
Tue Sep 7 18:56:17 PDT 2010


I'm trying to use VBox 3.2.8 on my PlanetCCRMA'ed Fedora 12 AMD 64-bit 
machine.  VBox (or I should say its kernel module since they are 
generated even when the VM is not running) generates kerneloops, like 
this one (extract from /var/log/messages):

kernel: BUG: sleeping function called from invalid context at 
kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 5835, name: VirtualBox
kernel: Pid: 5835, comm: VirtualBox Tainted: P   #1
kernel: Call Trace:
kernel: [<ffffffff81042002>] __might_sleep+0xe6/0xe8
kernel: [<ffffffff81083ade>] rt_spin_lock_fastlock.clone.1+0x34/0x79
kernel: [<ffffffff814514bd>] rt_spin_lock+0xe/0x10
kernel: [<ffffffffa0ced80e>] RTSpinlockAcquire+0x12/0x14 [vboxdrv]
kernel: [<ffffffffa0cf2545>] rtHandleTableLock+0x20/0x22 [vboxdrv]
kernel: [<ffffffffa0cf26d5>] RTHandleTableLookupWithCtx+0x5e/0xc9 [vboxdrv]
kernel: [<ffffffffa0ce9461>] SUPSemEventSignal+0x52/0x98 [vboxdrv]
kernel: [<ffffffffa0d16d2f>] g_abExecMemory+0x1fbaf/0x180000 [vboxdrv]
kernel: [<ffffffffa0d03dbe>] g_abExecMemory+0xcc3e/0x180000 [vboxdrv]
kernel: [<ffffffff814510e7>] ? rt_mutex_lock+0x31/0x36
kernel: [<ffffffffa0cffdfd>] g_abExecMemory+0x8c7d/0x180000 [vboxdrv]
kernel: [<ffffffffa0d3f2c7>] g_abExecMemory+0x48147/0x180000 [vboxdrv]
kernel: [<ffffffffa0d0ae2b>] g_abExecMemory+0x13cab/0x180000 [vboxdrv]
kernel: [<ffffffffa0ce37d7>] supdrvIOCtlFast+0x44/0x56 [vboxdrv]
kernel: [<ffffffffa0ce3270>] VBoxDrvLinuxIOCtl+0x44/0x1a3 [vboxdrv]
kernel: [<ffffffff8111f8d5>] vfs_ioctl+0x22/0x87
kernel: [<ffffffff8111fe3e>] do_vfs_ioctl+0x488/0x4ce
kernel: [<ffffffff8144ffdc>] ? thread_return+0x53/0xc8
kernel: [<ffffffff8111feda>] sys_ioctl+0x56/0x79
kernel: [<ffffffff81011e32>] system_call_fastpath+0x16/0x1b

How do I get rid of these messages?


More information about the PlanetCCRMA mailing list