Skip to contentSkip to conversation

BUG or virtualbox issue?

DISCUSSION Udo van den Heuvel 2 participants 2 messages Dec 26, 2008

lore
Share & tools
lore
#0 lore raw

Hello,

Just started virtualbox for the first time on x86_64 Phenom system; is this a kernel issue or something for the VirtualBox people?

Dec 26 12:20:01 surfplank2 kernel: BUG: using smp_processor_id() in preemptible [00000000] code: VirtualBox/26774
Dec 26 12:20:01 surfplank2 kernel: caller is RTMpCpuId+0x9/0x10 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: Pid: 26774, comm: VirtualBox Not tainted 2.6.28 #3
Dec 26 12:20:01 surfplank2 kernel: Call Trace:
Dec 26 12:20:01 surfplank2 kernel: [<ffffffff8036c964>] debug_smp_processor_id+0xd4/0xe0
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa03976a9>] RTMpCpuId+0x9/0x10 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa03a59c3>] g_abExecMemory+0x6403/0x180000 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa03a46a8>] g_abExecMemory+0x50e8/0x180000 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa03aedb7>] g_abExecMemory+0xf7f7/0x180000 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa03af232>] g_abExecMemory+0xfc72/0x180000 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa03af0e7>] g_abExecMemory+0xfb27/0x180000 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa0392a9d>] supdrvIOCtl+0xfbd/0x1e00 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa0395f55>] rtMemAlloc+0x85/0xf0 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffffa038e2d4>] VBoxDrvLinuxIOCtl+0x114/0x1f0 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: [<ffffffff802bb75f>] vfs_ioctl+0x2f/0xa0
Dec 26 12:20:01 surfplank2 kernel: [<ffffffff802bb84c>] do_vfs_ioctl+0x7c/0x470
Dec 26 12:20:01 surfplank2 kernel: [<ffffffff802bbce1>] sys_ioctl+0xa1/0xb0
Dec 26 12:20:01 surfplank2 kernel: [<ffffffff8020b8cb>] system_call_fastpath+0x16/0x1b

Udo

#1 lore raw
Quoted 7 lines · Udo van den Heuvel

Hello,

Just started virtualbox for the first time on x86_64 Phenom system; is this a kernel issue or something for the VirtualBox people?

Dec 26 12:20:01 surfplank2 kernel: BUG: using smp_processor_id() in preemptible [00000000] code: VirtualBox/26774
Dec 26 12:20:01 surfplank2 kernel: caller is RTMpCpuId+0x9/0x10 [vboxdrv]
Dec 26 12:20:01 surfplank2 kernel: Pid: 26774, comm: VirtualBox Not tainted 2.6.28 #3

Looks like the virtualbox code forgot to switch off preemption before calling smp_processor_id().

This is broken, because the thread could get de-scheduled and re-scheduled onto another CPU, which means the code could end up using the wrong smp processor ID.

Signature · 1 line
All rights reversed.