From owner-freebsd-ports@FreeBSD.ORG Mon Mar 25 00:03:52 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C982D7BA; Mon, 25 Mar 2013 00:03:52 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from fsm1.ukr.net (fsm1.ukr.net [195.214.192.120]) by mx1.freebsd.org (Postfix) with ESMTP id 7F939D0D; Mon, 25 Mar 2013 00:03:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=SdweTkZgTVsakIWN4p9kGkhl6CXaqwfrw4oZ5lKOFFc=; b=HgHwOuO5U0QZfx5VVlJbLkza6a3zRzL+yYYeo3odYpD6HAVMQ6N5VlINpe2H6VmXv6VdXjIBcM7/NarYg6mbSdNnUPj3hjx646Bh9mSdlYhEO5cQN68/XqRjSpoOlogrgfjaEZr8ogV6Lfd64k6WWipm6TZ6Rs5r3LxP1kzuuJg=; Received: from [178.137.138.140] (helo=nonamehost) by fsm1.ukr.net with esmtpsa ID 1UJut3-000Hy4-GY ; Mon, 25 Mar 2013 02:03:41 +0200 Date: Mon, 25 Mar 2013 02:03:40 +0200 From: Ivan Klymenko To: Konstantin Belousov Subject: Re: Kernel panic CURRENT r248596 at virtualbox-ose-kmod module load Message-ID: <20130325020340.02c5ace0@nonamehost> In-Reply-To: <20130324120507.GX3794@kib.kiev.ua> References: <20130323132627.04bf7ef4@nonamehost> <20130324120507.GX3794@kib.kiev.ua> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; amd64-portbld-freebsd10.0) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2013 00:03:52 -0000 =D0=92 Sun, 24 Mar 2013 14:05:07 +0200 Konstantin Belousov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > 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@nonamehost:/usr/obj/usr/src/sys/GENERIC amd64 > >=20 > > I updated the ports tree to r314921 and recompiled > > virtualbox-ose-kmod > >=20 > > After load the module a have kernel panic. > >=20 > > Panic String: Lock vm object not exclusively locked @ > > /usr/src/sys/vm/vm_page.c:1396 > >=20 > > http://pkgupdate.nevosoft.ru/backtrace.txt >=20 > This looks like a vbox issue, the driver did not properly locked > the object passed to the vm_page_alloc_contig(). >=20 > 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/pa= tch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_OBJECT_RENAME.c?= r1=3D314794&r2=3D314796 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.