VirtualBox

Opened 17 years ago

Closed 17 years ago

#175 closed defect (invalid)

NULL pointer dereference by loading the vboxdrv kernel module

Reported by: NooN001 Owned by:
Component: other Version:
Keywords: NULL pointer dereference linux kernel module Cc:
Guest type: other Host type: other

Description (last modified by Frank Mehnert)

Hello

I got a kernel null pointer dereference while i load the vboxdrv kernel module. I have a custom build kernel: Linux joshua 2.6.19.1 and a debian 'testing' system

In kern.log I found this:

<removed since the next comment contains a better log>

Change History (12)

comment:1 by NooN001, 17 years ago

I've updated my kernel and the vbox version, but i get still this error:

My kernel version is:

Linux joshua 2.6.20.2 #1 PREEMPT Fri Mar 9 23:52:47 CET 2007 i686 GNU/Linux

kernel log:

vboxdrv: Trying to deactivate NMI watchdog permanently...
vboxdrv: Successfully done.
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000002b
 printing eip:
c0268dd9
*pde = 00000000
Oops: 0002 [#1]
PREEMPT
Modules linked in: "vboxdrv" nvidia(P) agpgart ppdev lp ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables dm_crypt dm_mod snd_rtctimer rtc_sysfs rtc_core rtc_lib i2c_piix4 w83781d i2c_dev lm78 hwmon_vid i2c_isa vfat fat usbhid snd_ens1371 snd_rawmidi snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer hisax rtc parport_pc parport isdn serio_raw pcspkr i2c_sis96x snd soundcore snd_page_alloc ehci_hcd ohci_hcd slhc usbcore i2c_core unix
CPU:    0
EIP:    0060:[<c0268dd9>]    Tainted: P      VLI
EFLAGS: 00010296   (2.6.20.2 #1)
EIP is at misc_register+0xa/0x15c
eax: 0000001f   ebx: 0000001f   ecx: ffffffff   edx: 00000000
esi: 0000002b   edi: f8a38500   ebp: c4cd3ef0   esp: c4cd3eac
ds: 007b   es: 007b   ss: 0068
Process insmod (pid: 15035, ti=c4cd2000 task=f0a07070 task.ti=c4cd2000)
Stack: f8a38500 f8a38500 c4cd3ef0 c01197c1 f8a35bd4 ebd59000 f8a38500 f88f0088
       f8a37e64 00000001 c0149a36 00000000 c018bc35 f0d336e4 ebd59000 ebd59000
       f8a38500 00000017 c0132a92 f8a38548 c0394807 f8a3850c e5ecaf84 f8a38548
Call Trace:
 [<c01197c1>] printk+0x1b/0x1f
 [<f88f0088>] VBoxSupDrvInit+0x88/0x1fc ["vboxdrv"]
 [<c0149a36>] __vunmap+0x62/0xe5
 [<c018bc35>] sysfs_create_group+0x86/0xb1
 [<c0132a92>] sys_init_module+0x125/0x1736
 [<c0102df8>] syscall_call+0x7/0xb
 =======================
Code: 5d c3 8b 04 24 83 c4 04 5b 5e 5f 5d c3 ff 05 08 de 3c c0 7f 0b 8d 05 08 de 3c c0 e8 86 bd 0c 00 c3 56 53 83 ec 14 89 c3 8d 70 0c <89> 70 0c 89 76 04 ff 0d 08 de 3c c0 79 0b 8d 05 08 de 3c c0 e8
EIP: [<c0268dd9>] misc_register+0xa/0x15c SS:ESP 0068:c4cd3eac

svn info:

vbox$ svn info
Pfad: .
URL: http://virtualbox.org/svn/vbox/trunk
Basis des Projektarchivs: http://virtualbox.org/svn/vbox
UUID des Projektarchivs: cfe28804-0f27-0410-a406-dd0f0b0b656f
Revision: 1460
Knotentyp: Verzeichnis
Plan: normal
Letzter Autor: vboxsync
Letzte geänderte Rev: 1460
Letztes Änderungsdatum: 2007-03-14 04:45:32 +0100 (Mi, 14 Mär 2007)

Has somebody at least an idea what I can do to get ride of this?

comment:2 by Frank Mehnert, 17 years ago

I'm sure we will find and fix the problem. You can help us by posting:

  • your compiled vboxdrv module which causes the crash
  • your Linux kernel config (.config in your Linux kernel directory)
  • the complete output of dmesg after your kernel successfully booted

Thanks in advance.

comment:3 by Frank Mehnert, 17 years ago

Description: modified (diff)

comment:4 by NooN001, 17 years ago

Hello frank,

I put a tar.gz archive at http://windbuechse.samba-tng.org/vbox_kernel2.6.20.2_rev1460.tar.gz with the information you requested. I hope this will help.

Thank you

comment:5 by Frank Mehnert, 17 years ago

Ok. How did you compile the vboxdrv compiler? Please could you post me the command line and the compiler output please?

comment:6 by Frank Mehnert, 17 years ago

I mean the vboxdrv kernel module of course :)

comment:7 by NooN001, 17 years ago

Hello frank,

I made it like it was described on the page:

  1. configure
  2. source env.sh
  3. kmk

I will make you a log of the process.

comment:8 by Frank Mehnert, 17 years ago

All right, that is the problem: The vboxdrv.ko module which you find in the bin/ directory is not meant to be loaded into the current kernel! Instead of this go into bin/src and call make there! The vboxdrv.ko module in in/ is only to check if the module compiles right. We will change that sometimes ...

comment:9 by NooN001, 17 years ago

okey. I will try it.

thanks for your help :-)

comment:10 by NooN001, 17 years ago

I tried the vboxdrv.ko there:

~/source/vbox/out/linux.x86/release/obj/src/VBox/HostDrivers/vboxdrv$ sudo insmod vboxdrv.ko Speicherzugriffsfehler

but got anyway the NULL pointer dereference. befor I used the vboxdrv.ko from

~/source/vbox/out/linux.x86/release/bin/vboxdrv.ko

comment:11 by Frank Mehnert, 17 years ago

Please do what I told you! Compile the tree and go to out/linux.x86/release/bin/src and do make there! Then use this module!

comment:12 by Frank Mehnert, 17 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use