Opened 12 years ago
Last modified 12 years ago
#11035 closed defect
failed to start kernel module vboxdrv (custom kernel) — at Version 5
Reported by: | skywk | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.2.0 |
Keywords: | custom kernel module starting failed | Cc: | |
Guest type: | all | Host type: | Linux |
Description (last modified by )
The kernel module vboxdrv failed to start, when modprobe vboxdrv, the dmesg shows these:
[ 48.500393] vboxdrv: Found 2 processor cores. [ 48.500524] BUG: unable to handle kernel NULL pointer dereference at 00000600 [ 48.502986] IP: [<f8de458a>] VBoxHost_RTR0MemObjFree+0x294/0x294 [vboxdrv] [ 48.503333] *pde = 00000000 [ 48.503333] Oops: 0000 [#1] PREEMPT SMP [ 48.503333] Modules linked in: vboxdrv(O+) coretemp tp_smapi(O) thinkpad_ec(O) loop firewire_sbp2 fuse snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep thinkpad_acpi snd_pcm snd_page_alloc nvram snd_seq snd_seq_device snd_timer arc4 psmouse serio_raw i2c_i801 rng_core iwl3945 snd iwl_legacy mac80211 cfg80211 soundcore rfkill battery ac evdev processor microcode i915 i2c_algo_bit drm_kms_helper drm i2c_core sg usbhid hid sd_mod crc_t10dif ide_pci_generic uhci_hcd ahci libahci libata scsi_mod piix ide_core sdhci_pci sdhci mmc_core firewire_ohci firewire_core crc_itu_t ehci_hcd usbcore e1000e usb_common video thermal thermal_sys button [last unloaded: scsi_wait_scan] [ 48.503333] [ 48.503333] Pid: 2324, comm: modprobe Tainted: G O 3.2.1-ck1-bfs416 #1 LENOVO 636386U/636386U [ 48.503333] EIP: 0060:[<f8de458a>] EFLAGS: 00010293 CPU: 0 [ 48.503333] EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] [ 48.503333] EAX: f4cac000 EBX: f8dff158 ECX: 00000000 EDX: 00000002 [ 48.503333] ESI: f4cac000 EDI: 00000600 EBP: 00000000 ESP: f5673e98 [ 48.503333] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 48.503333] Process modprobe (pid: 2324, ti=f5672000 task=f4f7b930 task.ti=f5672000) [ 48.503333] Stack: [ 48.503333] f8ddd112 f4e9c850 00000000 f4e9c850 0000e444 00000020 000000d0 00000000 [ 48.503333] 00000010 f5673ee0 00000020 f8de4ef3 00000002 00000002 f4caa200 f4caa224 [ 48.503333] f8d72000 f8de3757 f4edcbc0 f8de378a f8de7362 00000010 f8df951f 00000000 [ 48.503333] Call Trace: [ 48.503333] [<f8ddd112>] ? supdrvInitDevExt+0x103/0x697 [vboxdrv] [ 48.503333] [<f8de4ef3>] ? rtR0MemAllocEx+0x4a/0x9d [vboxdrv] [ 48.503333] [<f8d72000>] ? 0xf8d71fff [ 48.503333] [<f8de3757>] ? rtR0MemAlloc+0x8/0x15 [vboxdrv] [ 48.503333] [<f8de378a>] ? VBoxHost_RTMemAllocTag+0xb/0x18 [vboxdrv] [ 48.503333] [<f8de7362>] ? VBoxHost_RTSpinlockCreate+0x1b/0x4f [vboxdrv] [ 48.503333] [<f8de4ca7>] ? rtR0PowerNotificationInit+0x11/0x15 [vboxdrv] [ 48.503333] [<f8d72000>] ? 0xf8d71fff [ 48.503333] [<f8d72050>] ? VBoxDrvLinuxInit+0x50/0xc7 [vboxdrv] [ 48.503333] [<c1001202>] ? do_one_initcall+0x66/0x10c [ 48.503333] [<c104ffab>] ? sys_init_module+0x136c/0x153f [ 48.503333] [<c12bff9f>] ? sysenter_do_call+0x12/0x28 [ 48.503333] Code: fe ff ff e9 cf fe ff ff 8b 4a 1c 85 c9 0f 84 47 ff ff ff 8d 34 8d fc ff ff ff 89 4c 24 04 e9 5c ff ff ff 83 c4 08 5b 5e 5f 5d c3 <8b> 0f 8b 47 04 8d 91 00 10 00 00 81 fa ff 1f 00 00 76 45 81 39 [ 48.503333] EIP: [<f8de458a>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] SS:ESP 0068:f5673e98 [ 48.503333] CR2: 0000000000000600 [ 48.608313] ---[ end trace 4eecccc0ba5c7023 ]---
I run a custom compiled kernel:
Linux debian.zzx.x60 3.5.4-bfs-424 #2 SMP Thu Sep 27 09:20:10 CST 2012 i686 GNU/Linux
and ...3.2.1-ck1-bfs416...
both failed.
but when run the kernel supplied by debian, i.e. ...3.2.0-3-686-pae... it works fine.
The VBOX version is 4.2.0, 4.1.18 also tried, and is the same as the former.
Change History (8)
by , 12 years ago
Attachment: | vbox.kernel.log added |
---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
I can confirm this bug on VBox 4.2.4
I am running a "vanilla" kernel directly from git from Linus stable branch with no extra patches, .config attached for 3.6.10
I have tried with earlier kernels as well: 3.5.4 and 3.4.2 since I have had vbox running succesfully with those before, but the error is the same.
For me it does not help to downgrade to vbox 4.1.18 though.
comment:3 by , 12 years ago
Forgot something. I've also tried with latest stable kernel: 3.7.0 but with this the vbox modules no longer builds.
Snippet from my dmesg when loading vboxdrv:
vboxdrv: Found 2 processor cores. BUG: unable to handle kernel NULL pointer dereference at 00000700 IP: [<f977dac2>] VBoxHost_RTR0MemObjFree+0x294/0x294 [vboxdrv] *pdpt = 0000000026144001 *pde = 0000000000000000 Oops: 0000 [#1] PREEMPT SMP Modules linked in: vboxdrv(O+) Pid: 14395, comm: modprobe Tainted: G O 3.6.10 #14 LENOVO 74585NG/74585NG EIP: 0060:[<f977dac2>] EFLAGS: 00210293 CPU: 1 EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] EAX: e64b6000 EBX: e64b6000 ECX: 264b6000 EDX: 00000002 ESI: f97963c8 EDI: 00000700 EBP: 00000000 ESP: e8ad9e84 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 CR0: 8005003b CR2: 00000700 CR3: 30243000 CR4: 000407f0 DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 DR6: ffff0ff0 DR7: 00000400 Process modprobe (pid: 14395, ti=e8ad8000 task=e9f5e6c0 task.ti=e8ad8000) Stack: f9779067 e9dfbb50 00000000 e9dfbb50 c10674fe e9f5e2e0 00000000 00000000 c10ccb9b 000000d0 f977e4fb 00000000 00000008 e8ad9edc 00000018 f977e4fb 00000004 00000000 f9796288 e3300f80 f979f000 f977cc8f d4d28960 f977ccc2 Call Trace: [<f9779067>] ? supdrvInitDevExt+0xdd/0x72d [vboxdrv] [<c10674fe>] ? ttwu_do_wakeup+0xb/0xa3 [<c10ccb9b>] ? __kmalloc+0x88/0xaa [<f977e4fb>] ? rtR0MemAllocEx+0x69/0xbc [vboxdrv] [<f977e4fb>] ? rtR0MemAllocEx+0x69/0xbc [vboxdrv] [<f979f000>] ? 0xf979efff [<f977cc8f>] ? rtR0MemAlloc+0x8/0x15 [vboxdrv] [<f977ccc2>] ? VBoxHost_RTMemAllocTag+0xb/0x18 [vboxdrv] [<f9780a1c>] ? VBoxHost_RTSpinlockCreate+0xc/0x30 [vboxdrv] [<f979f000>] ? 0xf979efff [<f979f050>] ? VBoxDrvLinuxInit+0x50/0xc7 [vboxdrv] [<c100114e>] ? do_one_initcall+0x66/0x104 [<c1083912>] ? sys_init_module+0x11d7/0x13de [<c15f5bcc>] ? sysenter_do_call+0x12/0x22 Code: fe ff ff e9 cf fe ff ff 8b 4a 1c 85 c9 0f 84 47 ff ff ff 8d 34 8d fc ff ff ff 89 4c 24 04 e9 5c ff ff ff 83 c4 08 5b 5e 5f 5d c3 <8b> 0f 8b 47 04 8d 91 00 10 00 00 81 fa ff 1f 00 00 76 45 81 39 EIP: [<f977dac2>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] SS:ESP 0068:e8ad9e84 CR2: 0000000000000700 ---[ end trace af95c3bddf7757dd ]---
comment:4 by , 12 years ago
Please attach your compiled vboxdrv.ko module. Which Linux distribution are you using?
comment:5 by , 12 years ago
Description: | modified (diff) |
---|---|
Summary: | failed to start kernel module vboxdrv → failed to start kernel module vboxdrv (custom kernel) |
Still relevant with VBox 4.2.4? This looks to me like a special Linux kernel, does it have some extra patches applied?