Re: buildworld panic on ia64

From: Anton Shterenlikht <mexas_at_bristol.ac.uk>
Date: Tue, 7 Jul 2009 16:00:52 +0100
On Tue, Jul 07, 2009 at 09:45:54AM -0500, Dan Nelson wrote:
> In the last episode (Jul 07), Anton Shterenlikht said:
> > On Tue, Jul 07, 2009 at 11:50:58AM +0200, Rink Springer wrote:
> > > On Tue, Jul 07, 2009 at 10:48:08AM +0100, Anton Shterenlikht wrote:
> > > > panic: mtx_lock_spin() of destroyed mutex _at_ /usr/src/sys/ia64/ia64/trap.c:680
> > > > cpuid = 0
> > > > KDB: enter: panic
> > > > [thread pid 67078 tid 100097 ]
> > > > Stopped at      kdb_enter+0x92: [I2]    addl r14=0xffffffffffe2a8e8,gp ;;
> > > 
> > > Do you have a backtrace ?
> > 
> > no, sorry, I was too quick to reboot.
> > I tried to reproduce the error, got this on the way:
> 
> If you add "options KDB_TRACE" to your kernel config, you'll get a stack
> trace automatically on every panic.

actually, I'll rebuild a kernel first, and then try to rebuid world.
I'll put this in as well. Do I still need

options         KDB             # Enable kernel debugger support

if I put options KDB_TRACE?


> > 1 error
> > *** Error code 2
> > 1 error
> > *** Error code 2
> > 1 error
> 
> There are no errors in this output; just make reporting that there was an
> error.  At -j6, the error message itself may be hundreds of lines back. 
> Make lets all remaining parallel jobs finish before exiting.

ok, thanks, will keep in mind.

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 928 8233 
Fax: +44 (0)117 929 4423
Received on Tue Jul 07 2009 - 13:00:59 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:51 UTC