From owner-freebsd-current@FreeBSD.ORG Sun Jun 19 20:40:20 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 854CF16A41C for ; Sun, 19 Jun 2005 20:40:20 +0000 (GMT) (envelope-from toa@pop.agri.ch) Received: from smtp.messaging.ch (exsmtp01.agrinet.ch [81.221.250.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18FED43D53 for ; Sun, 19 Jun 2005 20:40:19 +0000 (GMT) (envelope-from toa@pop.agri.ch) Received: from [192.168.225.5] ([80.218.0.93]) by smtp.messaging.ch with Microsoft SMTPSVC(6.0.3790.211); Sun, 19 Jun 2005 22:40:18 +0200 Message-ID: <42B5D82E.2090509@pop.agri.ch> Date: Sun, 19 Jun 2005 22:40:14 +0200 From: Andreas Tobler User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?UTF-8?B?77+9?= References: <20050617180321.GA1131@tarc.po.cs.msu.su> <867jgskfvd.fsf@xps.des.no> <20050618105622.GA723@tarc.po.cs.msu.su> <86k6krg0z5.fsf@xps.des.no> In-Reply-To: <86k6krg0z5.fsf@xps.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 19 Jun 2005 20:40:18.0200 (UTC) FILETIME=[1AA66980:01C5750F] Cc: Tarc , 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: Sun, 19 Jun 2005 20:40:20 -0000 Dag-Erling Smørgrav wrote: > Tarc writes: > >>On Fri, Jun 17, 2005 at 08:17:10PM +0200, Dag-Erling SmЬrgrav wrote: >> >>>Bad hardware - most likely bad RAM, possibly a bad CPU. >> >>Hmm... I thinked about this, but RAM is ok. Side note, I could not have a look at your config/dmesg etc. tarc.po.cs.msu.su could not be found. > How do you know? Most software memory testers don't load the system > enough to trip over marginal RAM; 'make buildworld' does. Yeah, buildkernel and buildworld are good stress tests. The same as a gcc bootstrap is. >>How test processor? > > > 'make buildworld' with known-good RAM is a pretty good indicator. Here my side note 2, it's not on x86, but on ppc. I have a powerbook with one GB of ram. Doing buildworld and buildkernel ended up in such sig 11 failures at random places. Not reproducable. I know my hw is ok, I do daily gcc bootstraps and the machine works. But under fbsd ppc I got the above sig 11 issues. A short talk with Peter Grehan made me try to reduce the physical memory software side with hw.physmem=512M. Bingo, that was it. I could do buildkernel and buildworld with hw.physmem=512M. No problem. So, our thinking is, that there is a trouble with physical mem > 512/640MB on fbsd ppc. This note may not help in your case since it is on ppc fbsd. But maybe it gives you another idea? Regards, Andreas