From owner-freebsd-current@FreeBSD.ORG Mon Nov 10 07:03:11 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 8D2B816A4D5; Mon, 10 Nov 2003 07:03:11 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2870143F75; Mon, 10 Nov 2003 07:03:10 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.10/8.12.10) with ESMTP id hAAF3mEQ005453; Mon, 10 Nov 2003 16:03:48 +0100 (CET) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.10/8.12.10/Submit) id hAAF3lbV005452; Mon, 10 Nov 2003 16:03:48 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200311101503.hAAF3lbV005452@spider.deepcore.dk> In-Reply-To: <3FAFA5A3.3000704@xtaz.co.uk> To: Matt Smith Date: Mon, 10 Nov 2003 16:03:47 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: Robert Watson cc: current@FreeBSD.ORG Subject: Re: Still getting NFS client locking up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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 15:03:11 -0000 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.. > NFS SERVER: > xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x1000-0x107f mem > 0xfc304800-0xfc30487f irq 10 at device 7.0 on pci5 > xl0: Ethernet address: 00:04:76:8d:c5:fd > miibus0: on xl0 > xlphy0: <3c905C 10/100 internal PHY> on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto OK the worst server I've got has: re0: port 0xdc00-0xdcff mem 0xe4000000-0xe40000ff irq 12 at device 9.0 on pci0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re1: port 0xe000-0xe0ff mem 0xe4001000-0xe40010ff irq 10 at device 10.0 on pci0 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re2: port 0xe400-0xe4ff mem 0xe4002000-0xe40020ff irq 11 at device 11.0 on pci0 rlphy2: on miibus2 rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto The clients use fxp/xl/sis cards and can all make this server hang in seconds.. -Søren