From owner-freebsd-current@FreeBSD.ORG Sat Jun 18 15:05:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 1CFD816A41C for ; Sat, 18 Jun 2005 15:05:02 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id C753D43D1D for ; Sat, 18 Jun 2005 15:05:01 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 89BB260F3; Sat, 18 Jun 2005 17:04:47 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 1DF7260F2; Sat, 18 Jun 2005 17:04:47 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 00C8533C23; Sat, 18 Jun 2005 17:04:46 +0200 (CEST) To: Tarc References: <20050617180321.GA1131@tarc.po.cs.msu.su> <867jgskfvd.fsf@xps.des.no> <20050618105622.GA723@tarc.po.cs.msu.su> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Sat, 18 Jun 2005 17:04:46 +0200 In-Reply-To: <20050618105622.GA723@tarc.po.cs.msu.su> (tarc@tarc.po.cs.msu.su's message of "Sat, 18 Jun 2005 14:56:22 +0400") Message-ID: <86k6krg0z5.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Learn: ham X-Spam-Score: -5.2/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on tim.des.no Cc: freebsd-current Subject: Re: -CURRENT crashes on compilling X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 18 Jun 2005 15:05:02 -0000 Tarc writes: > On Fri, Jun 17, 2005 at 08:17:10PM +0200, Dag-Erling Sm=D0=ACrgrav wrote: > > Bad hardware - most likely bad RAM, possibly a bad CPU. > Hmm... I thinked about this, but RAM is ok. How do you know? Most software memory testers don't load the system enough to trip over marginal RAM; 'make buildworld' does. > How test processor? 'make buildworld' with known-good RAM is a pretty good indicator. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no