From owner-freebsd-current@FreeBSD.ORG Fri Apr 27 23:22:49 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA00F16A403 for ; Fri, 27 Apr 2007 23:22:49 +0000 (UTC) (envelope-from tcumming123@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5B613C455 for ; Fri, 27 Apr 2007 23:22:49 +0000 (UTC) (envelope-from tcumming123@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so796965ana for ; Fri, 27 Apr 2007 16:22:48 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hiO6usPP3dOw0PrV/omPeaSvDjzbxPccHCITkox64qM4lUIvxAhQMkXkuSJQqQGS7Qc3nG731fHxi1CjYMMR5ITFj2M84I9563Ti8D48lmgmq63Is59fn4jI509q+kS2dghUwHPvNlfz+gG5+OmFI2M4YyMTScA5RsYe79lN+1c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=cc1rwb4fDIAgsCcilQOMj+UVMiukAKv/BQGd5vR9ts2W1FWq4J+17EzNMM5jaZQHV0U68a603UqO2/IX9rrQLpv21k63Eaup3nUUjthfojYlHyLmUcHq7cx92QL1vFhuH9FADp6Vu8ZFG7C4MaRC71UbV/49uDtXPRKD37crYLM= Received: by 10.114.150.1 with SMTP id x1mr1206382wad.1177716168125; Fri, 27 Apr 2007 16:22:48 -0700 (PDT) Received: by 10.114.159.16 with HTTP; Fri, 27 Apr 2007 16:22:48 -0700 (PDT) Message-ID: Date: Fri, 27 Apr 2007 16:22:48 -0700 From: "Tom Cumming" To: "Peter Jeremy" In-Reply-To: <20070427222116.GG840@turion.vk2pj.dyndns.org> MIME-Version: 1.0 References: <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> <20070427180021.GA57409@xor.obsecurity.org> <20070427222116.GG840@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org, Steve Kargl , Kris Kennaway Subject: Re: Panic on boot. How do I get a kernel dump. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2007 23:22:50 -0000 On 4/27/07, Peter Jeremy 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