From owner-freebsd-current  Mon Mar  6 05:29:40 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA05281 for current-outgoing; Mon, 6 Mar 1995 05:29:40 -0800
Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA05275 for <current@freebsd.org>; Mon, 6 Mar 1995 05:29:37 -0800
Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id IAA18554 for current@freebsd.org; Mon, 6 Mar 1995 08:29:30 -0500
Received: by starkhome.cs.sunysb.edu (8.6.10/1.34)
	id IAA03874; Mon, 6 Mar 1995 08:28:22 -0500
Date: Mon, 6 Mar 1995 08:28:22 -0500
From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark)
Message-Id: <199503061328.IAA03874@starkhome.cs.sunysb.edu>
To: davidg@Root.COM
CC: current@FreeBSD.org, dyson@Root.COM
In-reply-to: David Greenman's message of Sun, 05 Mar 1995 18:45:07 -0800 <199503060245.SAA00283@corbin.Root.COM>
Subject: Page fault panics during make world in -current 
Sender: current-owner@FreeBSD.org
Precedence: bulk

A little more info from my crash dump:

I notice that control has arrived at line 1005 in vfs_bio.c with "obj"
set to a VM object with ref_count = 0, even though the object was obtained
from vp->v_vmdata.  It seems wrong to have a pointer to a VM object
stored in a vnode without a positive reference count on the VM object.

The size field of the VM object also seems bogus: 0xf0668da4, though this
could perhaps be a consequence of the object's already having been freed
and the memory used for something else.

So, it looks like maybe there is a problem with the updating of the
reference counts when storing VM object pointers in vnodes.

							- Gene