Date: Sat, 31 Aug 2002 19:26:51 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Marc G. Fournier" <scrappy@hub.org> Cc: Arnvid Karstad <arnvid@karstad.org>, <bmah@FreeBSD.ORG>, <freebsd-stable@FreeBSD.ORG> Subject: Re: Problems with FreeBSD - causing zalloc to return 0 ?! Message-ID: <200209010226.g812Qptg011236@apollo.backplane.com> References: <20020831220710.D14642-100000@mail1.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:
: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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209010226.g812Qptg011236>