From owner-freebsd-questions@FreeBSD.ORG Fri Jun 19 20:58:05 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EE77106564A for ; Fri, 19 Jun 2009 20:58:05 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7D75D8FC12 for ; Fri, 19 Jun 2009 20:58:04 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n5JKvtcx075072; Fri, 19 Jun 2009 22:57:55 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n5JKvt7X075069; Fri, 19 Jun 2009 22:57:55 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Fri, 19 Jun 2009 22:57:55 +0200 (CEST) From: Wojciech Puchar To: Bruce Cran In-Reply-To: <20090619201419.27fcec9b@gluon.draftnet> Message-ID: References: <20090619175537.36128909@gluon.draftnet> <20090619201419.27fcec9b@gluon.draftnet> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: Processes dying with signal 11 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2009 20:58:05 -0000 >>> The problem I see is that after a few hours of running buildworld, >>> when it starts building clang itself, 'as' crashes with a signal 11. >>> >> always at the same point or in random places? >> >> if first - it's probably not hardware problem. > > It's at a random location, but it always happens after the build has > been running for a few hours and when it's ended up swapping some > processes out of main memory. I've read so it is hardware problem. As it start crashing when swap is used, it may be not memory but chipset problem - works fine until disk I/O is used.