From owner-freebsd-current@FreeBSD.ORG  Tue Jul 30 16:18:41 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 04C54F55;
 Tue, 30 Jul 2013 16:18:41 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C77F22D52;
 Tue, 30 Jul 2013 16:18:40 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 669E3B977;
 Tue, 30 Jul 2013 12:18:36 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Subject: Re: Fwd: Problem with curret in vmware
Date: Tue, 30 Jul 2013 11:55:51 -0400
User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p28; KDE/4.5.5; amd64; ; )
References: <CAPJF9wkLe+R2tJ6ej1guzCARQ1OF0RWFzX_qUQam6+XOZjyF9A@mail.gmail.com>
 <CAPJF9wkVjA4McyFhm7Ys-Kd9kYxOREbkYGnDDgMiR0ASCVJeQA@mail.gmail.com>
In-Reply-To: <CAPJF9wkVjA4McyFhm7Ys-Kd9kYxOREbkYGnDDgMiR0ASCVJeQA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201307301155.51473.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Tue, 30 Jul 2013 12:18:36 -0400 (EDT)
Cc: Attilio Rao <attilio@freebsd.org>, Alexander Yerenkow <yerenkow@gmail.com>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 16:18:41 -0000

On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote:
> Hello all.
> I have panics in vmware with installed vmwaretools (they are guessed
> culprit).
> Seems that memory balooning (or using more memory in all vms than there is
> in host)
> produces some kind of weird behavior in FreeBSD.
> This vm aren't shutted down now, is there somethin I can do to help
> investigate this?
> 
> Panic screens:
> http://gits.kiev.ua/FreeBSD/panic1.png
> http://gits.kiev.ua/FreeBSD/panic2.png

Looks like their code needs to be updated to work with locking changes in
HEAD.  Attilio is probably the best person to ask.

-- 
John Baldwin