From owner-freebsd-current Tue Oct 1 17:55:56 2002 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 DB5FE37B401 for ; Tue, 1 Oct 2002 17:55:55 -0700 (PDT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E3D543E42 for ; Tue, 1 Oct 2002 17:55:55 -0700 (PDT) (envelope-from sam@errno.com) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.5/8.12.1) with ESMTP id g920ts1H048601 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 1 Oct 2002 17:55:55 -0700 (PDT)?g (envelope-from sam@errno.com)œ X-Authentication-Warning: ebb.errno.com: Host melange.errno.com [66.127.85.82] claimed to be melange Message-ID: <138d01c269ae$766ee400$52557f42@errno.com> From: "Sam Leffler" To: Subject: system lockup: nfs server not responding 10 > 9 (tx driver bug?) Date: Tue, 1 Oct 2002 17:55:54 -0700 Organization: Errno Consulting MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have repeated problems where a machine running -current locks up while running make over an NFS mounted filesystem. The NFS server is an up to date -stable machine. When the lockup occurs I get a message: nfs server : not responding 10 > 9 The filesystem is mounted r/w with no options. nfsiod's 0, 1, and 2 are in DL, 3 is in IL state. nfsiod 0 is sleeping on sbwait. The -current machine is up to date. 100 Mb/s Ethernet. tx driver. When the lockup occurs I can still login to the console but the network appears dead (no packets appear to pass). Looks like maybe a tx driver bug. Anyone seen this with other NIC's? Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message