From owner-freebsd-current  Tue Jul 21 23:00:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA13389
          for freebsd-current-outgoing; Tue, 21 Jul 1998 23:00:46 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13383
          for <current@freebsd.org>; Tue, 21 Jul 1998 23:00:41 -0700 (PDT)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id AAA03924;
	Wed, 22 Jul 1998 00:59:55 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199807220559.AAA03924@home.dragondata.com>
Subject: Re: panic: page fault while in kernel mode - from gcc
In-Reply-To: <199807220049.RAA22703@implode.root.com> from David Greenman at "Jul 21, 98 05:49:09 pm"
To: dg@root.com
Date: Wed, 22 Jul 1998 00:59:55 -0500 (CDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >I was able to make gcc produce this twice - then it wouldn't do it again:
> >
> >page fault while in kernel mode
> >
> >A trace shows:
> >
> >_zalloci
> >_get_pv_entry
> >_pmap_insert_entry
> >_pmap_enter
> >_vm_fault
> >_trap
> >calltrap()
> >--- trap 0xc, eip = 0xf01cd754, esp = 0xfaa9fe88, ebp = 0xfaa9fe88
> >_get_ptbase
> >_pmap_protect
> >_vm_map_copy_entry
> >_vmspace_fork
> >_vm_fork
> >_fork1
> >_vfork
> >_syscall
> >_Xsyscall
> >
> >This mean anything to anyone?
> 
>    This seems to indicate that the new process's page directory either hasn't
> been allocated yet or went away for some reason. Apparantly one of several
> new bugs that John has left us with.
> 

Is there any reason why someone doesn't back out his last few batches of
large vm changes? Apparently he was half done with some of it, and what we
had before seemed more stable than what we have now.

(although the NFS changes did really fix a lot of problems)

Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message