From owner-freebsd-hackers Wed May 7 02:51:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA13417 for hackers-outgoing; Wed, 7 May 1997 02:51:29 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA13412 for ; Wed, 7 May 1997 02:51:25 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id TAA29730; Wed, 7 May 1997 19:55:10 +1000 (EST) Date: Wed, 7 May 1997 19:55:09 +1000 (EST) From: "Daniel O'Callaghan" To: Alexander Fuchsstadt cc: Garrett Casey , FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Slow, Slow, Slow In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 7 May 1997, Alexander Fuchsstadt wrote: > Hi, > I had a quite similar problem, but to a different hardware. A DEC > AlphaServer 1000 showed the same symptoms, mostly 100% idle, running a > R/3 system, logon took a minute, and working was not possible. Even a ls > -lR hung after all applications were stoped. > I then logged on via seriel and noticed, that the system ran normally. > This fact made me change the ethernet adapter, and the system now runs > with pretty good speed. > The reason for is that many applications use TCP/IP for communication and > in case of a network adapter failure they can't proceed any more, do not > report any errors and cpu is idle. Another possibility is a network card fault elsewhere on the LAN. I was driven nuts by the refusal of a Win machine to talk to a FreeBSD machine at anything like an acceptable speed. It turned out to be a broken D-link parallel port ethernet adapter on a third machine which was causing the problems. The frustrating thing was that IPX "appeared" to work normally. Danny