From owner-freebsd-current Sun Feb 15 02:19:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08315 for freebsd-current-outgoing; Sun, 15 Feb 1998 02:19:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isvara.net (root@[130.88.148.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08302 for ; Sun, 15 Feb 1998 02:19:51 -0800 (PST) (envelope-from freebsd@challenge.isvara.net) Received: from challenge.isvara.net ([130.88.66.5]) by isvara.net (8.8.7/8.8.7) with ESMTP id KAA00825 for ; Sun, 15 Feb 1998 10:19:36 GMT Message-ID: <34E6C14B.49A21738@challenge.isvara.net> Date: Sun, 15 Feb 1998 10:19:55 +0000 From: freebsd@isvara.net X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: FreeBSD Current Subject: Re: VM messed: vm_page_free panic problem References: <199802150658.XAA02323@usr02.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Terry Lambert wrote: > > > I'm experiencing a problem with the freebsd-current bootdisks since > > > a weeks ago. I get the error: > > > vm_page_free: pindex(12), busy(0), PG_BUSY(0), hold(0) > > > panic: vm_page_free: freeing page > Since John is snowed in... > > Is this "freeing free page" or "freeing busy page"? I'm not sure, the message above is all I get. > Are you using CCD? > Are you mounting async? > Are you trying to use union mounts, or any other FS other than FFS, > such as NFS, MSDOSFS, etc.? > Have you compiled your kernel -g, then copied it, "strip -d"'ed the > copy, and run on the stripped copy until you got a panic, so you could > do a source level debug of the kernel code in question? > > Have you traversed the scheduler queues in the kernel debugger to see > if the problem is really a process on two queues? > > Is vm_page_freechk_and_unqueue() (since it's probably "freeing ???? page") > being called from vm_page_free() or vm_page_free_zero()? > > When you look at the vm_object structure for the object that's failing, > is the "type" member OBJT_DEFAULT, OBJT_SWAP, OBJT_VNODE, OBJT_DEVICE, or > OBJT_DEAD? If OBJT_VNODE, is the backing_object member cast to a vnode > a device vnode, a directory, a file, or VNONE, or what? I am just getting the error from the bootdisk ATM, but compiling kernels a recent source works fine. > I'd ask for the -g kernel and dump image, but they are far in excess > of my account quota; unless you can put them up for FTP somewhere, and > I can pull them down on a faster-than-modem link, you're going to need > to go looking for yourself. Do *NOT* mail them to me! I could band the kernel and image on my server (155Mb ATM link to JANET via 10Mb Ethernet) > Terry Lambert > terry@lambert.org Thanx, Dan _____________________________________ Daniel J Blueman BSc Computation, UMIST, Manchester Email: blue@challenge.isvara.net Web: http://www.challenge.isvara.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message