From owner-freebsd-questions@FreeBSD.ORG Mon Aug 10 19:39:55 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 99EF3106564A for ; Mon, 10 Aug 2009 19:39:55 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 572198FC15 for ; Mon, 10 Aug 2009 19:39:54 +0000 (UTC) Received: from gate.ipt.ru ([194.62.233.123] helo=h30.sp.ipt.ru) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1Maain-000ApF-UD; Mon, 10 Aug 2009 23:39:53 +0400 To: Alex R References: <4A7FDA9E.6070906@mailinglist.ahhyes.net> <66403456@bb.ipt.ru> <4A807235.4090601@mailinglist.ahhyes.net> From: Boris Samorodov Date: Mon, 10 Aug 2009 23:39:53 +0400 In-Reply-To: <4A807235.4090601@mailinglist.ahhyes.net> (Alex R.'s message of "Tue\, 11 Aug 2009 05\:17\:09 +1000") Message-ID: <11033862@h30.sp.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org 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:39:55 -0000 On Tue, 11 Aug 2009 05:17:09 +1000 Alex R wrote: > 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. > Why might the system timer do this? I am confused. The thing that Well, there are too many possibilities here. Like some run an ntpdate command. If you have logs you may check them up. > ended up fixing it was completely rebuilding /usr/src (deleting the > dir and installing the system sources via csup again) Seems like the case I supposed. > 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. Hm, that is not good imho. Smells like hardware fault. > I ran memtest86 on this system for about 6 hours and after about 20 > passes, no errors reported. Memory is only one system component. A processor/disk may be overheated, coolers stopped, etc. A very good test is make world (one after another several times). -- WBR, bsam