Date: Tue, 21 Aug 2007 12:13:42 -0500 (CDT) From: "Sean C. Farley" <scf@FreeBSD.org> To: Nenhum_de_Nos <matheusber@gmail.com> Cc: freebsd-current@FreeBSD.org Subject: Re: error building yesterday code Message-ID: <alpine.BSF.0.999.0708211203110.4160@thor.farley.org> In-Reply-To: <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com> References: <4956a5e50708201723l623cf384ub10edd3ceea88e62@mail.gmail.com> <4956a5e50708201931t5e55d1d3lb329ed53b0edb356@mail.gmail.com> <b1fa29170708202132j3c9f2181ub48ea761d0102f99@mail.gmail.com> <4956a5e50708210725k76925c45l46410719029d6dd4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Aug 2007, Nenhum_de_Nos wrote: > On 8/21/07, Kip Macy <kip.macy@gmail.com> wrote: >> Sounds like bad memory. Try memtest. >> > memtest is 91% ano bad nothing ... > > at night I can make further tests, but so far I'm not blaming the > memory > > any other ideas ? Bad caps (http://www.badcaps.net/)? The site tells you what to examine. I had some capacitors go bad on two motherboards (circa 2001). In fact, one of the boards did not show any physical problems with the capacitors until much later. memtest did not show any issues, and I ran it many times. If it is happening at various locations in the code as opposed to the same line each time, it usually points to hardware issues. Sean -- scf@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.0.999.0708211203110.4160>