From owner-freebsd-hackers Thu Apr 10 18:20:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA17144 for hackers-outgoing; Thu, 10 Apr 1997 18:20:48 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA17137 for ; Thu, 10 Apr 1997 18:20:43 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AB15516; Thu, 10 Apr 1997 21:20:04 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 10 Apr 1997 21:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id TAA06047 for ; Thu, 10 Apr 1997 19:55:58 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA14202 for freebsd-hackers@freefall.cdrom.com; Thu, 10 Apr 1997 20:02:16 -0400 (EDT) Date: Thu, 10 Apr 1997 20:02:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704110002.UAA14202@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: More on my particular NFS problems (possibly the 3c509/ep0 driver?) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk OK - recalling this is 2.2.1 and I mentioned a lockup during directory accesses of NFS file systems (V2) - mounted from HP/UX 9.05 and SunOS. I did some quick tests on some other hardware, and am begining to believe the problem is my 3c509. Apparently, the ep0 driver has undergone some changes and is possibly the culprit... On Monday, the machine was running 2.1.5, happily doing NFS. On Tuesday, I installed 2.2.1; and now NFS hangs. Today (thursday) I tried the same operations using a 3c900 card (admitedly on a different machine, running 2.2.1) and did not get the problems. This makes me wonder if it's the 3c509 driver in 2.2.1... If this is so, would it explain the hang-up in sbwait()? - Opinions? - - Dave Rivers -