Re: Kernel panic CURRENT r248596 at virtualbox-ose-kmod module load

В Sun, 24 Mar 2013 14:05:07 +0200
Konstantin Belousov <kostikbel_at_gmail.com> пишет:

> On Sat, Mar 23, 2013 at 01:26:27PM +0200, Ivan Klymenko wrote:
> > I have
> > uname -a
> > FreeBSD nonamehost 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248596: Fri
> > Mar 22 01:17:08 EET 2013
> > ivan_at_nonamehost:/usr/obj/usr/src/sys/GENERIC  amd64
> > 
> > I updated the ports tree to r314921 and recompiled
> > virtualbox-ose-kmod
> > 
> > After load the module a have kernel panic.
> > 
> > Panic  String:  Lock  vm  object  not  exclusively   locked   _at_
> > /usr/src/sys/vm/vm_page.c:1396
> > 
> > http://pkgupdate.nevosoft.ru/backtrace.txt
> 
> This looks like a vbox issue, the driver did not properly locked
> the object passed to the vm_page_alloc_contig().
> 
> If you want this fixed, you probably need to look up the code
> yourself, compiling the vbox kld with debugging, finding the
> offending call to vm_page_alloc_contig() and looking around it to see
> which object is passed and why it is not locked.

The problem is that port commiter did not listen your advice:
http://docs.freebsd.org/cgi/mid.cgi?20130312151751.GJ3794

and used in the patch is not the functions that need
http://svnweb.freebsd.org/ports/head/emulators/virtualbox-ose-kmod/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_OBJECT_RENAME.c?r1=314794&r2=314796

I replaced the all function "VM_OBJECT_RLOCK" on "VM_OBJECT_WLOCK"
and
"VM_OBJECT_RUNLOCK" on "VM_OBJECT_WUNLOCK"

and the kernel panic ceased.

Thanks. This problem is solved.