From owner-freebsd-questions@FreeBSD.ORG Mon Aug 10 19:17:14 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 39F39106564A for ; Mon, 10 Aug 2009 19:17:14 +0000 (UTC) (envelope-from alex@mailinglist.ahhyes.net) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.freebsd.org (Postfix) with ESMTP id B1DE58FC15 for ; Mon, 10 Aug 2009 19:17:13 +0000 (UTC) Received: from [192.168.1.104] (c211-30-26-44.rivrw2.nsw.optusnet.com.au [211.30.26.44]) by mail08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n7AJH9TM027933 for ; Tue, 11 Aug 2009 05:17:11 +1000 Message-ID: <4A807235.4090601@mailinglist.ahhyes.net> Date: Tue, 11 Aug 2009 05:17:09 +1000 From: Alex R User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4A7FDA9E.6070906@mailinglist.ahhyes.net> <66403456@bb.ipt.ru> In-Reply-To: <66403456@bb.ipt.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: installworld fails on 7.2-RELEASE/amd64 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: Mon, 10 Aug 2009 19:17:14 -0000 Boris Samorodov wrote: > On Mon, 10 Aug 2009 18:30:22 +1000 Alex R wrote: > > >> /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o >> boot2.ld -P 1 boot2.bin >> btxld:No such file or directory >> *** Error code 1 >> > > This error (not only with btxld but with some random file) often > occures when the system timer has been changed (imho stepped back) > while the system is building/installing world. World rebuilding > helps in that case. > > Hi Boris, Why might the system timer do this? I am confused. The thing that ended up fixing it was completely rebuilding /usr/src (deleting the dir and installing the system sources via csup again) It's a new computer so perhaps there is some compatibility problem or fault with the machine? During a couple of port builds, I noticed a few processes relating to the build of a port had died with signal 10 in dmesg (bus error i think this means), and during a build of apache, something called confcheck had died with signal 12. I ran memtest86 on this system for about 6 hours and after about 20 passes, no errors reported.