From owner-freebsd-bugs@FreeBSD.ORG Thu Dec 22 08:10:12 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F212E106564A for ; Thu, 22 Dec 2011 08:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DC58C8FC0C for ; Thu, 22 Dec 2011 08:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBM8ACHY061567 for ; Thu, 22 Dec 2011 08:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBM8ACJS061566; Thu, 22 Dec 2011 08:10:12 GMT (envelope-from gnats) Date: Thu, 22 Dec 2011 08:10:12 GMT Message-Id: <201112220810.pBM8ACJS061566@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Oleg Ginzburg Cc: Subject: Re: kern/163493: FreeBSD 9x amd64 unstable while work with RAM X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oleg Ginzburg List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2011 08:10:13 -0000 The following reply was made to PR kern/163493; it has been noted by GNATS. From: Oleg Ginzburg To: bug-followup@freebsd.org, olevole@olevole.ru Cc: Subject: Re: kern/163493: FreeBSD 9x amd64 unstable while work with RAM Date: Thu, 22 Dec 2011 11:37:07 +0400 Update: The described case for the physical machine is ZFS-related. It is reproduced at ZFS Volume-based swap: (for example - da0 is empty disk): kldload zfs echo 'zfs_load="YES"' >> /etc/rc.conf zpool create swp /dev/da0 zfs create -V 4G swp/swap zfs set org.freebsd:swap=on zwp/swap zfs set checksum=off swp/swap service zfs restart service zvol restart then repeat actions from How-to-repeat For VirtualBox a case - problems arise without ZFS. It seems, it is related with inheritance kmem\* or other parameters from the master host