From khera@onceler.kciLink.com  Tue Aug 15 12:45:09 2000
Return-Path: <khera@onceler.kciLink.com>
Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2])
	by hub.freebsd.org (Postfix) with ESMTP id 4ADF937B9A0
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 15 Aug 2000 12:45:07 -0700 (PDT)
	(envelope-from khera@onceler.kciLink.com)
Received: (from khera@localhost)
	by onceler.kciLink.com (8.9.3/8.9.3) id PAA00584;
	Tue, 15 Aug 2000 15:45:01 -0400 (EDT)
	(envelope-from khera)
Message-Id: <200008151945.PAA00584@onceler.kciLink.com>
Date: Tue, 15 Aug 2000 15:45:01 -0400 (EDT)
From: Vivek Khera <khera@onceler.kciLink.com>
Reply-To: khera@onceler.kciLink.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: vmware port locks kernel when vmmon module loaded
X-Send-Pr-Version: 3.2

>Number:         20624
>Category:       ports
>Synopsis:       vmware vmmon module locks kernel
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 15 12:50:02 PDT 2000
>Closed-Date:    Thu Nov 15 11:51:46 PST 2001
>Last-Modified:  Thu Nov 15 11:53:16 PST 2001
>Originator:     Vivek Khera
>Release:        FreeBSD 4.1-STABLE i386
>Organization:
>Environment:

	
4.1S as of Aug 14.

>Description:

	
the vmware "vmmon" kernel module when loaded locks the kernel hard.
not even the keyboard is processed (caps lock non-functional).

once the module is loaded, the last thing the syslog gets is this line:

/kernel: /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-364 $

>How-To-Repeat:

	
cd /usr/ports/vmware
make extract
pushd work/vmware-distrib/vmnet-only/freebsd
apply this patch:

--- #vmnet.c~   Tue Aug 15 15:14:33 2000
+++ vmnet.c     Tue Aug 15 15:14:33 2000
@@ -153,7 +153,7 @@
 
        s = splimp();
        if_attach(ifp);
-       ether_ifattach(ifp);
+       ether_ifattach(ifp,0);
        bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header));
        splx(s);

popd
make
make install

>Fix:

	

I don't know.  I had to boot single user and pkg_delete the thing before
a full boot could happen since the /usr/local/etc/rc.d/vmware.sh
script would lock the system upon reboot.

I recommend marking this port as broken so others don't get stuck like
this.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-ports 
Responsible-Changed-By: jedgar 
Responsible-Changed-When: Wed Aug 16 04:43:59 PDT 2000 
Responsible-Changed-Why:  
Misfiled PR 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20624 
State-Changed-From-To: open->closed 
State-Changed-By: knu 
State-Changed-When: Sat Sep 16 17:56:24 JST 2000 
State-Changed-Why:  
A similar patch was added. (set the second argument of ether_ifattach() 
to ETHER_BPF_SUPPORTED, instead of 0 (ETHER_BPF_UNSUPPORTED)) 

Please check it out.  Thanks for the report! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20624 
State-Changed-From-To: closed->open 
State-Changed-By: knu 
State-Changed-When: Sat Oct 7 13:43:18 JST 2000 
State-Changed-Why:  
This PR was of vmware 1.x port, not 2.x port. 


Responsible-Changed-From-To: freebsd-ports->freebsd-emulation 
Responsible-Changed-By: knu 
Responsible-Changed-When: Sat Oct 7 13:43:18 JST 2000 
Responsible-Changed-Why:  
Over to the most appropriate list. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20624 

From: Vivek Khera <vivek@khera.org>
To: freebsd-gnats-submit@FreeBSD.org, khera@kciLink.com
Cc:  
Subject: Re: ports/20624: vmware vmmon module locks kernel
Date: Fri, 17 Nov 2000 17:18:15 -0500

 This is a multi-part message in MIME format.
 --------------D08105A8AEAECE417F43DD70
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 To make vmware version 1 work, you need to build the vmware2 port, and
 replace the kernel modules from vmware1 with the module from vmware2,
 and update the startup scripts appropriately from vmware2.  Most messy. 
 I did manage to get it to run vmware1 however.
 
 vmware1 should be marked broken, however, since the modules as-is lock
 up the kernel hard and require a hardware reset.
 --------------D08105A8AEAECE417F43DD70
 Content-Type: text/x-vcard; charset=us-ascii;
  name="vivek.vcf"
 Content-Transfer-Encoding: 7bit
 Content-Description: Card for Vivek Khera
 Content-Disposition: attachment;
  filename="vivek.vcf"
 
 begin:vcard 
 n:Khera;Vivek
 tel;fax:301-545-6899
 tel;work:301-545-6996
 x-mozilla-html:TRUE
 url:http://www.khera.org/~vivek/
 org:Khera Communications, Inc.
 version:2.1
 email;internet:vivek@khera.org
 adr;quoted-printable:;;1445 Research Blvd=0D=0A5th Floor;Rockville;MD;20850;USA
 x-mozilla-cpt:;0
 fn:Vivek Khera
 end:vcard
 
 --------------D08105A8AEAECE417F43DD70--
 
 
Responsible-Changed-From-To: freebsd-emulation->freebsd-bugs 
Responsible-Changed-By: ru 
Responsible-Changed-When: Tue Jul 3 07:02:40 PDT 2001 
Responsible-Changed-Why:  
freebsd-emulation is not a valid responsible. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20624 
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Sat Aug 25 16:24:10 PDT 2001 
State-Changed-Why:  

Does this problem still exist? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20624 

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
 
State-Changed-From-To: feedback->open 
State-Changed-By: iedowse 
State-Changed-When: Mon Aug 27 13:00:33 PDT 2001 
State-Changed-Why:  

This is apparently still a problem. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20624 
State-Changed-From-To: open->closed 
State-Changed-By: asmodai 
State-Changed-When: Thu Nov 15 11:51:46 PST 2001 
State-Changed-Why:  
Sorry, but with 3.0 being imminent or already released I see little 
use in trying to still try to support 1.x of VMWare, so much 
progress gets made in the application itself. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20624 
>Unformatted:
