From owner-freebsd-questions Mon May 3 12:12: 1 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 2225615012 for ; Mon, 3 May 1999 12:11:58 -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 MAA22641; Mon, 3 May 1999 12:11:46 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 3 May 1999 12:11:46 -0700 (PDT) From: Doug White To: "Alok K. Dhir" Cc: Hostmaster@gcsl.com, freebsd-questions@FreeBSD.ORG Subject: RE: Fatel trap 12 In-Reply-To: <000101be9348$d95e0ae0$5438b5d8@net> 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 Fri, 30 Apr 1999, Alok K. Dhir wrote: > Why? Is there a known problem with 3.1 on DELL servers? No, 3.1 is sensitive to certain systems and configurations. It's an early release, I guess. I don't have the hrdware or time to debug this properly, so I'd either go with 2.2.8 or wait for 3.2 and see if that clears things up. > > > Iam trying to install 3.1 on a plain DELL server, it starts up on the > > > two disks fine I go through the kernel via the visual mode remove all > > > the conflicts and devices I don't have then quit and save. After it has > > > finished probing EISA then PCI and finding my devices then I get the > > > following Fatel trap. > > > > > > Fatel trap 12: page fault while in kernel mode > > > fault virtual address = 0xefc00000 > > > > I'm getting tired of this. > > > > Use 2.2.8. 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