From owner-freebsd-alpha Mon Sep 11 8:40:15 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 ADDE637B423 for ; Mon, 11 Sep 2000 08:40:12 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA10592; Mon, 11 Sep 2000 08:40:10 -0700 Date: Mon, 11 Sep 2000 08:36:20 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: so much for *that* idea..... In-Reply-To: <14780.62432.185970.793919@grasshopper.cs.duke.edu> 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 On Mon, 11 Sep 2000, Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > I did a build from more or less top of tree- I had had a clean buildworld, so > > I built a kernel and did the installworld and did mergemaster and did > > disklabel -B, and got: > > <...> > > > halt code = 2 > > kernel stack not valid halt > > PC = 200000000 > > > > for my pains. Tsk. > > This typically means you're faulting very early in the boot process. > Thus is typically caused by trap'ing & then calling vm_map_lookup() > out of vm_fault() prior to setting up the vm maps. The > vm_map_lookup() faults & you get caught in an infinate recursion > ending in a ksp not valid. > > First thing I'd try is temporarily making the ALPHA_MMCSR_ACCESS case > in trap() always fatal for a kernel-mode trap. This should catch the > initial trap & give you a clue as to what's going wrong. Yup- that's a good trick to try. > Sorry for my delayed reply. My wife & I just moved into our new > place. No phone service yet, much less DSL. Blah. It wasn't delayed- not at all. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message