From owner-freebsd-bugs Thu Apr 22 7:42:33 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BB71915AA4 for ; Thu, 22 Apr 1999 07:42:30 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id HAA71508; Thu, 22 Apr 1999 07:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 22 Apr 1999 07:40:02 -0700 (PDT) Message-Id: <199904221440.HAA71508@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Daniel C. Sobral" Subject: Re: kern/11266: Page fault, fatal trap in kernel Reply-To: "Daniel C. Sobral" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/11266; it has been noted by GNATS. From: "Daniel C. Sobral" To: Nickolai Zeldovich Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/11266: Page fault, fatal trap in kernel Date: Thu, 22 Apr 1999 23:29:40 +0900 Nickolai Zeldovich wrote: > > Close. 256MB memory, maxusers is set at 96 right now. Other things from > the kernel configuration: > options "MAXDSIZ=(384*1024*1024)" > options "DFLDSIZ=(384*1024*1024)" > options "NMBCLUSTERS=3072" 3.1-stable, for now, has a problem with large memory configurations when certain kernel sizes are set too high. Maxusers 96 ought to be safe, but your problems looks like the mem/max problem, only at a very slow rate. The problem derives from the kernel taking up more memory than it has space to map. Since this is gradually used, it takes a while for the problem to show up. One week is a long while, so you might be a borderline case, because of your other options. I suggest lowering maxusers to 90, and see if that eliminates the problem, or make your machine survive a while longer. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message