From owner-freebsd-current  Thu Jul 18 13:06:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA13407
          for current-outgoing; Thu, 18 Jul 1996 13:06:44 -0700 (PDT)
Received: from ihgw1.att.com (ihgw1.att.com [207.19.48.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA13375
          for <freebsd-current@freebsd.org>; Thu, 18 Jul 1996 13:06:37 -0700 (PDT)
From: dob@naserver1.cb.lucent.com
Received: from nasvr1.cb.att.com by ihig1.att.att.com (SMI-8.6/EMS-1.2 sol2)
	id OAA01499; Thu, 18 Jul 1996 14:31:46 -0500
Original-From: dob@naserver1.cb.lucent.com
Received: from cbsky.cb.att.com by nasvr1.cb.att.com (5.x/EMS-L sol2)
	id AA17899; Thu, 18 Jul 1996 15:20:01 -0400
Received: by cbsky.cb.att.com (5.x/EMS-1.1 Sol2)
	id AA02888; Thu, 18 Jul 1996 15:19:29 -0400
Date: Thu, 18 Jul 1996 15:19:29 -0400
Message-Id: <9607181919.AA02888@cbsky.cb.att.com>
To: freebsd-current@freebsd.org
Subject: Re: panic on reboot with current -current - FOLLOWUP EMAIL
X-Sun-Charset: US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I hate to rain on anyone's parade, but my system panics with the current
> -current.

A follow up report to my previous report...

> I haven't been tracking all the changes since the last time we had VM 
> problems, but my officemate suggested I sup and get current before they put in
> gcc 2.7.3 so I did, but now I panic during reboot after making the world (and 
> making a kernel, reboot was to pick up the new kernel).  (I did it twice since
> I didn't capture the panic string the first time, thus seems to be 
> reproducible.)  
> 
> (Also panic's after making world without making new kernel.  Just this AM
> I halted the system after making world all night -- Kids play with PC during
> day so I don't *dare* leave it up :-)
> 
> panic: vm_page_free invalid wire count(2), pindex 0x6042
> 
> trace:
> 	_panic
> 	_vm_page_freechk_and_unqueue + 0x150
> 	_vm_page_free + 0x2d
> 	_vm_object_terminate + 0x12d
> 	_vm_object_deallocate + 0x1af
> 	_vn_vmio_close + 0x30
> 	_ffs_unmount + 0xac
> 	_dounmount + 0x90
> 	_ufs_unmountall + 0x41
> 	_boot + 0xf3
> 	_reboot + 0x29
> 
> Sup which fails: 07/03/96 15:33 EDT
> Sup which fails: 07/10/96 ~19:00 EDT
> 
> Sup which worked: 06/21/96 16:02 EDT
> 
> System specs the same.  8MB P75.  0K L2 cache.  Next week I'll move to 40MB of
> memory so these problems will probably disappear...  

Just added 32MB of memory (now at 40MB) and this problem has ``poof'' 
disappeared!  Sorry, John, but I'm no longer a valid VM code beta tester :-( 

Thanks,

Dan