From owner-freebsd-bugs@FreeBSD.ORG Mon Aug 1 16:40:13 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org 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 EF2A916A41F for ; Mon, 1 Aug 2005 16:40:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2EAB43D53 for ; Mon, 1 Aug 2005 16:40:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j71GeDAG063412 for ; Mon, 1 Aug 2005 16:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j71GeDaY063411; Mon, 1 Aug 2005 16:40:13 GMT (envelope-from gnats) Date: Mon, 1 Aug 2005 16:40:13 GMT Message-Id: <200508011640.j71GeDaY063411@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: kern/84389: 4.11-STABLE stuck in kernel-space? X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2005 16:40:14 -0000 The following reply was made to PR kern/84389; it has been noted by GNATS. From: Kris Kennaway To: "Marc G. Fournier" Cc: Mark Blackman , freebsd-bugs@FreeBSD.org, freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/84389: 4.11-STABLE stuck in kernel-space? Date: Mon, 1 Aug 2005 12:35:53 -0400 On Sun, Jul 31, 2005 at 06:55:37PM -0300, Marc G. Fournier wrote: > > 'k, I don't know how much RAM you have on this machine ... but, on all of > ours, we have 4G, and to fix *our* vnode issue, I have to build the > kernel/world with: > > CFLAGS= -O -mpentium -pipe -g -DKVA_PAGES=512 > COPTFLAGS= -O -mpentium -pipe -DKVA_PAGES=512 FYI, that's a kernel option that should better go into your kernel config. Kris