From owner-freebsd-current@FreeBSD.ORG Thu Apr 28 19:44:49 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 5BACE16A4CE for ; Thu, 28 Apr 2005 19:44:49 +0000 (GMT) Received: from fast.dnswatch.com (fast.dnswatch.com [216.177.243.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD7EF43D41 for ; Thu, 28 Apr 2005 19:44:48 +0000 (GMT) (envelope-from null@dnswatch.com) Received: from fast.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.12.6/8.12.6) with ESMTP id j3SJiirt008410; Thu, 28 Apr 2005 12:44:47 -0700 (PDT) (envelope-from null@dnswatch.com) Received: (from www@localhost) by fast.dnswatch.com (8.12.6/8.12.6/Submit) id j3SJihBQ008409; Thu, 28 Apr 2005 12:44:43 -0700 (PDT) (envelope-from null@dnswatch.com) X-Authentication-Warning: fast.dnswatch.com: www set sender to null@dnswatch.com using -f Received: from mail.1command.com ([216.177.243.35]) (DNSwatch.com_WebMail authenticated user null) by webmail.dnswatch.com with HTTP; Thu, 28 Apr 2005 12:44:42 -0700 (PDT) Message-ID: <54623.216.177.243.35.1114717482.localmail@webmail.dnswatch.com> In-Reply-To: <20050428082931.GA232@cirb503493.alcatel.com.au> References: <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> <42703671.8060707@attglobal.net> <59642.216.177.243.35.1114655240.localmail@webmail.dnswatch.com> <20050428082931.GA232@cirb503493.alcatel.com.au> Date: Thu, 28 Apr 2005 12:44:42 -0700 (PDT) From: "/dev/null" To: "Peter Jeremy" User-Agent: DNSwatch.com_WebMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal 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 19:44:49 -0000 > On Wed, 2005-Apr-27 19:27:20 -0700, /dev/null wrote: >>In my case I think it was just "sync" issues between the CPU cache and >>the RAM. Although it could have been just that this processor drove >>the RAM stick hard enough to make it fail. No matter, the stick of RAM is >>working flawlessly in a different box. :) > > Modern hardware is pushed very close to the limits. Maybe the RAM has > some pattern sensitivity that just happens to be hit by buildkernel or > buildworld. Maybe a combination of marginal bypass capacitors, > marginal memory bus drivers means that the logic transition is a few > picoseconds longer than desirable if a large number of bits change > state simultaneously so that the transition isn't seen by the marginal > receiver. > Good point(s). I sure wish I could just use 1 giant can capacitor that simply fills as required and releases as necessary. It would be so much simpler. On a sad note, after a long period of usage it still fails. So it seems that the new CPU is the culprit (CPU's cache?). Anyway, I might disable the CPU's cache in the bios settings and see what happens, while I wait for another CPU. Best wishes, Chris > -- > Peter Jeremy > //////////////////////////////////////////////////// If only Western Electric had found a way to offer binary licenses for the UNIX system back in 1974, the UNIX system would be running on all PC's today rather than DOS/Windows. ////////////////////////////////////////////////////