From owner-freebsd-hackers Thu Sep 10 14:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07589 for freebsd-hackers-outgoing; Thu, 10 Sep 1998 14:57:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hoth.ffwd.bc.ca ([209.153.243.242]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA07574 for ; Thu, 10 Sep 1998 14:57:54 -0700 (PDT) (envelope-from skye@ffwd.bc.ca) Received: from skye by hoth.ffwd.bc.ca with local (Exim 1.82 #3) id 0zHEhr-0004sJ-00; Thu, 10 Sep 1998 14:56:47 -0700 Message-ID: <19980910145647.62321@ffwd.bc.ca> Date: Thu, 10 Sep 1998 14:56:47 -0700 From: Skye Poier To: freebsd-hackers@FreeBSD.ORG Subject: Re: VM crash? questions pt.2 References: <19980820172445.54455@ffwd.bc.ca> <19980826113428.29710@ffwd.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85 In-Reply-To: <19980826113428.29710@ffwd.bc.ca>; from Skye Poier on Wed, Aug 26, 1998 at 11:34:28AM -0700 X-URL: http://www.ffwd.bc.ca/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If anyone is interested, the problem has been resolved. Setting the CPU clock speed to the correct value (it was accidently overclocked from 66 to 80 MHz when I installed the new CPU) has eliminated the strange swap partition problems. Cheers, Skye Word on the street is that Skye Poier said: > Previously I said: > > I am running 2.2.6-RELEASE on a 486 with 16mb of memory and a 65mb swap > > partition. > > > > Recently I've been working with some rather large files and the machine > > has had a tendancy to lock up solid. No error on the console, in dmesg, > > nothing. It seems to happen when VM (via swapinfo) reaches 30% usage or > > about 19MB of the 65MB avaiable.... other than this the server has been > > totally bulletproof. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message