From owner-freebsd-stable@FreeBSD.ORG Wed Oct 31 22:03:24 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C8B616A41A; Wed, 31 Oct 2007 22:03:24 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 34E3713C481; Wed, 31 Oct 2007 22:03:23 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4728FBAE.4030907@FreeBSD.org> Date: Wed, 31 Oct 2007 23:03:26 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Robert Marella References: <20071029093611.1ec829bc@p4> <20071030072253.6e3ea6b0@p4> <20071030150103.358629d5@asus64> <4727D5CD.7040900@FreeBSD.org> <20071031085044.06cab487@asus64> In-Reply-To: <20071031085044.06cab487@asus64> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Doug Barton , "freebsd-stable@freebsd.org" Subject: Re: Memory issues (was 7.0-BETA1 freeze using portmaster) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 22:03:24 -0000 Robert Marella wrote: > >> Robert Marella wrote: >> >>> It is looking like a hardware problem. I update portmaster to 1.24 >>> and it didn't help. When I tried with the -B option it froze in a >>> different place. I then csup the latest source rm'd /usr/obj and >>> attempted a buildworld. >>> >>> Lo and behold it froze up. It has been very hot the last few days >>> here in Kona but all the fans seem to pulling good air. I am now >>> running memtest and will let you know what I find. > > This is for the archives and to see if any hardware guru out there has > some helpful knowledge. > > This computer has a ASUS P4P800 mobo with 2Gig of ram (4x500M). Memtest > failed within minutes. I then ran each memory module one at a time and > each ran without failures no matter which socket it was in. > > Further tests showed that memory tests failed only when I had 2 or 4 > modules configured as dual channel *. The system is now running flawless > with 3 modules (1.5G) installed which forces single channel operation. > Again, the 3 modules can be in any sockets. > > Since the computer is about 4 years old I am not sure if I want to > invest any additional $$ into it but I would suspect either the mother > board or CPU as the culprit. > > I will be willing to test any ideas anyone has but I guess we can close > this out as another strange effect of memory. > > Robert > > * From the User Guide: > > Mode DIMM_A1 DIMM_A2 DIMM_B1 DIMM_B2 > Dual-channel X X > X X > X X X X Thanks for following up, and I'm glad you resolved it. It's good to remind people from time to time that hardware can and does fail so not every bug is in software :) Kris