From owner-freebsd-hackers  Tue Feb 24 08:49:14 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA28654
          for freebsd-hackers-outgoing; Tue, 24 Feb 1998 08:49:14 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from misery.sdf.com (misery.sdf.com [204.244.213.32])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA28647
          for <hackers@freebsd.org>; Tue, 24 Feb 1998 08:49:07 -0800 (PST)
          (envelope-from tom@sdf.com)
Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3)
	id 0y7NGX-0002oO-00; Tue, 24 Feb 1998 08:31:33 -0800
Date: Tue, 24 Feb 1998 08:31:32 -0800 (PST)
From: Tom <tom@sdf.com>
To: Snob Art Genre <benedict@echonyc.com>
cc: hackers@FreeBSD.ORG
Subject: Re: 2.2.5 keeps crashing . . . please advise. (fwd)
In-Reply-To: <Pine.GSO.3.96.980224110611.8521A-100000@echonyc.com>
Message-ID: <Pine.BSF.3.95q.980224083014.10804A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Tue, 24 Feb 1998, Snob Art Genre wrote:

> I can find nothing in the system log that would indicate the source of the
> error.  Could it be a hardware problem?

  It is almost certainly a hardware problem.

  I often allocate all available memory on a development machine here
(32MB RAM + 200MB swap).

Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message