From owner-freebsd-bugs  Mon Aug 27 13: 0: 6 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 8E37637B409
	for <freebsd-bugs@hub.freebsd.org>; Mon, 27 Aug 2001 13:00:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.4/8.11.4) id f7RK02p55076;
	Mon, 27 Aug 2001 13:00:02 -0700 (PDT)
	(envelope-from gnats)
Date: Mon, 27 Aug 2001 13:00:02 -0700 (PDT)
Message-Id: <200108272000.f7RK02p55076@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Ian Dowse <iedowse@maths.tcd.ie>
Subject: Re: ports/20624: vmware vmmon module locks kernel
Reply-To: Ian Dowse <iedowse@maths.tcd.ie>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR ports/20624; it has been noted by GNATS.

From: Ian Dowse <iedowse@maths.tcd.ie>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: ports/20624: vmware vmmon module locks kernel
Date: Mon, 27 Aug 2001 20:55:31 +0100

 Adding this to the audit-trail.
 
 ------- Forwarded Message
 
 From: Vivek Khera <khera@kcilink.com>
 Message-ID: <15242.28775.134215.950323@yertle.kciLink.com>
 Date: Mon, 27 Aug 2001 12:08:07 -0400
 To: iedowse@FreeBSD.org
 Cc: freebsd-bugs@FreeBSD.org
 Subject: Re: ports/20624: vmware vmmon module locks kernel
 In-Reply-To: <200108252324.f7PNOk661343@freefall.freebsd.org>
 References: <200108252324.f7PNOk661343@freefall.freebsd.org>
 
 >>>>> "i" == iedowse  <iedowse@FreeBSD.org> writes:
 
 i> Does this problem still exist?
 i> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20624
 
 I don't know.  I bit the bullet and upgraded to a vmware 2.0 license.
 But unless the vmware1 FreeBSD kernel modules have been updated, I
 don't see that the problem would go away magically ;-)
 
 I think if the vmware1 port's modules were retrofitted with the
 kernel modules from vmware2, it would work, as per one of my earlier
 messages.
 
 So, basically, I don't know if the problem still persists with
 vmware1.
 
 ------- End of Forwarded Message
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message