From owner-freebsd-bugs@FreeBSD.ORG  Mon Feb 23 09:04:04 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B0F5316A4CE; Mon, 23 Feb 2004 09:04:04 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 906EB43D2D; Mon, 23 Feb 2004 09:04:04 -0800 (PST)
	(envelope-from matusita@FreeBSD.org)
Received: from freefall.freebsd.org (matusita@localhost [127.0.0.1])
	i1NH44bv014602;	Mon, 23 Feb 2004 09:04:04 -0800 (PST)
	(envelope-from matusita@freefall.freebsd.org)
Received: (from matusita@localhost)
	by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1NH44Jr014598;
	Mon, 23 Feb 2004 09:04:04 -0800 (PST)
	(envelope-from matusita)
Date: Mon, 23 Feb 2004 09:04:04 -0800 (PST)
From: Makoto Matsushita <matusita@FreeBSD.org>
Message-Id: <200402231704.i1NH44Jr014598@freefall.freebsd.org>
To: matusita@FreeBSD.org, freebsd-bugs@FreeBSD.org, paul@FreeBSD.org
Subject: Re: kern/44126: lnc network hungup at large traffics on VMware
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2004 17:04:04 -0000

Synopsis: lnc network hungup at large traffics on VMware

Responsible-Changed-From-To: freebsd-bugs->paul
Responsible-Changed-By: matusita
Responsible-Changed-When: Mon Feb 23 08:57:25 PST 2004
Responsible-Changed-Why: 
VMware developer points out that there is a race condition in lnc
driver.  Paul, I believe you are the best person of investigating
this problem (the copyright says you're the author).  Would you please
check this PR out?

FYI, this problem is now also discussed at VMware Community Forums.
See also: http://www.vmware.com/community/thread.jspa?threadID=1816&tstart=0

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