From owner-freebsd-hackers Wed Feb 25 16:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04248 for freebsd-hackers-outgoing; Wed, 25 Feb 1998 16:12:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04178 for ; Wed, 25 Feb 1998 16:11:56 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id SAA29566; Wed, 25 Feb 1998 18:14:37 -0500 (EST) Date: Wed, 25 Feb 1998 18:14:37 -0500 (EST) From: Snob Art Genre To: Graham Wheeler cc: hackers@FreeBSD.ORG Subject: Re: 2.2.5 keeps crashing . . . please advise. (fwd) In-Reply-To: <199802241621.SAA00278@cdsec.com> Message-ID: 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, Graham Wheeler wrote: > Looks like bad RAM, or possibly badly seated RAM. I have experienced exactly > the same problem; swapped the SIMMs with another machines and the problem > disappeared (so it was a seating problem). 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. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message