Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Jan 2005 10:49:52 -0600
From:      Eric F Crist <ecrist@secure-computing.net>
To:        "J.D. Bronson" <jbronson@wixb.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: help logging a crash
Message-ID:  <A480AC9E-67DE-11D9-8D05-000D9333E43C@secure-computing.net>
In-Reply-To: <6.2.0.14.2.20050116103645.00becec8@cheyenne.wixb.com>
References:  <6.2.0.14.2.20050116103645.00becec8@cheyenne.wixb.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Jan 16, 2005, at 10:38 AM, J.D. Bronson wrote:

> I am having random reboots on my 5.3 system
> even using GENERIC.
>
> I am wondering, what do I have to do to enable some sort of debug/crash
> log...I dont want the thing to just reboot w/o telling me why.
>
> When this happens, there are no logs...just a reboot and then the FSCK.
>
> I believe I need to compile some options into a kernel to trap this, 
> but dunno...where...
>
> Thanks in advance guys :)

If you enable debugging in the kernel, IIRC, you should have a dump 
file in the system root directory when the system crashes.  If you tell 
us a little more about the system you're using, such as hardware, 
specific services you're running, we might be able to tell you why it's 
crashing.  Also, the output of uname -a would be beneficial.

HTH
_______________________________________________________
Eric F Crist                  "I am so smart, S.M.R.T!"
Secure Computing Networks              -Homer J Simpson

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iEYEARECAAYFAkHqmzAACgkQRAAY9knOW+onGQCfRxplgb/gV69cmr8h/sBiB6lV
VB4An3ORpFLoNPhF1YLwQjO4wg169rLj
=uMjv
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A480AC9E-67DE-11D9-8D05-000D9333E43C>