Date: Thu, 22 Apr 1999 23:50:01 -0700 (PDT) From: "Daniel C. Sobral" <dcs@newsguy.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/11266: Page fault, fatal trap in kernel Message-ID: <199904230650.XAA12331@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/11266; it has been noted by GNATS. From: "Daniel C. Sobral" <dcs@newsguy.com> To: Nickolai Zeldovich <kolya@zepa.net> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/11266: Page fault, fatal trap in kernel Date: Fri, 23 Apr 1999 08:46:48 +0900 Nickolai Zeldovich wrote: > > On Thu, 22 Apr 1999, Daniel C. Sobral wrote: > > > 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. > > Well, at least I'm not the only one having the problem. I recompiled my > kernel without the MAXDSIZ and DFLDSIZ settings, lowering NMBCLUSTERS to > 2048 and setting maxusers to 90. The machine promptly crashed again, only > an hour after being rebooted with a new kernel. As you noted, NMBCLUSTERS might be too low. It is actually possible to crash the machine with now enough NMBCLUSTERS. Get a higher NMBCLUSTERS. Much higher. But keep maxusers at 90, just in case this crash is a new problem, and the former was caused by, indeed, mem/maxusers. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904230650.XAA12331>