From owner-freebsd-stable@freebsd.org Wed Aug 26 17:38:49 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C672C9C3AA5 for ; Wed, 26 Aug 2015 17:38:49 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: from mail.xtaz.uk (tao.xtaz.uk [IPv6:2001:8b0:202::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 90163A55 for ; Wed, 26 Aug 2015 17:38:49 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: by mail.xtaz.uk (Postfix, from userid 1001) id 39F2C20AEEB6; Wed, 26 Aug 2015 18:38:46 +0100 (BST) Date: Wed, 26 Aug 2015 18:38:46 +0100 From: Matt Smith To: Slawa Olhovchenkov , freebsd-stable@freebsd.org Subject: Re: Buildworld failure on stable Message-ID: <20150826173846.GE85652@xtaz.uk> Mail-Followup-To: Matt Smith , Slawa Olhovchenkov , freebsd-stable@freebsd.org References: <20150826070125.GA85652@xtaz.uk> <20150826080920.GM3158@zxy.spb.ru> <20150826094829.GB85652@xtaz.uk> <20150826101045.GJ21849@zxy.spb.ru> <20150826112707.GC85652@xtaz.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20150826112707.GC85652@xtaz.uk> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2015 17:38:49 -0000 On Aug 26 12:27, Matt Smith wrote: >On Aug 26 13:10, Slawa Olhovchenkov wrote: >>>>Hardware error or memory exhausted >>> >>>It does appear to be something along those lines. It's not memory >>>exhaustion as it has around 2GB free at the point it fails. However I've >>>deleted /usr/obj and started the buildworld again and it failed in a >>>different place with the same error. I'm trying it again without -j4 to >>>see what happens. But isn't looking too good. :( >> >>Look like hardware error. >>RAM/CPU/MB > >Interestingly it *always* manages to succesfully compile clang etc and >it has no issues compiling things from ports. It fails compiling >something from lib like openssl or kerberos. Doesn't buildworld build >a bootstrap version of clang and then use that version to compile the >rest of it? I might try downgrading my sources back to the version >that I last succesfully compiled just to prove it one way or the other >to myself. > So, been doing some testing. It looks like a -j4 problem with the latest sources. If I buildworld with -j1 then it compiles with no issues at all. If I compile r286908 with -j4 then it compiles with no issues at all. If I try and compile r287155 with -j4 then I get the bus errors. So I'm not convinced at all that it's hardware related at the moment. -- Matt