Date: Tue, 8 Mar 2005 12:04:23 -0500 (EST) From: "Mike Jakubik" <mikej@rogers.com> To: "Doug White" <dwhite@gumbysoft.com> Cc: freebsd-current@freebsd.org Subject: Re: Reproducible Panic with port iplog Message-ID: <4420.172.16.0.199.1110301463.squirrel@172.16.0.199> In-Reply-To: <20050307184301.S32508@carver.gumbysoft.com> References: <2861.172.16.0.199.1109814152.squirrel@172.16.0.199> <20050303015438.GF15329@obiwan.tataz.chchile.org> <2910.172.16.0.199.1109816379.squirrel@172.16.0.199> <20050304230723.T4084@carver.gumbysoft.com> <1646.172.16.0.199.1110049506.squirrel@172.16.0.199> <20050307184301.S32508@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White said: >> Typing "call doadump" in the kernel debugger does work. Is there no way >> to >> have the kernel automatically do a dump when the system panics and there >> is no debugger compiled in? > > That should be the default behavior if a dumpdev is set (in rc.conf with > "dumpdev" or manually with the dumpon(8) command). It does not seem to be for me. The system just stands there doing nothing after the panic, when there is no debugger built in the kernel. P.S. I have also submitted a PR for this. http://www.freebsd.org/cgi/query-pr.cgi?pr=78384
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4420.172.16.0.199.1110301463.squirrel>