Opened 13 years ago
Closed 12 years ago
#9482 closed defect (invalid)
Can't compile/unload vbox modules on linux host (kernel: 3.0.0.7)
| Reported by: | Alexander Bierbaumer | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 4.1.2 |
| Keywords: | modules | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description (last modified by )
Hi there!
Tried to compile modules with kernels: 3.0.0.7 and 2.6.39
Modules are loaded as permanent (didn't even know this is possible) and vboxdrv can't unload it
dmesg:
BUG: unable to handle kernel paging request at 23599500
IP: [<f8845101>] VBoxPciLinuxInit+0x101/0x1000 [vboxpci]
and
Pid: 14641, comm: modprobe Not tainted 3.0.0-7-generic #9-Ubuntu Dell Inc. Latitude E6500 /0W612R
lsmod:
vboxpci 32018 1 [permanent]
vboxnetadp 13328 0 [permanent]
vboxnetflt 27252 0 [permanent]
vboxdrv 251877 3 vboxpci,vboxnetadp,vboxnetflt,[permanent]
during vbox install:
modprobe vboxpci failed. Please use 'dmesg' to find out why
vboxdrv setup:
* Stopping VirtualBox kernel modules
* Cannot unload module vboxpci
As it seems, that there is a bug in DKMS I uninstalled DKMS, purged Virtualbox and tried to reinstall:
Install:
Setting up virtualbox-4.1 (4.1.2-73507~Ubuntu~lucid) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
* Stopping VirtualBox kernel modules [ OK ]
* Uninstalling old VirtualBox DKMS kernel modules [ OK ]
* Removing old VirtualBox pci kernel module [ OK ]
* Trying to register the VirtualBox kernel modules using DKMS
* Failed, trying without DKMS
* Recompiling VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* modprobe vboxpci failed. Please use 'dmesg' to find out why
dmesg:
[ 203.601109] vboxdrv: Found 2 processor cores.
[ 203.601230] vboxdrv: fAsync=0 offMin=0x1e6 offMax=0x4101
[ 203.601292] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 203.601294] vboxdrv: Successfully loaded version 4.1.2 (interface 0x00190000).
[ 203.825653] BUG: unable to handle kernel paging request at 1ca622c0
[ 203.825775] IP: [<f8950101>] VBoxPciLinuxInit+0x101/0x1000 [vboxpci]
[ 203.825898] *pde = 00000000
[ 203.825953] Oops: 0002 [#1] SMP
[ 203.826016] Modules linked in: pci_stub vboxpci(+) vboxnetadp vboxnetflt vboxdrv parport_pc ppdev
dm_crypt arc4 snd_hda_codec_hdmi joydev snd_hda_codec_idt iwlagn mac80211 pcmcia cfg80211 snd_hda_intel
uvcvideo videodev yenta_socket pcmcia_rsrc sdhci_pci sdhci lp snd_hda_codec parport psmouse snd_hwdep
snd_pcm snd_timer snd pcmcia_core dell_laptop dell_wmi tpm_tis tpm tpm_bios soundcore snd_page_alloc
serio_raw dcdbas sparse_keymap usbhid hid i915 drm_kms_helper wmi drm ahci libahci i2c_algo_bit video e1000e
[ 203.826970]
[ 203.827001] Pid: 11180, comm: modprobe Not tainted 3.0.0-7-generic #9-Ubuntu Dell Inc. Latitude E6500 /0W612R
[ 203.827206] EIP: 0060:[<f8950101>] EFLAGS: 00010293 CPU: 0
[ 203.827307] EIP is at VBoxPciLinuxInit+0x101/0x1000 [vboxpci]
[ 203.827406] EAX: e9ac32c0 EBX: 00000000 ECX: 00000001 EDX: f908b145
[ 203.827513] ESI: f9001080 EDI: f908c214 EBP: eecc1f58 ESP: eecc1f44
[ 203.827620] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 203.827713] Process modprobe (pid: 11180, ti=eecc0000 task=f2dc7230 task.ti=eecc0000)
[ 203.827844] Stack:
[ 203.827880] 00000001 f908b13c 00000000 0000254a 00fce3a0 eecc1f88 c1001125 00000002
[ 203.828012] 00000000 00000000 00000000 f8951000 f8950000 00000000 f908c020 0000254a
[ 203.828012] 00fce3a0 eecc1fac c108262d 0000254a 00000000 4e4e8011 23a41acd 090a22a0
[ 203.828012] Call Trace:
[ 203.828012] [<c1001125>] do_one_initcall+0x35/0x170
[ 203.828012] [<f8950000>] ? 0xf894ffff
[ 203.828012] [<c108262d>] sys_init_module+0xad/0x210
[ 203.828012] [<c152bd34>] syscall_call+0x7/0xb
[ 203.828012] Code: 00 00 e8 c3 e4 70 c8 85 c0 75 69 b8 45 b1 08 f9 e8 65 e7 72 c8
85 c0 89 c6 a3 10 c2 08 f9 74 3e 83 38 02 74 63 8b 80 70 01 00 00
[ 203.828012] ff 00 a1 8c 32 7b c1 85 c0 74 1e 8b 1d 98 32 7b c1 85 db 74
[ 203.828012] EIP: [<f8950101>] VBoxPciLinuxInit+0x101/0x1000 [vboxpci] SS:ESP 0068:eecc1f44
[ 203.828012] CR2: 000000001ca622c0
[ 203.895011] ---[ end trace 431a05687b850c23 ]---
Any help would be appreciated!
Thanks,
Ali
Attachments (15)
Change History (35)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
| Description: | modified (diff) |
|---|
Please could you attach the compiled kernel modules?
comment:4 by , 13 years ago
Are these really the modules which resulted in the exact error message as described above?
comment:5 by , 13 years ago
Thanks for the fast reply Did some testing over the last few days, so maybe those aren't the correct ones - sorry for that, work distracted me from this... Will do a clean install and attach logs+modules in the next 30mins.
But the given case stays the same - modules can't be unloaded and so on...
Give me half an hour and I post a clean setup again.
comment:6 by , 13 years ago
So, here we go:
purged actual virtualbox-4.1 install vom repo removed installed dkms installed current virtualbox-4.1_4.1.2-73507~Ubuntu~lucid_i386
Setup:
sudo dpkg -i virtualbox-4.1_4.1.2-73507~Ubuntu~lucid_i386.deb Selecting previously deselected package virtualbox-4.1. (Reading database ... 120314 files and directories currently installed.) Unpacking virtualbox-4.1 (from virtualbox-4.1_4.1.2-73507~Ubuntu~lucid_i386.deb) ... Setting up virtualbox-4.1 (4.1.2-73507~Ubuntu~lucid) ... addgroup: The group `vboxusers' already exists as a system group. Exiting. * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules [ OK ] * Trying to register the VirtualBox kernel modules using DKMS * Failed, trying without DKMS * Recompiling VirtualBox kernel modules [ OK ] * Starting VirtualBox kernel modules * modprobe vboxpci failed. Please use 'dmesg' to find out why Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Processing triggers for shared-mime-info ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' Unknown media type in type 'fonts/package' Unknown media type in type 'interface/x-winamp-skin' Processing triggers for desktop-file-utils ... Processing triggers for hicolor-icon-theme ... Processing triggers for python-central ...
/var/log/messages, vbox-install.log and new kernel modules attached (will be right after this post)
Hm...hopefully nothing forgotten...
by , 13 years ago
| Attachment: | vboxnetadp.2.ko added |
|---|
/lib/modules/3.0.0-7-generic/misc/vboxnetadp.ko
by , 13 years ago
| Attachment: | vboxnetflt.2.ko added |
|---|
/lib/modules/3.0.0-7-generic/misc/vboxnetflt.ko
comment:7 by , 13 years ago
New modules and logs attached.
Decided to not overwrite already attached modules to differ from the new ones - couldn't decide, what would be more confusing...
comment:8 by , 13 years ago
Thanks. Still no idea what's exactly wrong. We fail when trying to lock the pci_stub module (in try_module_get().
comment:9 by , 13 years ago
Thanks
Is there a reason why the modules can't get unloaded?
vboxdrv setup:
sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules * Cannot unload module vboxpci
lsmod:
vboxpci 32348 1 [permanent] vboxnetadp 13328 0 [permanent] vboxnetflt 27252 0 [permanent] vboxdrv 251877 3 vboxpci,vboxnetadp,vboxnetflt,[permanent]
On my other machine they aren't loaded as permanent...?
comment:10 by , 13 years ago
This depends on the kernel configuration options. A configuration option is responsible for allowing kernel modules to be unloaded.
The vboxpci module cannot be unloaded because of the crash in the initialization function. A quick workaround would be to prevent loading of this module (edit the /etc/init.d/vboxdrv script). This module is only required if you plan to use PCI passthrough.
comment:11 by , 13 years ago
K, tried that. Took out everything vboxpci related from vboxdrv (check attached file) and deactivated the start routine in it, so modules won't get loaded permanent. Tried recompile and got an error (check 2nd vbox-install.log)
Did I do something wrong or isn't vboxpci the only module with problems?
by , 13 years ago
comment:13 by , 13 years ago
First I commented out every occurrence of vboxpci in vboxdrv, after that I had to temporarily put a "exit 0" on the beginning of the start-routine of vboxdrv, so I could restart with unloaded modules - else the other modules won't get unloaded aswell. After that I called /etc/init.d/vboxdrv setup, wich couldn't finish (see attached vbox-install.log)
Well, I didn't do more, so if you need more detailed information... ;)
comment:14 by , 13 years ago
I can confirm this bug is also affecting me. Running Bodhi Linux 1.1 (uses Ubuntu Lucid base) with kernel 3.0.0.7 from repository. Installed Virtualbox 4.1.2 from repository for the first time today (with dkms installed/in use).
by , 13 years ago
| Attachment: | vboxdmesg.txt added |
|---|
Relevant lines of dmesg output regarding unhandled paging request from fhteagle
comment:15 by , 13 years ago
Also tried with kernels 3.0.0.6 and 3.0.0.8 - no luck But as someone in the bodhi-linux forum pointed out, he runs VB4.1 just fine on 3.0.0.6
So don't know, what else is failing...
by , 13 years ago
by , 13 years ago
| Attachment: | vbox-install.3.log added |
|---|
comment:16 by , 13 years ago
Hi, I have the same issue with kernel 3.0.0-12-generic 20~lucid1build2-Ubuntu SMP
[ 18.862900] Oops: 0002 [#1] SMP [ 18.862927] Modules linked in: pci_stub vboxpci(+) vboxnetadp vboxnetflt vboxdrv parport_pc ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore psmouse snd_page_alloc serio_raw dcdbas lp parport radeon ttm usbhid hid drm_kms_helper drm tg3 i2c_algo_bit [ 18.863182] [ 18.863194] Pid: 1026, comm: modprobe Not tainted 3.0.0-12-generic #20~lucid1build2-Ubuntu Dell Inc. OptiPlex GX620 /0FH884 [ 18.863294] EIP: 0060:[<f81a6101>] EFLAGS: 00010293 CPU: 1 [ 18.863335] EIP is at VBoxPciLinuxInit+0x101/0x1000 [vboxpci] [ 18.863376] EAX: 00000000 EBX: 00000000 ECX: 00000001 EDX: f81a268f [ 18.863421] ESI: f813b080 EDI: f81a3214 EBP: f23d7f58 ESP: f23d7f44 [ 18.863465] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 18.863504] Process modprobe (pid: 1026, ti=f23d6000 task=f23f0000 task.ti=f23d6000) [ 18.863558] Stack: [ 18.863573] 00000001 f81a2686 00000000 f81a3020 080991c0 f23d7f88 c1001125 00000000 [ 18.863635] 00000000 f81a7000 f23d7f74 c107d36f f81a6000 00000000 0000246a f81a3020 [ 18.863696] 080991c0 f23d7fac c1082335 0000246a f23d7fac c11291a5 f2733c40 08099dc0 [ 18.863760] Call Trace: [ 18.863783] [<c1001125>] do_one_initcall+0x35/0x170 [ 18.863818] [<c107d36f>] ? set_page_attributes+0x1f/0x30 [ 18.863854] [<f81a6000>] ? 0xf81a5fff [ 18.863880] [<c1082335>] sys_init_module+0xb5/0x210 [ 18.863914] [<c11291a5>] ? sys_close+0x75/0xc0 [ 18.863945] [<c1523844>] syscall_call+0x7/0xb [ 18.863973] Code: 00 00 e8 43 7c eb c8 85 c0 75 5d b8 8f 26 1a f8 e8 95 8d ed c8 85 c0 89 c6 a3 10 32 1a f8 74 32 83 38 02 74 57 8b 80 78 01 00 00 [ 18.864143] ff 00 e9 00 00 00 00 eb 14 8b 43 04 b9 fb 60 1a f8 89 f2 ff [ 18.864223] EIP: [<f81a6101>] VBoxPciLinuxInit+0x101/0x1000 [vboxpci] SS:ESP 0068:f23d7f44 [ 18.864278] CR2: 00000000358a8000 [ 18.931356] ---[ end trace 83b122356efdaec8 ]---
dmesg and vbox-install.log are attached.
comment:17 by , 13 years ago
Also, when I try to run my virtual machine, kernel crashes:
[ 1157.420304] BUG: unable to handle kernel paging request at 357a8000 [ 1157.420376] IP: [<f81b47fa>] vboxNetFltOsInitInstance+0xca/0x110 [vboxnetflt] [ 1157.420452] *pde = 00000000 [ 1157.420482] Oops: 0002 [#2] SMP [ 1157.420517] Modules linked in: binfmt_misc pci_stub vboxpci(+) vboxnetadp vboxnetflt vboxdrv parport_pc ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore psmouse snd_page_alloc serio_raw dcdbas lp parport radeon ttm usbhid hid drm_kms_helper drm tg3 i2c_algo_bit [ 1157.420857] [ 1157.420874] Pid: 2234, comm: VirtualBox Tainted: G D 3.0.0-12-generic #20~lucid1build2-Ubuntu Dell Inc. OptiPlex GX620 /0FH884 [ 1157.424021] EIP: 0060:[<f81b47fa>] EFLAGS: 00210293 CPU: 0 [ 1157.424021] EIP is at vboxNetFltOsInitInstance+0xca/0x110 [vboxnetflt] [ 1157.424021] EAX: 00000000 EBX: ee351810 ECX: f234e800 EDX: 00000000 [ 1157.424021] ESI: ee351878 EDI: f81b81a0 EBP: ee2ddd64 ESP: ee2ddd50 [ 1157.424021] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 1157.424021] Process VirtualBox (pid: 2234, ti=ee2dc000 task=f6144c80 task.ti=ee2dc000) [ 1157.424021] Stack: [ 1157.424021] c106afe8 ee351868 ee351810 ee351810 f81b81a8 ee2ddd84 f81b4c4c f266c290 [ 1157.424021] f81b72ec 00000004 f23b4410 ee351c10 f8edec77 ee2dddf4 f8ec3e1f f81b81a8 [ 1157.424021] ee351ce0 f23b4410 00000000 f23b443c c10dfa61 000085f0 00000000 ee2ddf50 [ 1157.424021] Call Trace: [ 1157.424021] [<c106afe8>] ? up+0x28/0x40 [ 1157.424021] [<f81b4c4c>] vboxNetFltFactoryCreateAndConnect+0x21c/0x2c0 [vboxnetflt] [ 1157.424021] [<c10dfa61>] ? generic_file_buffered_write+0x51/0x80 [ 1157.424021] [<c152341d>] ? _raw_spin_lock+0xd/0x10 [ 1157.424021] [<f860ccb3>] ? rtR0MemAllocEx+0x43/0xc0 [vboxdrv] [ 1157.424021] [<c152341d>] ? _raw_spin_lock+0xd/0x10 [ 1157.424021] [<f860a582>] ? SUPSemEventCreate+0xa2/0x100 [vboxdrv] [ 1157.424021] [<c152341d>] ? _raw_spin_lock+0xd/0x10 [ 1157.424021] [<f8607278>] ? supdrvIOCtl+0x248/0x2a60 [vboxdrv] [ 1157.424021] [<f860ccb3>] ? rtR0MemAllocEx+0x43/0xc0 [vboxdrv] [ 1157.424021] [<c128dedd>] ? _copy_from_user+0x3d/0x130 [ 1157.424021] [<c10c5607>] ? stack_trace_call+0x157/0x190 [ 1157.424021] [<f86033bb>] ? VBoxDrvLinuxIOCtl+0xfb/0x1c0 [vboxdrv] [ 1157.424021] [<c10c5607>] ? stack_trace_call+0x157/0x190 [ 1157.424021] [<f86032c0>] ? SUPR0Printf+0x70/0x70 [vboxdrv] [ 1157.424021] [<c113ad56>] ? do_vfs_ioctl+0x86/0x2c0 [ 1157.424021] [<c113b007>] ? sys_ioctl+0x77/0x80 [ 1157.424021] [<c1523844>] ? syscall_call+0x7/0xb [ 1157.424021] [<c10c5607>] ? stack_trace_call+0x157/0x190 [ 1157.424021] [<c1520000>] ? longhaul_get_ranges+0x11c/0x2fa [ 1157.424021] Code: 04 c7 04 24 a4 72 1b f8 ff 92 14 c0 00 00 8b 45 f4 eb 8d 8d b6 00 00 00 00 83 3d 20 80 1b f8 02 0f 84 7a ff ff ff a1 98 81 1b f8 [ 1157.424021] ff 00 e9 00 00 00 00 31 c0 e9 66 ff ff ff 8b 1d 10 af 7a c1 [ 1157.424021] EIP: [<f81b47fa>] vboxNetFltOsInitInstance+0xca/0x110 [vboxnetflt] SS:ESP 0068:ee2ddd50 [ 1157.424021] CR2: 00000000357a8000 [ 1157.532170] ---[ end trace 83b122356efdaec9 ]---
comment:18 by , 13 years ago
relgames, please could you attach your vboxnetflt.ko module to this ticket?
comment:19 by , 12 years ago
Ubuntu package bug, see #9891! Please complain with the Ubuntu package maintainer!
comment:20 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Btw: Sorry, had to copy/paste my logs out of posting, as I didn't want to do the whole procedure with 2 different kernels with/-out DKMS and 2 different virtualbox versions.
Sorry for that :(