From owner-freebsd-hackers Fri Apr 2 11:34:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 5D3EE14EC9 for ; Fri, 2 Apr 1999 11:34:06 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id OAA26517; Fri, 2 Apr 1999 14:33:31 -0500 (EST) Message-Id: <199904021933.OAA26517@cs.rpi.edu> To: "Addr.com Web Hosting" Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Kernel panic question. In-Reply-To: Message from "Addr.com Web Hosting" of "Fri, 02 Apr 1999 11:25:33 PST." <4.1.19990402112404.0267b120@mail.addr.com> Date: Fri, 02 Apr 1999 14:33:31 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Recently I received the following kernel panic. I was wondering if anyone > has any thoughts or comments on this before I investigate further myself. > The system is a dual PII 400 with 1GB ram and an internal DPT raid > controller running several mirrored disks. Maxusers for the kernel is set > to 256, which I know is low, but anything above that makes the system > unstable (512 makes it panic every hour!). The system is running FreeBSD > 3.0-Release. The system is very stable in general, and is running high load > and with very diverse applications (http, https, sendmail, ftpd, ipop3d, > all the possible cgi scripts in this world and many more), however a panic > like this does occur once every few weeks. Sorry, no core dump for this > one, since I can't replicate the scenario. > Any help, comments or general information would be greatly appreciated. You have ben hit by the KVA issue. (WE *NEED* TO FIX THIS) It is tickled by a large ammount of RAM and/or a high maxusers, you have both. :I If you wish I can (via private email) step you through the patch for this, it is not complicated. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message