| Summary: | emulators/virtualbox-ose-kmod: kernel panic on boot in 10.2-PRERELEASE (10/stable) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Tony Narlock <tony> | ||||
| Component: | Individual Port(s) | Assignee: | Virtualbox Team (Nobody) <vbox> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Only Me | CC: | pavlos, rainbow, w.schwarzenfeld | ||||
| Priority: | --- | Keywords: | crash | ||||
| Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(vbox) |
||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
have you tried to rebuild kmod from ports? I remember the "same" error.. Can someone change the version this to 10-stable? I also get this on FreeBSD 9.3 with virbualbox-ose 4.3.34 (after upgrading from 4.3.24). In my case the kernel modules seem to be loading fine (vboxdrv.ko, vboxnetflt.ko and vboxnetadp.ko). So with vboxnet_enable="YES" the system boots properly. The kernel panic is caused when I add the vboxheadless_enable="YES" to rc.conf. Or if I try to start the VMs manually after booting. So it seems that the panic is caused when the VMs are starting. In the kernel panic output I also saw the "spinlock held too long" message. VBox version is at 5.2.4. 9.3 and 10.2 are gone. This is overcome by events. |
Created attachment 157972 [details] Screenshot of error VBoxDrvFreeBSDModuleEvent causes kernel panic on boot stable/10 - r281836 virtualbox-ose-kmod-4.3.28 This kernel panic isn't producing a crash core file. I can work around this temporarily by disabling `vboxdrv_load="YES"` inside /boot/loader.conf What can I do to give better debug info?