Date: Sun, 1 Sep 2002 11:29:27 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Crash with KVM monitoring in place ... Message-ID: <200209011829.g81ITRWK014499@apollo.backplane.com> References: <20020901135655.L27764-100000@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:Okay, according to my logs, here is what I have:
:
:Aug 31 22:13:47 venus scrappy[35952]: Starting KVM Monitoring
:Aug 31 22:13:47 venus scrappy[35962]: kernel_vm_end: 0xf6400000
:Aug 31 23:00:03 venus scrappy[41669]: kernel_vm_end: 0xf6800000
:Sep 1 00:00:25 venus scrappy[50135]: kernel_vm_end: 0xf7000000
:
:Note that I modified my script so that it only reports to syslog when the
:value changes, instead of every minute ...
:
:On the other server, she's still running with:
:
:Sep 1 02:05:30 jupiter root[93918]: kernel_vm_end: 0xfa000000
:Sep 1 02:07:32 jupiter root[95929]: kernel_vm_end: 0xfa400000
:Sep 1 02:09:34 jupiter root[98699]: kernel_vm_end: 0xfa800000
:Sep 1 02:10:34 jupiter root[1076]: kernel_vm_end: 0xfac00000
:Sep 1 04:30:42 jupiter root[33295]: kernel_vm_end: 0xfb000000
:
:Both server(s) are running kernels updated to sources of last night.
:
:Next?
A kernel core is what is really needed. All I can suggest
without a kernel core is to perhaps turn on DDB and instead
of it crashing and rebooting you drop into DDB and do a
'trace'. If over several crashes it dies in the same place
then we at least have an idea where to look.
How large is your swap space, or your largest free partition?
-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?200209011829.g81ITRWK014499>