From owner-freebsd-current@FreeBSD.ORG  Tue Oct 12 17:25:15 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0389816A4CE
	for <current@freebsd.org>; Tue, 12 Oct 2004 17:25:15 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EBDBD43D3F
	for <current@freebsd.org>; Tue, 12 Oct 2004 17:25:14 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 9B01B72DD4; Tue, 12 Oct 2004 10:25:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id 9605072DCB;
	Tue, 12 Oct 2004 10:25:14 -0700 (PDT)
Date: Tue, 12 Oct 2004 10:25:14 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Maxim Konovalov <maxim@macomnet.ru>
In-Reply-To: <20041012154552.E60900@mp2.macomnet.net>
Message-ID: <20041012101849.U41628@carver.gumbysoft.com>
References: <20041012154552.E60900@mp2.macomnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: sparc64 kernel dump debug
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2004 17:25:15 -0000

On Tue, 12 Oct 2004, Maxim Konovalov wrote:

> [Bcc: sparc64@ ]
>
> Hello,
>
> Are there any ways to debug a kernel dump on sparc64?  On our SMP
> netra1440:

Did you mean Netra 1400? I don't see a Netra 1440 on sunsolve.

The 1400 is a quad-US2; looks like a 420R from the back (?)

> # strings vmcore.3 | grep panic
> panic: trap: fast data access mmu miss
> ...
>
> # kgdb kernel.debug vmcore.3 2>&1| more

Have you tried this with the kernel.debug in your kernel compile dir,
rather than the one that savecore thinks its getting?


-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org