[Bug 238463] emulators/virtualbox-ose Fatal trap 12

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238463

            Bug ID: 238463
           Summary: emulators/virtualbox-ose Fatal trap 12
           Product: Ports & Packages
           Version: Latest
          Hardware: i386
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: vbox at FreeBSD.org
          Reporter: nostoc at live.ru
          Assignee: vbox at FreeBSD.org
             Flags: maintainer-feedback?(vbox at FreeBSD.org)

Created attachment 204955
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=204955&action=edit
Virtual machine

Overview: Fatal trap 12 and therefore kernel panic with hard reboots when
powering on any VM using VirtualBox OSE

Steps to Reproduce:

% uname -a
FreeBSD fbsd.gf4 12.0-RELEASE-p5 FreeBSD 12.0-RELEASE-p5 GENERIC  i386

% pkg info -x virtualbox
virtualbox-ose-5.2.26_3
virtualbox-ose-kmod-5.2.26

% virtualbox

Then create a virtual machine with any configuration (I even trying to create a
VM absolutely with no features) and start it. The VM is attached. No logs of
VBox are found in  the appropriate files.

Actual Results: hard reboot.
savecored vmcore.2 is available in my OneDrive (>195M) -
https://1drv.ms/u/s!ArE46lxEOnviizNQfyJvEuOdes0z?e=sNchgj.

Unlike bug #181818, the kernel panics when starting the VM, not the VirtualBox
manager.

Expected Results: VM started. I have had to use VirtualBox very actively on the
same PC (unchanged, except PSU) from two to four years ago.

coreinfo wasn't worked out:

cat -n /var/crash/core.txt.2 
     1  BFD: /boot/kernel/kernel: invalid relocation type 42
     2  BFD: /boot/kernel/kernel: invalid relocation type 42
     3  BFD: /boot/kernel/kernel: invalid relocation type 42
     4  /dev/stdin:1: Error in sourced command file:
     5  Cannot access memory at address 0x65657246
     6  BFD: /boot/kernel/kernel: invalid relocation type 42
     7  BFD: /boot/kernel/kernel: invalid relocation type 42
     8  BFD: /boot/kernel/kernel: invalid relocation type 42
     9  /dev/stdin:1: Error in sourced command file:
    10  Cannot access memory at address 0x65657246
    11  BFD: /boot/kernel.old1/kernel: invalid relocation type 42
    12  BFD: /boot/kernel.old1/kernel: invalid relocation type 42
    13  BFD: /boot/kernel.old1/kernel: invalid relocation type 42
    14  /dev/stdin:1: Error in sourced command file:
    15  Cannot access memory at address 0x65657246
    16  Unable to find matching kernel for /var/crash/vmcore.2

I already tried to load/unload vboxdrv and vboxnet.

Speculation possible, but it may be related with the fact that my videocard has
been moved to supporting via legacy nvidia-340 driver (this is not correlated
with the official nvidia information at the site, but I having a lot of
troubles to set my card working). My box is from year 2012 (quite old as you
can see).

-- 
You are receiving this mail because:
You are the assignee for the bug.