VBox 3.0.2 failure with Ubuntu x64 & Kernel 2.6.31 rc2

[meijkl]

Despite inserting "nmi_watchdog=0" and removing "splash" (suggested in some postings) in grub VirtualBox fails to start and refers to the nmi-watchdog.

dmesg output is:

[ 293.127992] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[ 293.128020] vboxdrv: NMI watchdog either active or at least initialized. Please disable the NMI
[ 293.128022] vboxdrv: watchdog by specifying 'nmi_watchdog=0' at kernel command line.

Kernel 2.6.30 works without issues.

Any idea?

Thanks
Klaus

[Perryg]

The NMI watchdog is usually used by programmers to check while they are building.
I assume that you are using Karmic Koala since this seems to be a topic discussed a lot on the Ubuntu forums.
I think that you will find once the build is released it will not be a problem, but at the time being it is.
You can try to watch the Ubuntu forums for their suggested fix when it is available.
I hope you can understand why there would not be a fix from VBox at this time since the OS is not even close to be released(October I believe).

[meijkl]

The NMI watchdog is usually used by programmers to check while they are building.
I assume that you are using Karmic Koala since this seems to be a topic discussed a lot on the Ubuntu forums.
I think that you will find once the build is released it will not be a problem, but at the time being it is.
You can try to watch the Ubuntu forums for their suggested fix when it is available.
I hope you can understand why there would not be a fix from VBox at this time since the OS is not even close to be released(October I believe).

It's an interesting aspect but I'm not yet convinced that this is reason for the problem. In the meantime I've installed kernel version 2.6.31 rc3 (basic Ubuntu version is Jaunty) and now vboxdrv works deterministically after the 3rd modprobe:

Code: Select all

root@x-1l:~# modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.31-3-generic/updates/dkms/vboxdrv.ko): Invalid argument
root@x-1l:~# modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.31-3-generic/updates/dkms/vboxdrv.ko): Invalid argument
root@x-1l:~# modprobe vboxdrv
root@x-1l:~# 

Strange, isn't it?

When checking dmesg I also found the message:

Code: Select all

[ 8524.021965] Platform driver 'vboxdrv' needs updating - please use dev_pm_ops

Probably not directly related with my problem but maybe a hint that the driver isn't yet ready for Kernel 2.6.31.

Klaus

modedit: Blue is hard to read on a dark grey background (ProDark theme), please don't use low contrast colours. Stick to code blocks instead.

[Perryg]

IMHO, I actually think they are directly connected, otherwise there would not be an issue. I suspect that the next VBox release will improve and it will incorporate the necessary fixes to accommodate the new kernel. Such is the nemesis of working on the bleeding edge.

[frank]

The warning about Platform driver 'vboxdrv' needs updating - please use dev_pm_ops is just a warning, nothing more. The real problem is how to deactivate the NMI. Unfortunately we are still not able to reproduce this problem. It seems that this happens only on certain hardware. You could help us by attaching (please attach, do not cut'n'paste!) the output of dmesg to this ticket.