From owner-freebsd-current@FreeBSD.ORG Wed Apr 27 23:16:06 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 E0C1516A4CE for ; Wed, 27 Apr 2005 23:16:06 +0000 (GMT) Received: from toad.mtbrook.bozemanpass.com (toad.mtbrook.bozemanpass.com [69.145.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEF2443D53 for ; Wed, 27 Apr 2005 23:16:06 +0000 (GMT) (envelope-from elliot.schlegelmilch@gmail.com) Received: from [69.145.82.223] (unknown [69.145.82.223]) by toad.mtbrook.bozemanpass.com (Postfix) with ESMTP id 90D831102E6; Wed, 27 Apr 2005 16:19:16 -0700 (PDT) Message-ID: <42701D35.6020307@gmail.com> Date: Wed, 27 Apr 2005 17:16:05 -0600 From: Elliot Schlegelmilch User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: /dev/null 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> In-Reply-To: <64018.216.177.243.35.1114641057.localmail@webmail.dnswatch.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 27 Apr 2005 23:16:07 -0000 /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.