From owner-freebsd-alpha Tue May 9 10: 6:13 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 BB7AB37BE6A; Tue, 9 May 2000 10:06:09 -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 KAA29865; Tue, 9 May 2000 10:04:52 -0700 Date: Tue, 9 May 2000 10:05:20 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@freebsd.org Subject: Re: borked Alpha boot loader? In-Reply-To: <20000509095916.B28677@dragon.nuxi.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. Well, since I leave for three weeks on Thursday, I'll leave this problem for you && mike to sort out...:-) On Tue, 9 May 2000, David O'Brien wrote: > On Mon, May 08, 2000 at 10:12:27PM -0700, Matthew Jacob 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 > > I get the same. (well thought it was code 2) > Mike Smith and I have talked about it and couldn't immediately think of > which commit could have broken the loader. > > At the loader 10 sec count down, do: > > unload > load kernel.old > boot > > This works for me. Seems unloading and reloading a kernel "fixes" the > problem. Sometimes I am even able to load "kernel" after the unload and > have it boot. > > -- > -- David (obrien@NUXI.com) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message