Re: Panic when loading vboxdrv module

From: Randy Westlund <rwestlun_at_gmail.com>
Date: Mon, 25 Jul 2016 17:17:41 -0400
On Mon, Jul 25, 2016 at 04:09:58PM -0400, Jung-uk Kim wrote:
> If you feel adventurous, please drop the attached patch in
> *emulators/virtualbox-ose/files* directory, and rebuild
> *emulators/virtualbox-ose-kmod*.
> 
> JK
> 
> * Note the patch directory is emulators/virtualbox-ose/files, not
> emulators/virtualbox-ose-kmod/files.

> --- src/VBox/HostDrivers/Support/SUPDrvInternal.h.orig	2016-07-18 11:56:19 UTC
> +++ src/VBox/HostDrivers/Support/SUPDrvInternal.h
> _at__at_ -235,7 +235,7 _at__at_
>  # define SUPDRV_WITHOUT_MSR_PROBER
>  #endif
>  
> -#if 1
> +#if 0
>  /** _at_def SUPDRV_USE_TSC_DELTA_THREAD
>   * Use a dedicated kernel thread to service TSC-delta measurement requests.
>   * _at_todo Test on servers with many CPUs and sockets. */

With the patch, vboxdrv loads successfully.  But when I start a VM, I
get the following panic (after rebuilding virtualbox-ose as well):

> vboxdrv: ffffffff82973020 VMMR0.r0
> vboxdrv: ffffffff82a92020 VBoxDDR0.r0
> vboxdrv: ffffffff82aaf020 VBoxDD2R0.r0
> panic: _mtx_lock_sleep: recursed on non-recursive mutex aiomtx _at_ /usr/src/sys/kern/vfs_aio.c:996
> 
> cpuid = 1
> KBD: stack backtrace:
> db_trace_wrapper() at db_trace_wrapper+0x2b
> vpanic() at vpanic+0x182
> kassert_panic() at kassert_panic+0x126
> __mtx_lock_sleep() at __mtx_lock_sleep+0x228
> __mtx_lock_flags() at __mtx_lock_flags+0x10d
> aio_queue() at aio_queue+0x9d6
> amd64_syscall() at amd64_syscall+0x2db
> Xfast_syscall() at Xfast_syscall+0xfb
> --- syscall (465, FreeBSD ELF64, sys_aio_fsync), rip = 0x80119fa0a, rsp = 0x7fffdf2abc98, rbp = 0x7fffdf2abcd0 ---
> KDB: enter: panic
> [ thread pid 14588 tid 101813 ]
> Stopped at      kdb_enter+0x3b: movq    $0,kdb_why




Received on Mon Jul 25 2016 - 19:17:45 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:07 UTC