From owner-freebsd-bugs Mon Feb 24 8:10:16 2003 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CF5A37B401 for ; Mon, 24 Feb 2003 08:10:15 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC8B43FE9 for ; Mon, 24 Feb 2003 08:10:11 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h1OGAANS015668 for ; Mon, 24 Feb 2003 08:10:10 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h1OGAAbb015667; Mon, 24 Feb 2003 08:10:10 -0800 (PST) Date: Mon, 24 Feb 2003 08:10:10 -0800 (PST) Message-Id: <200302241610.h1OGAAbb015667@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Marc G. Fournier" Subject: Re: kern/48166: panic: pmap_new_proc: u_map allocation failed Reply-To: "Marc G. Fournier" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/48166; it has been noted by GNATS. From: "Marc G. Fournier" To: David Schultz Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/48166: panic: pmap_new_proc: u_map allocation failed Date: Mon, 24 Feb 2003 12:02:13 -0400 (AST) On Mon, 24 Feb 2003, David Schultz wrote: > I believe your problem here is having KVA_PAGES set too low. > (I take it this machine has lots of memory.) When you increase > KVA_PAGES, does the problem go away? > > Of course, you've discovered that all sorts of other > wonderful things happen when you change KVA_PAGES, but let's > work on one thing at a time. Right now, I'm not sure ... with KVA_PAGES up at 512, I'm still getting a 'nightly hang' ... as its a remote server, I asked the folks at Rackspace to do ctl-alt-esc and type 'panic', which worked, but I failed to tell them what to expect after typing panic, so when it started spewing a sequence of #'s at them (I use netdump to get my cores), they powercycled it, thinking there was a problem ... If/when it happens again tonight, I'll get them to let it finish and publish a new report ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message