Vboxdrv and custom kernel on slackware 14
First, vboxdrv (and the whole virtualbox system) works flawless on the 3.2.29 (hugesmp.s) kernel shipped with slackware 14.
However, I cannot manage to run several version of virtualbox (4.0, 4.1, latest: 4.2) on custom kernel, including the following: 3.2.30, 3.4.11, 3.5.4 and (surprise, surprise) the 3.2.29, which is exactly the same version shipped with s14. Each time I run into the following kernel panic:
Quote:
Oct 1 23:01:26 chives kernel: IP: [<f8a66702>] VBoxHost_RTR0MemObjFree+0x294/0x294 [vboxdrv]
Oct 1 23:01:26 chives kernel: Modules linked in: vboxdrv(O+) snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss usb_storage iwl3945 iwl_legacy fbcon snd_hda_codec_idt i915 mac80211 cfbfillrect cfbimgblt bitblit snd_hda_intel snd_hda_codec snd_hwdep snd_pcm video softcursor font cfg80211 cfbcopyarea i2c_algo_bit snd_page_alloc drm_kms_helper firewire_ohci snd_timer sony_laptop drm firewire_core snd rfkill sky2 intel_agp intel_gtt agpgart soundcore backlight loop
Oct 1 23:01:26 chives kernel: EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv]
Oct 1 23:01:26 chives kernel: [<f8a5f08e>] ? supdrvInitDevExt+0x103/0x69e [vboxdrv]
Oct 1 23:01:26 chives kernel: [<f8a66fa7>] ? rtR0MemAllocEx+0x4a/0x9d [vboxdrv]
Oct 1 23:01:26 chives kernel: [<f8a65829>] ? VBoxHost_RTMemAllocTag+0xe/0x22 [vboxdrv]
Oct 1 23:01:26 chives kernel: [<f8a6946a>] ? VBoxHost_RTSpinlockCreate+0x1b/0x4f [vboxdrv]
Oct 1 23:01:26 chives kernel: [<f8a66d83>] ? rtR0PowerNotificationInit+0x11/0x15 [vboxdrv]
Oct 1 23:01:26 chives kernel: [<f8841050>] ? VBoxDrvLinuxInit+0x50/0xc7 [vboxdrv]
Oct 1 23:01:26 chives kernel: EIP: [<f8a66702>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] SS:ESP 0068:e043dea0
Oct 1 23:03:59 chives kernel: IP: [<f904a702>] VBoxHost_RTR0MemObjFree+0x294/0x294 [vboxdrv]
Oct 1 23:03:59 chives kernel: Modules linked in: vboxdrv(O+) snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss usb_storage fbcon bitblit softcursor font i915 cfbfillrect cfbimgblt video cfbcopyarea i2c_algo_bit drm_kms_helper drm intel_agp intel_gtt agpgart iwl3945 iwl_legacy mac80211 snd_hda_codec_idt sky2 firewire_ohci snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer cfg80211 snd sony_laptop firewire_core backlight soundcore rfkill loop
Oct 1 23:03:59 chives kernel: EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv]
Oct 1 23:03:59 chives kernel: [<f904308e>] ? supdrvInitDevExt+0x103/0x69e [vboxdrv]
Oct 1 23:03:59 chives kernel: [<f904afa7>] ? rtR0MemAllocEx+0x4a/0x9d [vboxdrv]
Oct 1 23:03:59 chives kernel: [<f9049829>] ? VBoxHost_RTMemAllocTag+0xe/0x22 [vboxdrv]
Oct 1 23:03:59 chives kernel: [<f904d46a>] ? VBoxHost_RTSpinlockCreate+0x1b/0x4f [vboxdrv]
Oct 1 23:03:59 chives kernel: [<f904ad83>] ? rtR0PowerNotificationInit+0x11/0x15 [vboxdrv]
Oct 1 23:03:59 chives kernel: [<f8976050>] ? VBoxDrvLinuxInit+0x50/0xc7 [vboxdrv]
Oct 1 23:03:59 chives kernel: EIP: [<f904a702>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x0/0x67 [vboxdrv] SS:ESP 0068:f2dd7ea0
|
either when modprobing the virtualbox or when running a virtual machine. It sounds really strange to me that this happens with several versions of the kernel - it may depend on some modules or features I have configured in the kernel, but which? I do not have an exotic kernel configuration, just the classical things you encounter on an ICH7 sony vaio notebook. I can also attach the .config file if it is needed.
Any hints? |
