From owner-freebsd-stable Mon Oct 4 6:20:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id A914115496 for ; Mon, 4 Oct 1999 06:20:27 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id JAA22300; Mon, 4 Oct 1999 09:20:25 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id JAA02125; Mon, 4 Oct 1999 09:20:23 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id JAA01108; Mon, 4 Oct 1999 09:20:26 -0400 (EDT) Date: Mon, 4 Oct 1999 09:20:26 -0400 (EDT) From: Thomas David Rivers Message-Id: <199910041320.JAA01108@lakes.dignus.com> To: jeffrl@wantabe.com, rivers@dignus.com Subject: Re: Spontaneous reboot on 3.3-RELEASE. Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i've had problems like these over the years. usually i have a bad spot in > my ram or in the bios. > > often the ram problem is pointed out by "page fault" failures, such as > while running fsck in a daily cron job. > > cheers, > jeff Yes, thanks.... I've frequently seen others post such observations. [and, I believe that's what is happening to me.] It's just rather sudden - the machine has been running for almost a week with no ram problems... but, that's the nature of the beast :-) I'm off to CompUSA to grab some RAM... - Thanks again - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message