Date: Wed, 7 May 1997 19:55:09 +1000 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Alexander Fuchsstadt <afuchs@totum.plaut.de> Cc: Garrett Casey <garrett@websidestory.com>, FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Slow, Slow, Slow Message-ID: <Pine.BSF.3.91.970507195135.4479B-100000@panda.hilink.com.au> In-Reply-To: <Pine.BSF.3.95.970507104432.18349A-100000@totum.plaut.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970507195135.4479B-100000>