From owner-freebsd-hackers Wed Feb 25 16:33:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08740 for freebsd-hackers-outgoing; Wed, 25 Feb 1998 16:33:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08610 for ; Wed, 25 Feb 1998 16:32:56 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id LAA28287; Thu, 26 Feb 1998 11:33:45 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199802260033.LAA28287@cimlogic.com.au> Subject: Re: 2.2.5 keeps crashing . . . please advise. (fwd) In-Reply-To: from Snob Art Genre at "Feb 25, 98 06:14:37 pm" To: benedict@echonyc.com (Snob Art Genre) Date: Thu, 26 Feb 1998 11:33:45 +1100 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre wrote: > Well, I reseated the RAM, and when that didn't work I bought a SIMM and > swapped out each of my own (not at the same time :). No change. What > should I try next? I can repost the results of my investigation so far if > that would help. I am: stumped here. I had a similar sort of crash with 2.2.5 trying to update it to current. I thought it was memory too, but reseating that had no effect. Then I noticed that the CPU fan had come unstuck (it doesn't have a clip like it probably should). After putting the fan back, the system has run reliably since. So as a long shot, is there enough air flow to keep the processor "cool"? 8-) -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message