virtualbox status on 8.0-STABLE i386

Mikolaj Golub to.my.trociny at gmail.com
Mon Mar 8 08:33:57 UTC 2010


On Sun, 07 Mar 2010 15:28:48 +0100 Alexander Eichner wrote:

> Hi,
>
> can you try the attached patch please?
> This should fix the panic you encountered. Please undo your kernel
> changes befoer testing.

Unfortunately, the same panic:

(kgdb) bt
#0  doadump () at pcpu.h:246
#1  0xc04ec379 in db_fncall (dummy1=-1064468854, dummy2=0, dummy3=-1, dummy4=0xe866b5b4 "х╣fХ")
    at /usr/src/sys/ddb/db_command.c:548
#2  0xc04ec7af in db_command (last_cmdp=0xc0e04c9c, cmd_table=0x0, dopager=0)
    at /usr/src/sys/ddb/db_command.c:445
#3  0xc04ec864 in db_command_script (command=0xc0e05bc4 "call doadump")
    at /usr/src/sys/ddb/db_command.c:516
#4  0xc04f09a0 in db_script_exec (scriptname=0xe866b6c0 "kdb.enter.panic", warnifnotfound=Variable "warnifnotfound" is not available.
)
    at /usr/src/sys/ddb/db_script.c:302
#5  0xc04f0a87 in db_script_kdbenter (eventname=0xc0cc246d "panic") at /usr/src/sys/ddb/db_script.c:324
#6  0xc04ee768 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:228
#7  0xc08d7d06 in kdb_trap (type=3, code=0, tf=0xe866b7fc) at /usr/src/sys/kern/subr_kdb.c:535
#8  0xc0beb38b in trap (frame=0xe866b7fc) at /usr/src/sys/i386/i386/trap.c:690
#9  0xc0bcccfb in calltrap () at /usr/src/sys/i386/i386/exception.s:165
#10 0xc08d7e8a in kdb_enter (why=0xc0cc246d "panic", msg=0xc0cc246d "panic") at cpufunc.h:71
#11 0xc08a88b6 in panic (fmt=0xc0cecba4 "vm_fault: fault on nofault entry, addr: %lx")
    at /usr/src/sys/kern/kern_shutdown.c:562
#12 0xc0b0c3c7 in vm_fault (map=0xc1990000, vaddr=3244318720, fault_type=Variable "fault_type" is not available.
)
    at /usr/src/sys/vm/vm_fault.c:283
#13 0xc0bea7c6 in trap_pfault (frame=0xe866bab8, usermode=0, eva=3244322776)
    at /usr/src/sys/i386/i386/trap.c:840
#14 0xc0beb215 in trap (frame=0xe866bab8) at /usr/src/sys/i386/i386/trap.c:533
#15 0xc0bcccfb in calltrap () at /usr/src/sys/i386/i386/exception.s:165
#16 0xc12beef3 in rtR0MemObjNativeGetPagePhysAddr () from /boot/modules/vboxdrv.ko
#17 0xc12ac374 in SUPR0LockMem () from /boot/modules/vboxdrv.ko
#18 0xc12ac8eb in supdrvIOCtl () from /boot/modules/vboxdrv.ko
#19 0xc12b0c5a in VBoxDrvFreeBSDIOCtl () from /boot/modules/vboxdrv.ko
#20 0xc0829658 in devfs_ioctl_f (fp=0xc5f1c8c0, com=3321378576, data=0xe866bd00, cred=0xc6972a00, 
    td=0xc728e250) at /usr/src/sys/fs/devfs/devfs_vnops.c:659
#21 0xc08eec8d in kern_ioctl (td=0xc728e250, fd=7, com=536892942, 
    data=0xe866bd00 "@г\023)Ь\023Эю8╫fХЬ\023Эю,╫fХ\005\\╫ю\001") at file.h:262
#22 0xc08eee14 in ioctl (td=0xc728e250, uap=0xe866bcf8) at /usr/src/sys/kern/sys_generic.c:678
#23 0xc0beaac0 in syscall (frame=0xe866bd38) at /usr/src/sys/i386/i386/trap.c:1111
#24 0xc0bccd90 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:261
#25 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)

(this time I built the modules without debugging symbols).

Just to be sure that I did all thing properly below the steps I did:

1) returned original pmap.h (with KPTmap), rebuilt the kernel and rebooted
2) rebuilt with the patch virtualbox drivers and virtualbox (not sure this last was 
   needed bu just in case...):
     cd emulators/virtualbox-ose-kmod && make patch
     applied this patch and your previous patch ("Patch to fix VirtualBox with recent kernel versions")
     built and reinstall
     the same for emulators/virtualbox-ose
3) rebooted and started vm guest

virtualbox-ose-3.1.2_1 A general-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-3.1.2_1 VirtualBox kernel module for FreeBSD

-- 
Mikolaj Golub


More information about the freebsd-emulation mailing list