From owner-freebsd-hardware Tue Aug 25 12:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22398 for freebsd-hardware-outgoing; Tue, 25 Aug 1998 12:45:41 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22390 for ; Tue, 25 Aug 1998 12:45:36 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey.cloud9.net (IDENT:TnkxYKeXXuvjMVVsqAbfFljzx++cdFje@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.9.1a/8.9.0/rc-19980602) with SMTP id PAA19797 for ; Tue, 25 Aug 1998 15:44:46 -0400 (EDT) Date: Tue, 25 Aug 1998 15:44:46 -0400 (EDT) From: Scott Drassinower To: freebsd-hardware@FreeBSD.ORG Subject: Intel 100+ troubles Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In May I posted about a problem we were (and still are) having with Intel 100+ cards with 2.2.6. The machines are connected to a Cisco Catalyst 2916 switch. Some NFS operations, on large (200+ megabyte) files or files that are being constantly updated will simply hang; ps shows them as being in disk wait state. They never recover and won't die. Running tail, grep, or sz on one of these files will reproduce the problem almost every time. A 2.2.6 NFS client reading files from a BSDI 2.1 NFS server also reproduces the problem. I have since tried a Catalyst 2924 (which has silghtly different hardware compared to the 2916), a Catalyst 2926 (which is similar to a Catalyst 5000 and entirely different from the other mid-range Catalyst switches), and an SMC dumb 10/100 hub. In any of these cases, the problem arises. 100 megabit full or half duplex, 10 megabit full or half duplex, same thing. When running the same machines with a 10 megabit dumb hub or a 10 megabit SMC switch, this problem doesn't exist. There was some discussion about Cisco switches being suspect, but the fact that the problem persists with a dumb hub that is running at 100 megabits makes me think something weird is going on with FreeBSD, and not the hardware. Any ideas? -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message