From owner-freebsd-current Fri Jul 12 14:14:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16731 for current-outgoing; Fri, 12 Jul 1996 14:14:24 -0700 (PDT) Received: from hogw2.att.com ([204.179.186.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA16726 for ; Fri, 12 Jul 1996 14:14:21 -0700 (PDT) From: dob@naserver1.cb.lucent.com Received: from nasvr1.cb.att.com by hoig2.att.att.com (SMI-8.6/EMS-1.2 sol2) id HAA19178; Thu, 11 Jul 1996 07:24:40 -0400 Original-From: dob@naserver1.cb.lucent.com Received: from cbsky.cb.att.com by nasvr1.cb.att.com (5.x/EMS-L sol2) id AA14788; Thu, 11 Jul 1996 07:29:41 -0400 Received: by cbsky.cb.att.com (5.x/EMS-1.1 Sol2) id AA12874; Thu, 11 Jul 1996 07:29:13 -0400 Date: Thu, 11 Jul 1996 07:29:13 -0400 Message-Id: <9607111129.AA12874@cbsky.cb.att.com> To: freebsd-current@freebsd.org Subject: panic on reboot with current -current 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. 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... Thanks, Dan O'Brien Lucent Technologies, Bell Labs Innovations Columbus, OH USA