From owner-freebsd-bugs@FreeBSD.ORG  Sun Jul 27 16:04:04 2008
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CB12C106566C;
	Sun, 27 Jul 2008 16:04:04 +0000 (UTC)
	(envelope-from gavin@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id A60268FC16;
	Sun, 27 Jul 2008 16:04:04 +0000 (UTC)
	(envelope-from gavin@FreeBSD.org)
Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m6RG44vM044265;
	Sun, 27 Jul 2008 16:04:04 GMT
	(envelope-from gavin@freefall.freebsd.org)
Received: (from gavin@localhost)
	by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m6RG44LT044261;
	Sun, 27 Jul 2008 16:04:04 GMT (envelope-from gavin)
Date: Sun, 27 Jul 2008 16:04:04 GMT
Message-Id: <200807271604.m6RG44LT044261@freefall.freebsd.org>
To: kirk@strauser.com, gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: gavin@FreeBSD.org
Cc: 
Subject: Re: kern/126002: Installing java/diablo-jdk15 crashes an amd64
	machine
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jul 2008 16:04:04 -0000

Synopsis: Installing java/diablo-jdk15 crashes an amd64 machine

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Sun Jul 27 15:55:56 UTC 2008
State-Changed-Why: 
Also, if you still have hte camera image and can transcribe the
information you missed out, that may be of use.  Take the value
of "instruction pointer" and use:
addr2line -e /boot/kernel/kernel.symbols 0x<address>
There is a possibility that this might give enough information
to begin to guess what caused this.  Otherwise, Kris's suggestion
of recompiling wiuth DDB and obtaining a backtrace is best if you
can recreate this panic, however.

http://www.freebsd.org/cgi/query-pr.cgi?pr=126002