From owner-freebsd-questions Fri Aug 30 6: 3:57 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88B3D37B400 for ; Fri, 30 Aug 2002 06:03:53 -0700 (PDT) Received: from mail.seattleFenix.net (seattleFenix.net [216.39.145.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1FF643E3B for ; Fri, 30 Aug 2002 06:03:52 -0700 (PDT) (envelope-from roo@mail.seattleFenix.net) Received: (from roo@localhost) by mail.seattleFenix.net (8.11.6/8.11.6) id g7UD2LM61016; Fri, 30 Aug 2002 06:02:21 -0700 (PDT) (envelope-from roo) Date: Fri, 30 Aug 2002 06:02:21 -0700 From: Benjamin Krueger To: Marc Schneiders Cc: freebsd-questions@freebsd.org Subject: Re: Why is this box so slow? Message-ID: <20020830060221.J59566@mail.seattleFenix.net> References: <20020830144957.C27785-100000@voo.doo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020830144957.C27785-100000@voo.doo.net>; from marc@schneiders.org on Fri, Aug 30, 2002 at 02:55:15PM +0200 X-PGP-Key: http://www.macguire.net/benjamin/public_key.asc Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Marc Schneiders (marc@schneiders.org) [020830 05:54]: > I am running FreeBSD 4 stable on a Pentium II 300 with sufficient RAM, > I think. Nevertheless certain things are very, very slow. A buildworld > takes days. Also opening a large (18 MB file) with vi doesn't work out > for ages. (I am now waiting 5 minutes and still nothing to edit...) When did this problem begin? What circumstances surrounded it? Had you made any changes at the time? > Another thing that is very slow is fsck after the machine crashed. > Hours. Harddisks are reported to run as UDMA-33. So? > > What can be the problem? Dmesg below. > > Machine is collocated, so, please, no suggestions to take RAM out etc. > Thanks! My first educated guess would be to verify that the CPU cache is enabled in the BIOS. When disabled, the machine will display exactly the behavior you're describing. This will, of course, require somebody be able to look at the BIOS. Explore other alternatives, but my money's on this one. Solutions shouldn't be ruled out simply because they cause us hassle. =) Regards, -- Benjamin Krueger "Everyone has wings, some folks just don't know what they're for" - B. Banzai ---------------------------------------------------------------- Send mail w/ subject 'send public key' or query for (0x251A4B18) Fingerprint = A642 F299 C1C1 C828 F186 A851 CFF0 7711 251A 4B18 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message