From owner-freebsd-questions@FreeBSD.ORG  Sun Oct 31 17:14:58 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3F29216A4CE
	for <questions@freebsd.org>; Sun, 31 Oct 2004 17:14:58 +0000 (GMT)
Received: from imo-m21.mx.aol.com (imo-m21.mx.aol.com [64.12.137.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C411943D55
	for <questions@freebsd.org>; Sun, 31 Oct 2004 17:14:57 +0000 (GMT)
	(envelope-from TM4525@aol.com)
Received: from TM4525@aol.com
	by imo-m21.mx.aol.com (mail_out_v37_r3.8.) id t.89.187ce792 (3972);
	Sun, 31 Oct 2004 12:14:49 -0500 (EST)
From: TM4525@aol.com
Message-ID: <89.187ce792.2eb67789@aol.com>
Date: Sun, 31 Oct 2004 12:14:49 EST
To: josh@hewbert.com
MIME-Version: 1.0
X-Mailer: 9.0 for Windows sub 5114
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.1
cc: questions@freebsd.org
Subject: Re: 5.3-RC1 - Hangs on high net load(?)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Oct 2004 17:14:58 -0000

In a message dated 10/31/04 11:56:29 AM Eastern Standard Time, 
josh@hewbert.com writes:
>After upgrading from 5.2.1 to 5.3-RC1 (including a recompile of all
>ports), I noticed my system locking up when there was a high network
>load.  A common way to reproduce this is to run a BiTTorrent client and,
>say, copy a file to another local machine over NFS.  The computer does
>not respond to pings or any key presses.  I'm using the lnc(4) driver
>for an AMD PCnet PCI ethernet card (exact model escapes me)
>[Am79C970/1/2/3/5/6 PCnet LANCE PCI Ethernet Controller].  (I'm aware of
>the pcn(4) driver, but cannot get it to recognize the card).  I can
>reproduce this with both the 4BSD and ULE schedulers, if that matters.
>
>All relevant sysctl variables are defaults. Is this a known issue?
>Any ideas?  Thanks.

Are you certain that its not NFS that's locking up? Certainly the use
of NFS muddies the issue, as it doesnt like losing packets and isn't 
very eloquent in its handling of adversity.