From owner-freebsd-current@FreeBSD.ORG Thu Apr 28 01:04:08 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80ECC16A4CE for ; Thu, 28 Apr 2005 01:04:08 +0000 (GMT) Received: from plounts.uits.indiana.edu (plounts.uits.indiana.edu [129.79.1.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D02D43D48 for ; Thu, 28 Apr 2005 01:04:08 +0000 (GMT) (envelope-from dmschei@attglobal.net) Received: from mail-relay.iu.edu (logchain.uits.indiana.edu [129.79.1.77]) j3S13jx5009779; Wed, 27 Apr 2005 20:03:45 -0500 (EST) Received: from [10.0.1.4] (scheidt-rout.canopy.nd.edu [129.74.98.169] (may be forged)) (authenticated bits=0)j3S13jsY012770; Wed, 27 Apr 2005 20:03:45 -0500 (EST) Message-ID: <42703671.8060707@attglobal.net> Date: Wed, 27 Apr 2005 20:03:45 -0500 From: David Scheidt User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050426) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Elliot Schlegelmilch References: <63349.216.177.243.42.1114575288.localmail@webmail.dnswatch.com> <20050427060414.GA54657@ns2.wananchi.com> <55065.216.177.243.42.1114583234.localmail@webmail.dnswatch.com> <20050427083649.GC6929@ns2.wananchi.com> <61364.216.177.243.42.1114593685.localmail@webmail.dnswatch.com> <84dead7205042706554f32484@mail.gmail.com> <57775.216.177.243.35.1114633009.localmail@webmail.dnswatch.com> <20050427204939.GA796@uk.tiscali.com> <53015.216.177.243.35.1114635611.localmail@webmail.dnswatch.com> <20050427212835.GA87673@uk.tiscali.com> <64018.216.177.243.35.1114641057.localmail@webmail.dnswatch.com> <42701D35.6020307@gmail.com> In-Reply-To: <42701D35.6020307@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: /dev/null cc: freebsd-current@freebsd.org Subject: Re: can't build kernel [with CONFIG this time][[[FIXED]]] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2005 01:04:08 -0000 Elliot Schlegelmilch wrote: > /dev/null wrote: > >> Greetings, >> To anyone that was following this, or is interested. The problem >> turned out >> to be the fact that the new processor didn't play well with the RAM. A >> different stick of RAM solved it. :) >> >> > For future reference, if anything things 'weirdly', the memory tester at > http://www.memtest86.com/ is one of the first things I try. Remember that just because some random piece of software doesn't detect errors doesn't mean they don't exist. Memtest86 has never found an error on anything I've run it on.