Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Apr 2007 16:22:48 -0700
From:      "Tom Cumming" <tcumming123@gmail.com>
To:        "Peter Jeremy" <peterjeremy@optushome.com.au>
Cc:        freebsd-current@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: Panic on boot. How do I get a kernel dump.
Message-ID:  <de193d070704271622o805ca68ja332a08139269420@mail.gmail.com>
In-Reply-To: <20070427222116.GG840@turion.vk2pj.dyndns.org>
References:  <de193d070704231519h671193emdd5f8673246559ad@mail.gmail.com> <de193d070704261535k11e5de1eh12842a4ab340a971@mail.gmail.com> <20070427012401.GZ2445@obelix.dsto.defence.gov.au> <20070427013742.GA51877@troutmask.apl.washington.edu> <20070427014317.GA17436@xor.obsecurity.org> <20070427030017.GA52347@troutmask.apl.washington.edu> <20070427031124.GA18527@xor.obsecurity.org> <de193d070704270831y6f57e559xfaf036338c263100@mail.gmail.com> <20070427180021.GA57409@xor.obsecurity.org> <20070427222116.GG840@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 4/27/07, Peter Jeremy <peterjeremy@optushome.com.au> wrote:

> 1) It is a production server that can't be left down for extended periods.


   Yup.  I.e., the dump provides a snapshot of the full state of the system
at the moment of the panic. This snapshot can be examined at leisure, a
customer could ftp the dump to a qualified engineer, etc.

2) It is a remote system without remote console access.


   .. or number 3) I can use my existing dump analysis tools and scripts to
examine the dump, and I cannot run the scripts from the console prompt.

Lets put the original question slightly differently:  How can the
> kernel state be saved if the kernel crashes before it's possible to
> invoke dumpon(8)?


I don't follow the geom code... is there a place in geom where I could put
something like, geom->dumpdev = "mydevice"?

Or ...
> Since dumpdev is now intertwined with geom and the geom tasting is
> quite late in the boot process, I agree that the current crashdump
> code does not seem amenable to use early in the boot process.

does  this mean even hard coding the dumpdev won't work? If so, then maybe
the, "your sol" statement is correct.

Thx, tom



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de193d070704271622o805ca68ja332a08139269420>