From owner-freebsd-bugs Mon Aug 27 9: 8:15 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by hub.freebsd.org (Postfix) with ESMTP id C4BC337B401; Mon, 27 Aug 2001 09:08:12 -0700 (PDT) (envelope-from khera@kciLink.com) Received: by yertle.kciLink.com (Postfix, from userid 100) id 4B8DE2E45F; Mon, 27 Aug 2001 12:08:07 -0400 (EDT) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15242.28775.134215.950323@yertle.kciLink.com> Date: Mon, 27 Aug 2001 12:08:07 -0400 To: 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> X-Mailer: VM 6.92 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> "i" == iedowse 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message