From owner-freebsd-stable Sat Aug 31 19:41:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F63037B400; Sat, 31 Aug 2002 19:41:08 -0700 (PDT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCE9043E4A; Sat, 31 Aug 2002 19:41:07 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 298C02CC7F0; Sat, 31 Aug 2002 23:41:06 -0300 (ADT) Date: Sat, 31 Aug 2002 23:41:06 -0300 (ADT) From: "Marc G. Fournier" To: Matthew Dillon Cc: Arnvid Karstad , , Subject: Re: Problems with FreeBSD - causing zalloc to return 0 ?! In-Reply-To: <200209010226.g812Qptg011236@apollo.backplane.com> Message-ID: <20020831234019.R14885-100000@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Okay, well, both apear to have stablized at: Aug 31 21:36:25 jupiter root[31544]: $1 = 0xf6800000 Aug 31 21:37:26 jupiter root[31630]: $1 = 0xf6800000 Aug 31 21:38:26 jupiter root[31694]: $1 = 0xf6800000 Aug 31 21:39:26 jupiter root[31744]: $1 = 0xf6800000 Aug 31 21:40:27 jupiter root[32226]: $1 = 0xf6800000 and Aug 31 21:35:47 venus scrappy[23584]: $1 = 0xf5c00000 Aug 31 21:36:47 venus scrappy[23715]: $1 = 0xf5c00000 Aug 31 21:37:47 venus scrappy[23790]: $1 = 0xf5c00000 Aug 31 21:38:48 venus scrappy[23826]: $1 = 0xf5c00000 Aug 31 21:39:48 venus scrappy[23925]: $1 = 0xf5c00000 but will leave the processes running until next crash to see if that changes at all ... On Sat, 31 Aug 2002, Matthew Dillon wrote: > > : > :jupiter# tail -f /var/log/server_watch > :Aug 31 20:12:46 jupiter root[8902]: $1 = 4055891968 > :Aug 31 20:13:47 jupiter root[9548]: $1 = 4060086272 > : > :Anything I might want to add to that script, or is the kernel_vm_end the > :only thing that is useful at this point? > > set radix 0x10 > > (kgdb) set radix 0x10 > Input and output radices now set to decimal 16, hex 10, octal 20. > (kgdb) print kernel_vm_end > $1 = 0xe9000000 > > ^^^^^^^^^^ > this is a normal looking value. KVM is 0xC0000000 - 0xFFFFFFFF. > > If kernel_vm_end reaches 0xFFC00000 (or somewhere very close to > that), then you have run out of KVM. > > Typically the KVM high address progresses slowly and then stabilizes > (no longer progresses). If the KVM high address continues to progress > and the system eventually runs out of KVM, BOOM. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message