From owner-freebsd-alpha Mon May 8 22:24:42 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C00C37BDA1; Mon, 8 May 2000 22:24:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA27964; Mon, 8 May 2000 22:23:28 -0700 Date: Mon, 8 May 2000 22:23:54 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: alpha@freebsd.org Subject: Re: borked Alpha boot loader? In-Reply-To: <200005090529.WAA17429@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm. Yes. Well, the last good working copy was April 30th for me. On Mon, 8 May 2000, Mike Smith wrote: > > > > setting affinity to the primary CPU > > jumping to bootstrap code > > Loading /boot/loader > > Console: SRM firmware console > > panic: zfree(0x2003cb58,4096): wild pointer > > > > halted CPU 0 > > > > halt code = 5 > > HALT instruction executed > > > > > > This has happened to two systems I did a buildworld on over the last 48 > > hours. Pretty annoying. Anyone with a clue here about this? > > This has hurt me too, which is why I fixed the loader install to save a > backup copy. I don't know what's up here yet, but I'm going to try to > find out fairly soon (have been somewhat buried in the 3ware driver, but > I seem to have hit a brick wall there). > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message