From owner-freebsd-hackers Mon Feb 16 13:59:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12501 for freebsd-hackers-outgoing; Mon, 16 Feb 1998 13:59:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12423 for ; Mon, 16 Feb 1998 13:58:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA07811; Mon, 16 Feb 1998 13:27:37 -0800 (PST) Message-Id: <199802162127.NAA07811@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tor Egge cc: toor@dyson.iquest.net, freebsd@isvara.net, hackers@FreeBSD.ORG Subject: Re: VM messed: vm_page_free panic problem In-reply-to: Your message of "Mon, 16 Feb 1998 20:57:36 +0100." <199802161957.UAA07226@pat.idi.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Feb 1998 13:27:37 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > freebsd@isvara.net said: > > > Hi, > > > 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 > > > > > > There is clearly a problem with the VM subsystem, and there have been a > > > few messages posted here with people pointing this out. Since this stops > > > people installing the latest freebsd-current, it could be considered > > > quite important. > > > > > I'll try to look at it, but I am going to be very busy again next week. > > If someone else gets a chance to look into it, it would be helpful. > > vnode_pager_getpages first called ffs_getpages. ffs_getpages assumes > that the underlying device has a getpages operation, and performes > some operations (e.g. freeing the 4 last pages passed to ffs_getpages). > Then the VOP_GETPAGES routine returns EOPNOTSUPP, and ffs_getpages > returns this error code. In the case in question, this is to be expected. The MFS is supposed to be in the kernel image, but because the 4MB page covering the kernel is not correctly set up an early MFS operation causes a fatal fault. Your fix is probably correct in the general case, but it's not relevant here. Just for general reference though, with DISABLE_PSE in GENERIC the -current install disk image works again. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message