From owner-freebsd-questions@FreeBSD.ORG Mon Sep 8 05:58:00 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECFDD16A4BF for ; Mon, 8 Sep 2003 05:58:00 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11B4C43FB1 for ; Mon, 8 Sep 2003 05:57:58 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (rwcrmhc13) with ESMTP id <20030908125757015003l3uae>; Mon, 8 Sep 2003 12:57:57 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h88Cvuto014705; Mon, 8 Sep 2003 08:57:56 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h88Cvq2H014702; Mon, 8 Sep 2003 08:57:52 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: "admin" References: <20030907175542.M69000@enabled.com> From: Lowell Gilbert Date: 08 Sep 2003 08:57:52 -0400 In-Reply-To: <20030907175542.M69000@enabled.com> Message-ID: <44ad9figj3.fsf@be-well.ilk.org> Lines: 9 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: [newbie] 4.8-STABLE became unreachable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 12:58:01 -0000 "admin" writes: > I am suspecting hardware issues - perhaps the RAM memory board. 512MB single > board. If your suspicion is strong, test this directly. Do a full memory test if you can take the machine offline long enough; if not, do something that is both memory- and cpu- intensive ("make buildworld" is the traditional suggestion :-).