From owner-freebsd-stable Mon Aug 10 20:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20081 for freebsd-stable-outgoing; Mon, 10 Aug 1998 20:05:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA20059 for ; Mon, 10 Aug 1998 20:05:00 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z64jj-0001UW-00; Mon, 10 Aug 1998 20:04:35 -0700 Date: Mon, 10 Aug 1998 20:04:32 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "David O'Brien" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash In-Reply-To: <19980810194311.A29027@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, David O'Brien wrote: > On Fri, Aug 07, 1998 at 10:20:59AM +0200, laurens van alphen wrote: > > > Fatal trap 12: page fault while in kernel mode > > Yet more VM panics. I'm at the point I can't even build the gcc28 port, > or even ``make install'' it if I get past the build of it. gdb "where" > output from From two different pannics are below. > > What's the next step to figuring out this problem? Well, since you are getting different kinds of panics, you should start by using some kind of error detecting memory. Either parity or ECC SIMM or DIMM modules will do, with a supporting motherboard. What you are seeing is almost certainly a hardware failure. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message