From owner-freebsd-alpha@FreeBSD.ORG Fri Aug 20 14:46:44 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18C4E16A4CE for ; Fri, 20 Aug 2004 14:46:44 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BBFD43D55 for ; Fri, 20 Aug 2004 14:46:43 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i7KEkabK054260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Aug 2004 17:46:37 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i7KEkc9u092678; Fri, 20 Aug 2004 17:46:38 +0300 (EEST) (envelope-from ru) Date: Fri, 20 Aug 2004 17:46:38 +0300 From: Ruslan Ermilov To: Garance A Drosihn Message-ID: <20040820144638.GA92603@ip.net.ua> References: <20040820101817.GE27931@ip.net.ua> <1092999187.9863.2.camel@builder02.qubesoft.com> <20040820105915.GA29178@ip.net.ua> <1093000460.9863.4.camel@builder02.qubesoft.com> <20040820120757.GC29568@ip.net.ua> <20040820135844.GA76070@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: alpha@freebsd.org Subject: Re: Alpha is seriously broken X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 14:46:44 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Garance, Did you read this thread before replying? :-) On Fri, Aug 20, 2004 at 10:37:01AM -0400, Garance A Drosihn wrote: > At 4:58 PM +0300 8/20/04, Ruslan Ermilov wrote: > >On Fri, Aug 20, 2004, Dag-Erling Sm?rgrav wrote: > > > Ruslan Ermilov writes: > >> > I think there's no emergency plan other than to reinstall "base" > >> > on these systems from some older snapshot? > >> > > > cross-compile on a different machine in the cluster, copy over > > > the new make(1), then use it to installworld over NFS. > > > >Only if this machine is also Alpha. To tell you the truth, some bits > >produced by cross-compiles on different architectures are not ready > >for use on a native architecture. This includes binary files such as > >fortune(6) .dat files, NLS catalogs, etc. I haven't identified them > >all yet. >=20 > If this machine has been getting rebuilt frequently, then maybe you > can just boot up kernel.old and have a working machine. >=20 The problem is not with the kernel, but with libc. Moreover, it affects all statically linked binaries, so recompiling libc will not help to recover. :-( > If that does not work, and would a cross-compile work well-enough to > generate a new library (if the problem is a library), or a new kernel > (if the error is in the kernel). Or maybe just generate dynamically- > linked versions of make & cc. Even if cross-builds are not good > enough to do a complete buildworld, might they work well enough to > recover from this with less work than a complete reinstall? >=20 All static binaries on these two systems crash. Log in to beast and give it a try. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBJg7OqRfpzJluFF4RAi1fAJ96lJ1+FtlcuRCWTO30+2BdyoAjoACfYjLk rnh4TCbu6sWoKVn2Zx3u028= =ND9f -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU--