From owner-freebsd-hackers Thu Dec 13 4:28:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apache.metrocom.ru (www.metrocom.ru [195.5.128.139]) by hub.freebsd.org (Postfix) with ESMTP id C93BB37B41D for ; Thu, 13 Dec 2001 04:28:39 -0800 (PST) Received: from apache.metrocom.ru (apache.metrocom.ru [195.5.128.150]) by apache.metrocom.ru (8.12.1/8.12.1) with ESMTP id fBDCSYmf012776; Thu, 13 Dec 2001 15:28:34 +0300 (MSK) Date: Thu, 13 Dec 2001 15:28:34 +0300 (MSK) From: Varshavchick Alexander To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4G phisical memory kernel trap - the solution In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 5 Dec 2001, Varshavchick Alexander wrote: > Thank you Dan, can you please give a more detailed description as how to > do it? > > > You can run a 4.4 kernel on a 4.2 userland with no problem. On some of > > my production boxes, I'm running a 4.4 kernel on a 4.0 userland :) You > > should be able to build a 4.4 kernel, copy it to /kernel.test, and do a > > quick reboot to see if it works. That way you can fall back to the 4.2 > > kernel if you have problems. > > > > -- > > Dan Nelson > > dnelson@allantgroup.com The system itself worked with 4.4 stable kernel on a 4.2 userland, but the apache experienced problems in killing unused processes - the apache processes stacked to the MaxProcess number and just sat there. So I upgraded the whole system to 4.4 after it, and it all worked without problems with 4G phisical memory. My big thanks to all who helped in solving this issue! Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)118-3322, 118-3115(fax) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message