Bugzilla Bug 218198

The vboxdrv doesn't load for the 2.6.25 kernel.  The emerge completes, but a
warning is produced when updating the module dependencies.

innotek has an updated module tarball for this kernel at
http://www.virtualbox.de/download/vboxdrv-1.5.7-for-linux.2.6.25.tar.gz

Reproducible: Always

Steps to Reproduce:
1. upgrade to 2.6.25 kernel
2. emerge -1 virtualbox-modules
3. modprobe vboxdrv

Actual Results:  
 * Removing app-emulation/virtualbox-modules-1.5.6 from moduledb.
>>> Original instance of package unmerged safely.
 * Updating module dependencies for 2.6.25-gentoo ...
WARNING: //lib/modules/2.6.25-gentoo/misc/vboxdrv.ko needs unknown symbol
change_page_a  [ ok ]
 * Adding module to moduledb.
>>> app-emulation/virtualbox-modules-1.5.6 merged.


Expected Results:  
Module should load fine

I have the same problem. 

modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.25-gentoo-r1/misc/vboxdrv.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

dmesg | grep vboxdrv
vboxdrv: Unknown symbol change_page_attr

Weird it loaded here so there must be a work around:

betelgeuse@pena /usr/portage/app-emulation/virtualbox-modules $ lsmod | grep
vbox
vboxdrv                35176  1
betelgeuse@pena /usr/portage/app-emulation/virtualbox-modules $ uname -a
Linux pena 2.6.25-gentoo-r1 #1 SMP Sat Apr 19 13:20:10 EEST 2008 i686 Intel(R)
Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel GNU/Linux

(In reply to comment #2)
> Weird it loaded here so there must be a work around:
> 
Hi, 

maybe a workaround is possible[1] but unsafe[2], due the API change in kernel
2.6.25 is not a good idea to ignore the set_memory_nx()/set_memory_x() calls.

i just commited an ebuild for the new version of virtualbox-modules on jokey's
overlay[3], in version 1.5.7 vboxdrv provides a fix for this problem as
described on LKML[4].


[1]
http://www.virtualbox.org/attachment/ticket/1263/vbox-r7168-chpgattr-out.patch
[2] http://www.virtualbox.org/ticket/1263
[3]
http://overlays.gentoo.org/dev/jokey/browser/trunk/app-emulation/virtualbox-modules
[4] http://lkml.org/lkml/2008/2/17/319

Added to cvs

(In reply to comment #4)
> Added to cvs

Can you please change the dependency in app-emulation/virtualbox-1.5.6
accordingly?

Thanks in advance,
Torsten

*** Bug 218935 has been marked as a duplicate of this bug. ***

*** Bug 219061 has been marked as a duplicate of this bug. ***

Huh, I'm not sure if this is really fixed.

We now have virtualbox-modules-1.5.7 in portage, but we don't have 1.5.7
version for other virtualbox packages. Looking at the ebuilds, both virtualbox
and virtualbox-bin depend on the exact same version of virtualbox-modules:
~app-emulation/virtualbox-modules-${PV}

So... Am I missing something or this isn't *really* fixed?

I was doing some searching on a similar problem with the binary nvidia drivers
and the SLUB allocator.  It seems that the vboxdrv also has issues when I try
to compile the kernel with SLUB.  I thought this may help narrow down the
problem.

hpwx070212 linux # make modules_install
  INSTALL drivers/scsi/scsi_wait_scan.ko
  DEPMOD  2.6.25-gentoo-r6
WARNING: /lib/modules/2.6.25-gentoo-r6/video/nvidia.ko needs unknown symbol
malloc_sizes
WARNING: /lib/modules/2.6.25-gentoo-r6/misc/vboxdrv.ko needs unknown symbol
change_page_attr

This bug has been fixed at least for app-emulation/virtualbox-modules-1.6.2. It
works perfectly here for Linux version 2.6.26-rc8 (root@loki) (gcc version
4.1.2 (Gentoo 4.1.2 p1.1)). I had this problem with 2.6.25 and 2.6.26 in
earlier versions.

by the way 1.6.2 still have the ~amd64 flag...

seems like this problem came back again with 1.6.4 with my amd64 machine

(In reply to comment #12)
> seems like this problem came back again with 1.6.4 with my amd64 machine
> 

Hi
can you please:
- describe exactly what kind of problem you noticed.
- report which kernel are you running/using with vboxdrv.
- report if you are using SLUB with your kernel (zgrep SLUB /proc/config.gz).

> can you please:
> - describe exactly what kind of problem you noticed.

virtualbox module does not run

# modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.25-gentoo-r7/misc/vboxdrv.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

because of

# dmesg | grep vboxdrv
vboxdrv: Unknown symbol change_page_attr

> - report which kernel are you running/using with vboxdrv.

# uname -a
Linux monolith 2.6.25-gentoo-r7 #10 SMP PREEMPT Tue Aug 19 09:33:17 EEST 2008
x86_64 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux

> - report if you are using SLUB with your kernel (zgrep SLUB /proc/config.gz).

# zgrep SLUB /proc/config.gz
CONFIG_SLUB_DEBUG=y
CONFIG_SLUB=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set

I have same kernel version, and the same issue with vboxdrv.

dragonfly@Sakura ~ $ uname -a
Linux Sakura 2.6.25-gentoo-r7.Sakura #1 SMP PREEMPT Fri Aug 1 14:22:35 EDT 2008
x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux
dragonfly@Sakura ~ $ zgrep SLUB /proc/config.gz 
# CONFIG_SLUB is not set



(In reply to comment #14)
> > can you please:
> > - describe exactly what kind of problem you noticed.
> 
> virtualbox module does not run
> 
> # modprobe vboxdrv
> FATAL: Error inserting vboxdrv (/lib/modules/2.6.25-gentoo-r7/misc/vboxdrv.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> 
> because of
> 
> # dmesg | grep vboxdrv
> vboxdrv: Unknown symbol change_page_attr
> 
> > - report which kernel are you running/using with vboxdrv.
> 
> # uname -a
> Linux monolith 2.6.25-gentoo-r7 #10 SMP PREEMPT Tue Aug 19 09:33:17 EEST 2008
> x86_64 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
> 
> > - report if you are using SLUB with your kernel (zgrep SLUB /proc/config.gz).
> 
> # zgrep SLUB /proc/config.gz
> CONFIG_SLUB_DEBUG=y
> CONFIG_SLUB=y
> # CONFIG_SLUB_DEBUG_ON is not set
> # CONFIG_SLUB_STATS is not set
> 

VirtualBox 1.6.4 plays perfectly well with both 2.6.25 kernel and SLUB.
Maybe stabilizing to 1.6.x would solve the problem?

(In reply to comment #16)
> VirtualBox 1.6.4 plays perfectly well with both 2.6.25 kernel and SLUB.
> Maybe stabilizing to 1.6.x would solve the problem?

I think this is a good idea. I've been using 1.6.2 with no problems for about 1
or 2 months.