From owner-freebsd-current Sat Mar 15 2:12:12 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 9DFE237B401 for ; Sat, 15 Mar 2003 02:12:10 -0800 (PST) Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB3CC43F75 for ; Sat, 15 Mar 2003 02:12:09 -0800 (PST) (envelope-from hiten@angelica.unixdaemons.com) Received: from angelica.unixdaemons.com (localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.8/8.12.1) with ESMTP id h2FAC2mq016990; Sat, 15 Mar 2003 05:12:02 -0500 (EST) Received: (from hiten@localhost) by angelica.unixdaemons.com (8.12.8/8.12.1/Submit) id h2FAC16c016989; Sat, 15 Mar 2003 05:12:01 -0500 (EST) (envelope-from hiten) Date: Sat, 15 Mar 2003 05:12:01 -0500 From: Hiten Pandya To: Lucky Green Cc: freebsd-current@FreeBSD.ORG Subject: Re: ENOMEM error diagnosis? Message-ID: <20030315101201.GA13145@unixdaemons.com> References: <000001c2ea9c$52176d60$6601a8c0@VAIO650> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c2ea9c$52176d60$6601a8c0@VAIO650> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD i386 X-Public-Key: http://www.pittgoth.com/~hiten/pubkey.asc X-URL: http://www.unixdaemons.com/~hiten X-PGP: http://pgp.mit.edu:11371/pks/lookup?search=Hiten+Pandya&op=index 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 Lucky Green (Fri, Mar 14, 2003 at 06:40:58PM -0800) wrote: > 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. I stumbled upon this problem when I was messing around with the swapoff() system call and /dev/md. If you do the following: # swapoff (one after another... # mdconfig -a -t swap -s 30M -u 3 # newfs /dev/md0 (nice unkillable loop) So, doing some research indicates that one way of fixing this problem was to detect if swap was available at all, in the md{start,done}_swap() routines, but not sure if that is the best fix. The ENOMEM error occurs in geom_io.c:g_io_deliver(). I have not familiarized myself with the GEOM code yet, but I could get a stack trace by just shoving panic() into g_io_deliver(). If you are running X or some sort of window system, you will not be able to use it, as Lucky Green said, it will be just hang. Going into DDB will not help because it hasn't crashed, and even doing so, will just give you a trace of the fork_trampoline(), ithd_loop() stuff... i.e. nothing which helps with the problem. The error looks like: "ENOMEM (0x) on (0x)..." in my case. Cheers. -- Hiten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message