From owner-freebsd-questions@FreeBSD.ORG Wed Jan 9 19:03:36 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CC3516A419 for ; Wed, 9 Jan 2008 19:03:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 332FE13C46E; Wed, 9 Jan 2008 19:03:34 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47851A85.9070501@FreeBSD.org> Date: Wed, 09 Jan 2008 20:03:33 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: robert@webtent.com References: <1199888376.7589.6.camel@columbus.webtent.org> In-Reply-To: <1199888376.7589.6.camel@columbus.webtent.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Subject: Re: 5.4-RELEASE crashing X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 19:03:36 -0000 Robert Fitzpatrick wrote: > I upgraded memory in a 5.4-RELEASE server from 1GB (2x512MB) to 4GB > (4x1GB). I'm wondering if that can even be causing my problem since > nothing went wrong for an entire week. One week later, the server just > stops responding in the middle of the night, I can see the login prompt, > but cannot type anything, no response to keyboard at all. Since the > initial crash one week after the memory upgrade, it continues to do this > every couple of days. > > The crash has happened during the 3-4am time span every time except at > 9pm once and then this morning at 9am. So, it seems it may be related to > something building up over time. After reset and disk cleanup, I have > examined the logs and cannot find anything in the message log, one entry > shows my last login activity and the next entry is the start of boot > info from the reset. The only thing I find in the logs erroneous is an > NFS connection not responding, then alive again, but I unmounted and > disabled the entry in fstab before it happened this morning. > > I'm just trying to figure out how to approach tracking down my crashing > issue. Whether it somehow is related to the memory upgrade. The only > thing to note about the memory upgrade is on boot, it will say that it > is ignoring a small amount of memory over 4GB. Can someone suggest how > to approach my problem? > It's almost certain to be bad RAM. Try swapping it out incrementally until the problem goes away, then toss that stick in the garbage :) Kris