From owner-freebsd-current Sat Mar 15 2:22: 8 2003 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 237E037B401 for ; Sat, 15 Mar 2003 02:22:07 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A0CC43F75 for ; Sat, 15 Mar 2003 02:22:06 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.8/8.12.8) with ESMTP id h2FAM3h8018130; Sat, 15 Mar 2003 11:22:03 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: "Lucky Green" Cc: freebsd-current@FreeBSD.ORG Subject: Re: ENOMEM error diagnosis? From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 14 Mar 2003 18:40:58 PST." <000001c2ea9c$52176d60$6601a8c0@VAIO650> Date: Sat, 15 Mar 2003 11:22:03 +0100 Message-ID: <18129.1047723723@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <000001c2ea9c$52176d60$6601a8c0@VAIO650>, "Lucky Green" writes: >I am seeing a lot of crashes of GBDE, causing "ENOMEM" errors to scroll >rapidly on the console. Whenever this happens, the server becomes >unresponsive to keyboard or any other input and has to be power cycled. >Is there some debug setting that I can set which would help diagnose the >problem further? This is on a minimally-loaded test machine with no >other users and no significant load from any services. Make sure you have rev 1.9 of src/sys/geom/bde/g_bde_crypt.c I hadn't done my math and before that rev gbde would request very large lumps of ram from malloc(9). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message