From owner-freebsd-current Sat Dec 4 7:56: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E1D2614FB6 for ; Sat, 4 Dec 1999 07:56:04 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id HAA09955; Sat, 4 Dec 1999 07:57:03 -0800 Date: Sat, 4 Dec 1999 07:57:03 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: -current no longer builds on the alpha In-Reply-To: <199912040846.JAA55879@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. > > > > > On Fri, 3 Dec 1999, Jordan K. Hubbard wrote: > > > > > > What is beast? I was happily able to build -current at about 5 this > > > > morning on a pc164. > > > > > > 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 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 was caused by one of the I/O boards (PALcode cannot go offboard to read registers on another board to find out what address was porked, IIRC)), or a 660 machine check, which is a panic. At any rate, this is a different entry point than mmu traps. It's not like I don't get sig-11s... ctags always seems to core dump on me- somewhere up in libc. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message