Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Dec 2020 17:10:54 +0000
From:      Gary Palmer <gpalmer@freebsd.org>
Cc:        vbox@freebsd.org
Subject:   Re: Crash on 12.2 with virtualbox-ose-kmod
Message-ID:  <X940HrTs%2BFMD3npl@in-addr.com>
In-Reply-To: <X94iR9CNgwlgBBkg@in-addr.com>
References:  <X94iR9CNgwlgBBkg@in-addr.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 19, 2020 at 03:54:47PM +0000, Gary Palmer wrote:
> Hi,
> 
> I just upgraded from 11.4 to 12.2 and now every time I start virtualbox GUI
> my box kernel panics.  Before everyone screams "install new kernel moudle",
> I did that already
> 
> % pkg info virtualbox-ose-kmod | grep -i arch
> Architecture   : FreeBSD:12:amd64
> 
> In fact recompiled it today in case that was the problem
> 
> The backtrace from core.txt is:
> 
> #0  doadump () at src/sys/amd64/include/pcpu_aux.h:55
> 55              __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct pcpu,
> (kgdb) #0  doadump () at src/sys/amd64/include/pcpu_aux.h:55
> #1  0xffffffff80bbe7b5 in kern_reboot (howto=260)
>     at /usr/src/sys/kern/kern_shutdown.c:451
> #2  0xffffffff80bbebf3 in vpanic (fmt=<value optimized out>, 
>     ap=<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:880
> #3  0xffffffff80bbea13 in panic (fmt=<value optimized out>)
>     at /usr/src/sys/kern/kern_shutdown.c:807
> #4  0xffffffff8108f911 in trap_fatal (frame=<value optimized out>, 
>     eva=<value optimized out>) at /usr/src/sys/amd64/amd64/trap.c:921
> #5  0xffffffff8108f96f in trap_pfault (frame=0xfffffe00fd135650, 
>     usermode=<value optimized out>, signo=<value optimized out>, 
>     ucode=<value optimized out>) at src/sys/amd64/include/pcpu_aux.h:55
> #6  0xffffffff8108efb6 in trap (frame=0xfffffe00fd135650)
>     at /usr/src/sys/amd64/amd64/trap.c:405
> #7  0xffffffff81066f68 in calltrap ()
>     at /usr/src/sys/amd64/amd64/exception.S:289
> #8  0xffffffff80cb787a in if_alloc (type=6 '\006') at /usr/src/sys/net/if.c:384
> #9  0xffffffff83f5e02a in vboxNetAdpOsCreate ()
>    from /boot/modules/vboxnetadp.ko
> #10 0xffffffff83f5e619 in vboxNetAdpCreate () from /boot/modules/vboxnetadp.ko
> #11 0xffffffff83f5e4f6 in VBoxNetAdpFreeBSDCtrlioctl ()
>    from /boot/modules/vboxnetadp.ko
> #12 0xffffffff80a79130 in devfs_ioctl (ap=<value optimized out>)
>     at /usr/src/sys/fs/devfs/devfs_vnops.c:797
> #13 0xffffffff8124722b in VOP_IOCTL_APV (vop=0xffffffff81af67d0, 
>     a=0xfffffe00fd135878) at vnode_if.c:1067
> #14 0xffffffff80c9ca6a in vn_ioctl (fp=0xfffff800116d5f50, 
>     com=<value optimized out>, data=0xfffffe00fd135a10, 
>     active_cred=0xfffff80182dce400, td=<value optimized out>) at vnode_if.h:882
> #15 0xffffffff80a7971e in devfs_ioctl_f (fp=<value optimized out>, 
>     com=<value optimized out>, data=<value optimized out>, 
>     cred=<value optimized out>, td=0xfffff8021fbd4740)
>     at /usr/src/sys/fs/devfs/devfs_vnops.c:755
> #16 0xffffffff80c28697 in kern_ioctl (td=<value optimized out>, 
>     fd=<value optimized out>, com=3223352833, data=<value optimized out>)
>     at src/sys/sys/file.h:337
> #17 0xffffffff80c2833a in sys_ioctl (td=0xfffff8021fbd4740, 
>     uap=0xfffff8021fbd4b00) at /usr/src/sys/kern/sys_generic.c:713
> #18 0xffffffff810904c7 in amd64_syscall (td=0xfffff8021fbd4740, traced=0)
>     at src/sys/amd64/amd64/../../kern/subr_syscall.c:144
> #19 0xffffffff8106788e in fast_syscall_common ()
>     at /usr/src/sys/amd64/amd64/exception.S:582
> #20 0x000000080056763a in ?? ()
> Previous frame inner to this frame (corrupt stack?)
> 
> 
> I tried "vboxmanage list vms" from my account on the console, which
> caused the crash.  If I try it from an acocunt which has no VMs
> then it doesn't cause a crash, so it looks like something in one of my
> VMs is causing the issue.  Figuring out which one is causing the issue
> could be problematic.
> 
> I also compiled a GENERIC kernel to see if that would help, it did not.
> My src.conf is pretty bare - just turns off sendmail, NIS, IPX and
> SHAREDOCS.


OK, seems I got bitten by the upgrade.  Even though I had recompiled
everything I had not checked the VIMAGE option in virtualbox-ose-kmod

Checked that option, recompiled the kmod, did "service vboxnet stop"
followed by "service vboxnet start" and no more crashes

Sorry for the noise

Regards,

Gary



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X940HrTs%2BFMD3npl>