From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 13:25:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35F6916A4CE for ; Sun, 25 Jan 2004 13:25:43 -0800 (PST) Received: from bim01.bimmer-edv.at (s1ip3.bimmer-edv.at [213.133.101.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE6EC43D1D for ; Sun, 25 Jan 2004 13:25:41 -0800 (PST) (envelope-from freebsd.org@bimmer.at) Received: from localhost (bim01 [127.0.0.1]) by bim01.bimmer-edv.at (Postfix) with ESMTP id 1B2AC5F807B; Sun, 25 Jan 2004 22:25:41 +0100 (CET) Received: from bim01.bimmer-edv.at ([127.0.0.1]) by localhost (bim01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01690-01; Sun, 25 Jan 2004 22:25:10 +0100 (CET) Received: from chris (chello080110217205.114.11.wu-wien.teleweb.at [80.110.217.205]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by bim01.bimmer-edv.at (Postfix) with ESMTP id E02EF5F807D; Sun, 25 Jan 2004 22:25:09 +0100 (CET) From: "Christian B." To: "'Doug White'" Date: Sun, 25 Jan 2004 22:25:21 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20040125122226.J81485@carver.gumbysoft.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcPjgU7e0XbAXjN8T/+xfvaljZeTngACFSCQ X-Virus-Scanned: by amavisd-new at bimmer-edv.at cc: freebsd-current@freebsd.org Subject: RE: FreeBSD 5.2: malloc(): error: allocation failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 21:25:43 -0000 Hello Doug, thanks for your answer. > > First, I have FreeBSD 5.1 installed on my dual-Xeon machine > with 2GB RAM. > > Now, I delete the disk and installed FreeBSD 5.2 with the > same ports > > and configuration. > > Hm, you haven't been adjusting MAXDSIZ, have you? I've been > getting this exact same error sequence when I set MAXDSIZ so > big there was no space left for mmap() to work. In that case > I was setting it to near 3GB. > > Are you setting any tuning option in loader.conf or with a > custom kernel configuration? This effect is also with my custom kernel and with the GENERIC-kernel. The only setting in the loader.conf is: set console=comconsole and in the sysctl.conf: kern.ipc.somaxconn=4096 Have you another idea? thanks, regards, Christian