From owner-freebsd-stable Fri May 7 16: 4: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (Postfix) with ESMTP id C647F15258 for ; Fri, 7 May 1999 16:00:25 -0700 (PDT) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (MailHost/Current) with UUCP id SAA11225 for freebsd-stable@FreeBSD.ORG; Fri, 7 May 1999 18:00:25 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.9.3/8.9.2) with ESMTP id RAA00966 for ; Fri, 7 May 1999 17:30:58 -0500 (CDT) (envelope-from jdn@acp.qiv.com) Date: Fri, 7 May 1999 17:30:58 -0500 (CDT) From: Jay Nelson To: freebsd-stable@FreeBSD.ORG Subject: Re: Strange reboot saga In-Reply-To: <199905070922.JAA18409@jaygrp.intelihealth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a 3.1 (stable from 5/3) system that suddenly started the spontaneous reboot problem, but it turned out to be bad EDO non-parity ram. I replaced the ram and the world has been happy ever since. The only symptoms were random traps, mostly SEGVs and core files. I'm curious if anyone experiencing this problem is _not_ using 32 bit EDO ram. Has anyone experienced this using ECC ram? Another question for the developers: what symptoms would I see if a disk block in a swap partition were bad and no more blocks could be remapped? Thanks -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message