From owner-freebsd-current  Sun Dec  1 14:16:42 2002
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 B365037B401; Sun,  1 Dec 2002 14:16:40 -0800 (PST)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AA14D43E88; Sun,  1 Dec 2002 14:16:39 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA03861;
	Sun, 1 Dec 2002 17:16:33 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gB1MG3V87599;
	Sun, 1 Dec 2002 17:16:03 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15850.35363.546311.924458@grasshopper.cs.duke.edu>
Date: Sun, 1 Dec 2002 17:16:03 -0500 (EST)
To: Kris Kennaway <kris@obsecurity.org>
Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: weird panic on alpha
In-Reply-To: <20021130223224.GC45105@rot13.obsecurity.org>
References: <20021130223224.GC45105@rot13.obsecurity.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


Kris Kennaway writes:
 > I'm getting this on several of my alphas.  Any ideas?  The traceback
 > and panic message is weird.

gdb sucks bigtime on alpha.  The weirdness is just gdb throwing its
hands up in the air because it doesn't understand the trapframe and
can't grok anymore of the stack than that.  gdb is useful for getting
stack traces from kernel panics on alpha only when a specific panic is
hit, not a trap.


So, you need to have ddb configured:
    options DDB
    options DDB_TRACE

and maybe:
    options DDB_UNATTENDED


Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message