From owner-freebsd-questions@FreeBSD.ORG Fri Jan 23 15:57:11 2004 Return-Path: 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 ABF1B16A4CE for ; Fri, 23 Jan 2004 15:57:11 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 652C143D6A for ; Fri, 23 Jan 2004 15:56:15 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 03F0566DF2; Fri, 23 Jan 2004 15:54:44 -0800 (PST) Date: Fri, 23 Jan 2004 15:54:44 -0800 From: Kris Kennaway To: "Richard G. Roberto" Message-ID: <20040123235444.GB93595@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zx4FCpZtqtKETZ7O" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-questions@freebsd.org Subject: Re: CPU usage goes way up on 5.1 when memory is added X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 23:57:11 -0000 --zx4FCpZtqtKETZ7O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 23, 2004 at 06:07:20PM -0500, Richard G. Roberto wrote: > Hi, >=20 > I've been running 5.1-RELEASE for quite some time on my dual PIII 333Mhz > Micron PC with 384MB of RAM and 670MB of swap. Its a little low on memory > for what I'm now doing with it though, so I added 256MB of RAM. The new > RAM gets recognized, and there are no obvious errors on the console or in > the logs, but every little thing drives the CPU utilization through the > roof and the system is unusable. Even just typing "man ls" triggers it, > never mind trying to run ssh. I remove the RAM, and it goes back to > normal. How are you trying to measure this? Have you tried reverting to a GENERIC kernel to isolate one of your non-default options that may be causing the problem (or measurement artefact)? Kris --zx4FCpZtqtKETZ7O Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAEbREWry0BWjoQKURAqEBAKDVhZVKQuuLKPWpaeHrgAJIeExosQCggL0B T8odKrjRb3013zP8gZ+FPQk= =Hd60 -----END PGP SIGNATURE----- --zx4FCpZtqtKETZ7O--