From owner-freebsd-current@FreeBSD.ORG Thu Apr 28 08:29:44 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 3BF5716A4CE for ; Thu, 28 Apr 2005 08:29:44 +0000 (GMT) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6534F43D54 for ; Thu, 28 Apr 2005 08:29:43 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j3S8TX1D004309 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 28 Apr 2005 18:29:34 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j3S8TXXw001655; Thu, 28 Apr 2005 18:29:33 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j3S8TWna001654; Thu, 28 Apr 2005 18:29:32 +1000 (EST) (envelope-from pjeremy) Date: Thu, 28 Apr 2005 18:29:31 +1000 From: Peter Jeremy To: /dev/null Message-ID: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59642.216.177.243.35.1114655240.localmail@webmail.dnswatch.com> User-Agent: Mutt/1.4.2i 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 08:29:44 -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. -- Peter Jeremy