Date: Thu, 29 Mar 2001 16:10:31 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Bernd Walter <ticso@mail.cicely.de> Cc: freebsd-alpha@freebsd.org Subject: Re: -current boot panic Message-ID: <15043.42183.306906.990732@grasshopper.cs.duke.edu> In-Reply-To: <20010329230022.B29139@cicely20.cicely.de> References: <20010329221942.A29139@cicely20.cicely.de> <15043.39496.927622.874793@grasshopper.cs.duke.edu> <20010329230022.B29139@cicely20.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter writes:
> > How about running gdb on the kernel (with symbols) and mapping
> > 0xfffffc00003f53d0 to a function & line number?
>
> Mmm - yes - sounds logical.
> I don't know how to do with gdb here is the relevant objdump -S output:
gdb kernel.debug
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "alpha-unknown-freebsd"...
(gdb) l *0xfffffc00003f53d0
> /*
> * The WITNESS-enabled diagnostic code.
> */
> static void
> witness_initialize(void *dummy __unused)
> {
> struct lock_object *lock;
> struct witness_order_list_entry *order;
> struct witness *w, *w1;
> int i;
Sounds like a problem with the witness code. I'd suggest grabbing
today's -current before going any further (you might have grabbed your
sources when jhb was in the middle of changing all the mutex/witness
code around). If that doesn't help, try disabling the WITNESS option
& seeing if that helps.
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15043.42183.306906.990732>