From owner-freebsd-hackers  Fri Aug 29 05:50:59 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id FAA01429
          for hackers-outgoing; Fri, 29 Aug 1997 05:50:59 -0700 (PDT)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA01424
          for <hackers@FreeBSD.ORG>; Fri, 29 Aug 1997 05:50:52 -0700 (PDT)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA14584; Fri, 29 Aug 1997 08:50:18 -0400
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 29 Aug 1997 08:50 EDT
Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id IAA24967; Fri, 29 Aug 1997 08:32:23 -0400 (EDT)
Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id IAA03273; Fri, 29 Aug 1997 08:25:09 -0400 (EDT)
Date: Fri, 29 Aug 1997 08:25:09 -0400 (EDT)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199708291225.IAA03273@lakes.dignus.com>
To: ponds!FreeBSD.ORG!hackers, ponds!whistle.com!julian
Subject: Re: 2.2.2+ kernel panic
Content-Type: text
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


I just saw this from Julien...

> 
> what's wrong with this picture?
> 
> #0  boot (howto=260) at ../../kern/kern_shutdown.c:243
> #1  0xf010cfd2 in panic (fmt=0xf017158f "page fault")
>     at ../../kern/kern_shutdown.c:367
> #2  0xf01720f6 in trap_fatal (frame=0xefbffb20) at
> ../../i386/i386/trap.c:742
> #3  0xf0171be4 in trap_pfault (frame=0xefbffb20, usermode=0)
>     at ../../i386/i386/trap.c:653
> #4  0xf01718bf in trap (frame={tf_es = 16, tf_ds = 16, tf_edi =
> -260688384, 
>       tf_esi = 0, tf_ebp = -272630932, tf_isp = -272630968, 
>       tf_ebx = -260578816, tf_edx = 0, tf_ecx = -260888576, 
>       tf_eax = -260286976, tf_trapno = 12, tf_err = -260505600, 
>       tf_eip = -267219466, tf_cs = -266797048, tf_eflags = 65606, tf_esp
> = 0, 
>       tf_ss = -260578816}) at ../../i386/i386/trap.c:311
> #5  0xf0128df6 in vget (vp=0xf077e200, lockflag=1) at
> ../../kern/vfs_subr.c:817
> 
> See below..
> 
  ...

 where he goes on to note an issues in vfs_subr.c (curproc was NULL).

 I was wondering if anything has come of this - 2.2.2+ fixes particularly.
This is in the area of my "daily panics" - and I always have questions
when something like this pops up.

	 - Thanks -
	- Dave Rivers -