From owner-freebsd-questions@FreeBSD.ORG Thu Dec 9 19:27:32 2004 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 E7BD716A4CE for ; Thu, 9 Dec 2004 19:27:32 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9285D43D3F for ; Thu, 9 Dec 2004 19:27:32 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-161-115-118.ny325.east.verizon.net [68.161.115.118]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iB9JRQlE031475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 14:27:28 -0500 (EST) Message-ID: <41B8A71A.9040207@mac.com> Date: Thu, 09 Dec 2004 14:27:22 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: akhthar@carmatec.com References: <200412090049.iB90ntMx029318@mail.cs.ait.ac.th> <200412100041.46272.akhthar@carmatec.com> In-Reply-To: <200412100041.46272.akhthar@carmatec.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.5 required=5.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on pi.codefab.com cc: freebsd-questions@freebsd.org Subject: Re: Memory problems:-( X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 19:27:33 -0000 Akhthar Parvez. K wrote: > I have even tried replacing the RAM and upgrading the RAM. But nothing worked. > And I am facing this issue on both my FreeBSd servers. And no problems in my > redhat servers. Please do not give me an unmatured reply as my friends Oliver > and Check gave. A sense of humor is lost on some people, apparently. The error messages you provided suggest hardware failure, whether of RAM, or the CPU overheating, or from some other cause. Taking the system apart and reseating all components is a reasonable first diagnostic step, but if that didn't work and you've exchanged RAM, then I'd try doing a 24-hour run of www.memtest.org's tester and see whether your system can handle that properly. -- -Chuck