Date: Fri, 29 Apr 2005 17:56:40 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: /dev/null <null@dnswatch.com> Cc: freebsd-current@freebsd.org Subject: Re: can't build kernel [with CONFIG this time][[[FIXED]]] Message-ID: <20050429075640.GB232@cirb503493.alcatel.com.au> In-Reply-To: <54623.216.177.243.35.1114717482.localmail@webmail.dnswatch.com> References: <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> <54623.216.177.243.35.1114717482.localmail@webmail.dnswatch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2005-Apr-28 12:44:42 -0700, /dev/null wrote: >Good point(s). I sure wish I could just use 1 giant can capacitor that >simply fills as required and releases as necessary. That won't work - there's too much inductance between (and inside) the giant can capacitor and the electronics. The bypasses that matter for logic transitions are the surface-mount chip ceramics that are on the RAM stick, on the CPU carrier and next to (under) the northbridge. >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. Try under-clocking a bit, or using more conservative memory timings (especially if you've set you motherboard to "aggressive" timings). -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050429075640.GB232>