From owner-freebsd-amd64@FreeBSD.ORG  Tue Feb 22 06:08:53 2005
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D67F516A4CE
	for <amd64@freebsd.org>; Tue, 22 Feb 2005 06:08:53 +0000 (GMT)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1398E43D1F
	for <amd64@freebsd.org>; Tue, 22 Feb 2005 06:08:51 +0000 (GMT)
	(envelope-from scottl@samsco.org)
Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11])
	(authenticated bits=0)
	by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j1M69BOb046427;
	Mon, 21 Feb 2005 23:09:11 -0700 (MST)
	(envelope-from scottl@samsco.org)
Message-ID: <421ACBFF.6030606@samsco.org>
Date: Mon, 21 Feb 2005 23:06:55 -0700
From: Scott Long <scottl@samsco.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sean Chittenden <sean@gigave.com>
References: <20050221211056.GC826@sean.gigave.com>
In-Reply-To: <20050221211056.GC826@sean.gigave.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed 
	version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org
cc: amd64@freebsd.org
Subject: Re: Crash dumps not working correctly for amd64?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2005 06:08:53 -0000

Sean Chittenden wrote:
> Howdy.  I've got myself an interesting situation.  It seems as though
> amd64 is unable to collect crash dumps via savecore(8).  Has anyone
> else seen this?  From dmesg(1):
> 
> Checking for core dump on /dev/da0s1b ...
> savecore: first and last dump headers disagree on /dev/da0s1b
> Feb 21 12:45:59 host savecore: first and last dump headers disagree on /dev/da0s1b
> savecore: unsaved dumps found but not saved
> 
> ???  sys/amd64/amd64/dump_machdep.c and sys/i386/i386/dump_machdep.c
> are essentially identical.  I'm not familiar enough with these
> innards, but reviewing savecore(8) didn't point out anything obvious.
> I'm dumping onto a twa(4) controller.
> 
> Are there any known workarounds to get this info?  I'm tempted to turn
> off swap in fstab(5) that way the next time the machine comes up after
> a crash, it'll still have the dump in tact and could poke at it as
> time permitted.  Other suggestions?  -sc
> 

Can you modify savecore to dump the headers anyways so they can be 
inspected?

Scott