Date: Wed, 1 Jun 2005 11:14:48 -0500 (CDT) From: Denny White <dennyboy@cableone.net> To: Greg 'groggy' Lehey <grog@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: System Panics and Core Dump help Message-ID: <20050601102547.Q1345@dualman.cableone.net> In-Reply-To: <20050601080952.GR35959@wantadilla.lemis.com> References: <20050531215354.F613@dualman.cableone.net> <20050601080952.GR35959@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Okay, didn't get a dump. Everything's fine on the system. I was just trying to follow how to be prepared for a panic, crash, etc., to be able to do a backtrace and have info to give someone trying to help debug the kernel. First time I rebooted after adding the new settings, I got: unable to open bounds file, using 0 no dumps found And to the best of my knowledge, there was no bounds file in /var/crash. Now there is, size is 2k & has an internal value of 5. Also, now when I boot, I get: Checking for core dump on /dev/amrd0s1b no dumps found And, after rebooting again, I see that the internal value of /var/crash/bounds has been incremented by 1, so now it's at 6. I read where it does that each time it checks it. Only reason I bugged anyone on the mailing list about this was I'm still a relative newbie & didn't want to trash all the work I'd done with my experimenting before getting it where it could be fixed if I did. :) So, as best as I can see it, it's doing just what it's supposed to do. Thanks for helping me clear that up, Greg. On Wed, 1 Jun 2005, Greg 'groggy' Lehey wrote: > On Wednesday, 1 June 2005 at 2:25:56 -0500, Denny White wrote: >> >> Just trying to get a heads up if I'm going about >> this in the right way, if I've understood what >> I've read and applied, outlined below. >> I read an article at Onlamp on how to prepare >> for system panics and core dumps. Article here: >> >> ... >> >> Now, in /var/log/messages, I get: >> >> savecore: unable to open bounds file, using 0 >> savecore: no dumps found > > Did you get a dump? Otherwise the second message is normal. The > first one is harmless, and should only occur on the first real dump. > >> Am I right in assuming that the system's doing exactly what it's >> supposed to do? That is, checking for a dump when booting, not >> finding any, reporting as much, and proceeding booting as usual? > > Assuming that you didn't write a dump, yes. > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply or reply to the original recipients. > For more information, see http://www.lemis.com/questions.html > The virus contained in this message was not detected. > > Finger grog@FreeBSD.org for PGP public key. > See complete headers for address and phone numbers. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCnd8Cy0Ty5RZE55oRAsYeAKCncUDXMAlnnT45hWHtn7TLK9/QdACeOVgQ rSSLP5BqgFAxeY5ICufJcrw= =QJke -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050601102547.Q1345>