From owner-freebsd-current@FreeBSD.ORG Tue Oct 4 13:03:45 2005 Return-Path: X-Original-To: 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 30DD716A41F; Tue, 4 Oct 2005 13:03:45 +0000 (GMT) (envelope-from mi@blue.virtual-estates.net) Received: from blue.virtual-estates.net (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id A14B843D46; Tue, 4 Oct 2005 13:03:44 +0000 (GMT) (envelope-from mi@blue.virtual-estates.net) Received: from blue.virtual-estates.net (blue [127.0.0.1]) by blue.virtual-estates.net (8.13.4/8.13.4) with ESMTP id j94D3hXO067063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Oct 2005 09:03:43 -0400 (EDT) (envelope-from mi@blue.virtual-estates.net) Received: (from mi@localhost) by blue.virtual-estates.net (8.13.4/8.13.4/Submit) id j94D3hQv067062; Tue, 4 Oct 2005 09:03:43 -0400 (EDT) (envelope-from mi) From: "Mikhail T." Message-Id: <200510041303.j94D3hQv067062@blue.virtual-estates.net> To: current@FreeBSD.org, openoffice@FreeBSD.org Date: Tue, 4 Oct 2005 09:03:43 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 13:03:45 -0000 This happened twice already -- I rebuilt the kernel after the first time. I'm currently running FreeBSD 6.0-BETA5 #7: Mon Oct 3 19:10:37 EDT 2005 This is a dual Xeon-PII @450MHz with 512Mb of memory. The OOo build progresses until it gets stuck on something like: if ( -e ../../../unxfbsd.pro/slo/provider.o) touch ../../../unxfbsd.pro/slo/provider.obj According to Ctrl-T, the active process is: load: 0.00 cmd: perl5.8.7 64983 [runnable] 0.00u 0.01s 0% 4868k but the machine is 100% idle. The build itself can be interrupted with Ctrl-C, but the subsequent access to the work-directory will somewhere. The first time `rm -rf' got hung. Now `find work/ -name provider.o' is hanging (after displaying work/OOo_2.0beta2/configmgr/unxfbsd.pro/slo/provider.o). The machine is otherwise usable. When rebooted after the first time this happened, the reboot hung too -- I had to cold-reset it and the filesystem hosting /usr/ports had to be fsck-ed. This last build log can be found at: http://aldan.algebra.com:8015/~mi/ooo-2.0-build.log.bz2 but I doubt, it is OOo-specific, although other heavy ports (like firefox or jdk14) built fine. -mi