From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: BUG or virtualbox issue?
Date: Fri, 26 Dec 2008 12:31:33 +0100 [thread overview]
Message-ID: <4954C095.3080300@xs4all.nl> (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
next reply other threads:[~2008-12-26 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 11:31 Udo van den Heuvel [this message]
2008-12-26 19:42 ` BUG or virtualbox issue? Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4954C095.3080300@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox