From owner-freebsd-current@FreeBSD.ORG Mon Nov 10 08:00:46 2003 Return-Path: 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 7D03416A4CE for ; Mon, 10 Nov 2003 08:00:46 -0800 (PST) Received: from swank.verbotenplanet.net (mail.verbotenplanet.net [207.99.115.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BC4143FE5 for ; Mon, 10 Nov 2003 08:00:45 -0800 (PST) (envelope-from schnozzy@verbotenplanet.net) Received: from www by swank.verbotenplanet.net with local (Exim 4.24; FreeBSD 4.9) id 1AJET2-000E9u-Sj for current@FreeBSD.ORG; Mon, 10 Nov 2003 11:00:40 -0500 From: "Kelley Reynolds" Date: Mon, 10 Nov 2003 11:00:40 -0500 To: current@FreeBSD.ORG In-Reply-To: <200311101503.hAAF3lbV005452@spider.deepcore.dk> Message-ID: <0.87229300.1068480040@verbotenplanet.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Description: messagebody References: <200311101503.hAAF3lbV005452@spider.deepcore.dk> X-Mailer: ISMail (http://www.insidesystems.net/projects/project.php?projectid=4) X-Mailer-Version: v1.7.1 Subject: Re: Still getting NFS client locking up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: schnozzy@verbotenplanet.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2003 16:00:46 -0000 --- Original Message --- From: Soren Schmidt Sent: Mon, 10 Nov 2003 16:03:47 +0100 (CET) To: Matt Smith Subject: Re: Still getting NFS client locking up > It seems Matt Smith wrote: > > With a current build from november the 9th I am still getting exactly > > the same NFS lockups. I assume soren is as well. NFS has basically been > > pretty unusable now for over a month. > > Yes I do, NFS is virtually useless... > > > As only a couple of people have complained about this from what I can > > see I assume it is something related to something specific such as a > > network card? > > Could be, but its more than one type of card which suggests to me > its more "generic" in origin.. > > > From my testing I only get this lockup when writing to the server. > > Reading from the server works perfectly all the time. So luckily I can > > still manage an NFS mounted installworld/kernel. > > I can also lock it up with just reading, but it takes longer. > > > Obviously we should really try and find the cause of this before 5.2. I > > am willing to try any patches/debug on my systems. But I just have zero > > clue about what to look for myself. > > I think its a definite showstopper for 5.2 actually.. > Just to add some more evidence to the mix, I have two 5.1 current boxes using bfe, vr, and both have ath, and I am experience all of the lockups on the server end... client has yet to lock up. Kelley