From owner-freebsd-bugs Thu Nov 15 12: 6:36 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 EE8B537B420; Thu, 15 Nov 2001 12:06:31 -0800 (PST) Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106]) by yertle.kciLink.com (Postfix) with ESMTP id 466FC1E985; Thu, 15 Nov 2001 15:06:31 -0500 (EST) Received: (from khera@localhost) by onceler.kciLink.com (8.11.6/8.11.6) id fAFK6Vb79779; Thu, 15 Nov 2001 15:06:31 -0500 (EST) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15348.8263.120049.16709@onceler.kciLink.com> Date: Thu, 15 Nov 2001 15:06:31 -0500 To: Cc: freebsd-bugs@FreeBSD.org Subject: Re: ports/20624: vmware vmmon module locks kernel In-Reply-To: <200111151953.fAFJrGt49862@freefall.freebsd.org> References: <200111151953.fAFJrGt49862@freefall.freebsd.org> X-Mailer: VM 6.96 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 >>>>> "a" == asmodai writes: I think vmware should just be marked broken so it doesn't harm other people, as it does lock up the kernel hard. Personally, I use vmware2 and will use vmware3 when it gets ported. Thaks for the followup. a> Synopsis: vmware vmmon module locks kernel a> State-Changed-From-To: open->closed a> State-Changed-By: asmodai a> State-Changed-When: Thu Nov 15 11:51:46 PST 2001 a> State-Changed-Why: a> Sorry, but with 3.0 being imminent or already released I see little a> use in trying to still try to support 1.x of VMWare, so much a> progress gets made in the application itself. a> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20624 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message