From owner-freebsd-hackers Wed May 7 01:53:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11632 for hackers-outgoing; Wed, 7 May 1997 01:53:40 -0700 (PDT) Received: from plaut.de (inet.plaut.de [194.39.177.166]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA11625 for ; Wed, 7 May 1997 01:53:37 -0700 (PDT) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by plaut.de (8.6.12/8.6.12) with ESMTP id KAA25950; Wed, 7 May 1997 10:53:33 +0200 Received: from localhost (afuchs@localhost) by totum.plaut.de (8.8.5/8.7.3) with SMTP id KAA19539; Wed, 7 May 1997 10:53:35 +0200 (MET DST) Date: Wed, 7 May 1997 10:53:34 +0200 (MET DST) From: Alexander Fuchsstadt To: Garrett Casey cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Slow, Slow, Slow In-Reply-To: <3.0.1.32.19970506213922.00908210@mail.websidestory.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. Bye Alex