From owner-freebsd-current@FreeBSD.ORG  Tue Jun 20 20:37:04 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 103D416A479
	for <freebsd-current@freebsd.org>; Tue, 20 Jun 2006 20:37:04 +0000 (UTC)
	(envelope-from astrodog@gmail.com)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C3ED043D78
	for <freebsd-current@freebsd.org>; Tue, 20 Jun 2006 20:37:01 +0000 (GMT)
	(envelope-from astrodog@gmail.com)
Received: by nf-out-0910.google.com with SMTP id l36so1410204nfa
	for <freebsd-current@freebsd.org>; Tue, 20 Jun 2006 13:37:00 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ULTRPzaOoHzX6nZoD4oCzRKGkxS6nLCNpCrDTgm8XA/TI/euHlWto+70mSccuYymdMTbOEPd6E3eW+0wAlnslhbDc8KWLxHMvllBEAXToY/hwwdIjwxRPDLxdZqafv0qof7il2vAPUxVJtN1Nv3xGC0BKFnXEG5nRBqM2rnKbdU=
Received: by 10.49.31.1 with SMTP id i1mr5985526nfj;
	Tue, 20 Jun 2006 13:37:00 -0700 (PDT)
Received: by 10.49.38.4 with HTTP; Tue, 20 Jun 2006 13:37:00 -0700 (PDT)
Message-ID: <2fd864e0606201337k20fe5225qd8ac55d4fa1a3bda@mail.gmail.com>
Date: Tue, 20 Jun 2006 15:37:00 -0500
From: Astrodog <astrodog@gmail.com>
To: obrien@freebsd.org, "Robert Watson" <rwatson@freebsd.org>, 
	freebsd-current@freebsd.org
In-Reply-To: <20060620202654.GB45624@dragon.NUXI.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060620034229.GA48515@dragon.NUXI.org>
	<44977E82.8040801@samsco.org>
	<20060620113745.N35462@fledge.watson.org>
	<20060620202654.GB45624@dragon.NUXI.org>
Cc: 
Subject: Re: Often experiencing nfs server foo:/bar: not responding
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2006 20:37:04 -0000

On 6/20/06, David O'Brien <obrien@freebsd.org> wrote:
> On Tue, Jun 20, 2006 at 11:38:29AM +0100, Robert Watson wrote:
> > It's possible the origin of the issue is actually a network driver problem.
>
> I experience this with a wide range of NICs for the client (nve, bge,
> gem), and both bge(4) and sk(4) for the server.
>
> --
> -- David  (obrien@FreeBSD.org)
> Q: Because it reverses the logical flow of conversation.
> A: Why is top-posting (putting a reply at the top of the message) frowned upon?
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>

I see this same behavior on newish 6-STABLE and 7-CURRENT systems,
between a FreeBSD server and FreeBSD and Solaris clients.