From owner-freebsd-questions Mon Apr 12 10:57:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id D5D0214CF6 for ; Mon, 12 Apr 1999 10:57:12 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA21385; Mon, 12 Apr 1999 10:54:32 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 12 Apr 1999 10:54:32 -0700 (PDT) From: Doug White To: Greg Lehey Cc: Davis , freebsd-questions@FreeBSD.ORG Subject: Re: fatal trap! How do I escape? In-Reply-To: <19990410095012.X2142@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Greg Lehey wrote: > On Friday, 9 April 1999 at 16:09:26 -0700, Doug White wrote: > > On Fri, 9 Apr 1999, Davis wrote: > > > >> That did it; pcm0 was detected (as pcm1, of course). > >> BUT - several lines later (after the kernel loaded ep0, then npx0), I > >> received the following message: > >> > >> Fatal trap 12: page fault while in kernel mode > >> fault virtual address = 0x4 ^^^ > > I've had odd boot-time crashes like this. Based on the fault address I'd > > say it's a corrupted pointer. > > That's pretty good. How do you deduce that from the fault address? > That's the usual reason for a "page fault", of course. Well, it's looking for code in byte 4 of the kernel binary, which doesn't contain useful code. The solution: check your kernel config. Something you keyed in is wrong, or there is a device conflict. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message