From owner-freebsd-current Tue May 21 16:23:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA10635 for current-outgoing; Tue, 21 May 1996 16:23:35 -0700 (PDT) Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA10608 for ; Tue, 21 May 1996 16:22:16 -0700 (PDT) Received: (from mark@localhost) by linus.demon.co.uk (8.7.5/8.7.3) id AAA00210 for freebsd-current@freebsd.org; Wed, 22 May 1996 00:21:17 +0100 (BST) Message-Id: <199605212321.AAA00210@linus.demon.co.uk> From: mark@linus.demon.co.uk (Mark Valentine) Date: Wed, 22 May 1996 00:21:17 +0100 X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: freebsd-current@freebsd.org Subject: panic: freeing held page Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk panic: freeing held page, count=4, pindex=0(0x0) This panic is from vm_free_page() in revision 1.72 of vm_object.c. Some more of the stack: _vm_free_page() _pmap_release() _vmspace_free() _cpu_wait() _wait1() _wait4() _syscall() Circumstances: I've had a few problems starting up X with the new VM code, sometimes hanging before olvwm starts up, sometimes after, sometimes getting SIGSEGVs from bash. The attempt before this panic gave me a window manager, but my xterms were hanging as they appeared (bash again). I CTL-ALT-BS'd out of the X server, and I had four bash processes in state R+ (I think: there may have been a small letter in there I forgot...), eating up CPU time. A straight "kill" on them had no effect; "kill -9" got me the panic. System: 486DX2/66, 16MB RAM, AHA1542C SCSI, ISA S3C801 video. Cheers, Mark. -- Mark Valentine at Home