From owner-freebsd-stable Fri Aug 7 10:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10756 for freebsd-stable-outgoing; Fri, 7 Aug 1998 10:17:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (user-37kbmvg.dialup.mindspring.com [207.69.219.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10718 for ; Fri, 7 Aug 1998 10:16:59 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost.mindspring.com [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id NAA29648; Fri, 7 Aug 1998 13:17:45 -0400 (EDT) (envelope-from dex@wankers.net) Date: Fri, 7 Aug 1998 13:17:44 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: laurens van alphen cc: Gary Kline , freebsd-stable@FreeBSD.ORG Subject: RE: 2.2.6 page fault (Prev: Re: 2.2.7 crash) In-Reply-To: <000101bdc1dc$4f08bae0$0a00a8c0@uptight.student.utwente.nl> 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 Fri, 7 Aug 1998, laurens van alphen wrote: > > Fatal trap 12: page fault while in kernel mode > > today i got the same error when the box was pretty idle: > > > fault virtual address = 0x12a > > fault code = supervisor read, page not present > > intstruction pointer = 0x8:0xf01182b7 > > stack pointer = 0x10:0xefbffb5c > > frame pointer = 0x10:0xefbffb7c > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 11 (fsck) > > interupt mask = > > panic: page fault > > those address might have been different, i can't read THAT quickly ;) > > > syncing disks... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up > > it probably did that correctly though... > this is our first freebsd box (2.2.7) and has been runnin' in an testenv. > for a few weeks now. > > cheers, If you could replicate this, and we could debug a bit, it'd help...at least it didn't double fault, though...for a while when I was working on Solaris 2.6 x86, we were double faulting during specific tests...talk about a nightmare to trace... -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message