From owner-freebsd-current Sat Dec 4 13:24:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5CB1F151A7 for ; Sat, 4 Dec 1999 13:24:26 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA32507; Sat, 4 Dec 1999 22:04:15 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA81924; Sat, 4 Dec 1999 17:11:31 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912041611.RAA81924@yedi.iaf.nl> Subject: Re: -current no longer builds on the alpha In-Reply-To: from Matthew Jacob at "Dec 4, 1999 7:57: 3 am" To: mjacob@feral.com Date: Sat, 4 Dec 1999 17:11:31 +0100 (CET) Cc: jkh@time.cdrom.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matthew Jacob wrote ... > > As Matthew Jacob wrote ... > > > > > > Q'uelle strange- what I have... well, we'll see what my nightly build > > > brings... > > > > Mine fell over in 'truss'. I already reported it to Marcel, looks > > like something was changed in kdump/mkioctls, a script that 'truss' also > > uses. > > Mine's still going (I start mine at 0430 PST8PDT, the update from > freefall runs at 0107 PST8PDT)).... Nope, what a coincidence. It *just* > finished. Went all the way through w/o errors on a buildworld. My buildworld is OK now. Minor snag in the truss Makefile that Marcel committed already. > > > > It's an Aspen systems DEC Durango PC164 motherboard based system. > > > > Doesn't that one have ECC memory (refering to a previous post where > > you theorised a bit on memory problems and sig-11s ;) > > It may or may not, but memory problems are typically detected pretty well Right, that is my experience. > on alphas and you'll get a 670 machine check if it was recoverable (which > the PALcode has already done, except for TurboLaser if the memory problem I don't have TL :) Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message