From owner-freebsd-bugs Sun May 31 16:50:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16456 for freebsd-bugs-outgoing; Sun, 31 May 1998 16:50:24 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16433 for ; Sun, 31 May 1998 16:50:22 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id QAA10140; Sun, 31 May 1998 16:50:02 -0700 (PDT) Date: Sun, 31 May 1998 16:50:02 -0700 (PDT) Message-Id: <199805312350.QAA10140@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Studded Subject: Re: i386/2431: panic: get_pv_entry: cannot get a pv_entry_t Reply-To: Studded Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/2431; it has been noted by GNATS. From: Studded To: freebsd-gnats-submit@freebsd.org, Tor.Egge@idt.ntnu.no Cc: Subject: Re: i386/2431: panic: get_pv_entry: cannot get a pv_entry_t Date: Sun, 31 May 1998 16:43:18 -0700 I am seeing this problem regularly on a 2.2.2-Release system with 256M of physical ram dedicated to a single process that regularly demands 200M. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message