Subject: Re: sparc64 -current kernel fails to boot
To: Michael Lorenz <firstname.lastname@example.org>
From: Andrew Doran <email@example.com>
Date: 12/21/2007 11:43:42
On Thu, Dec 20, 2007 at 11:57:24PM -0500, Michael Lorenz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Dec 20, 2007, at 23:07, Chris Ross wrote:
> >[Okay, one more time. Mac's Mail client doesn't protect .'s at the
> >start of a line. Oops!]
> >[bizarre. I swear I attached more output. :-/]
> > The remainder of the console log was:
> > .
> > .
> >nf at sbus0 slot 3 offset 0x7ff0 vector 4 ipl 6 not configured
> >pcons at mainbus0 not configured
> >wskbd0 at kbd0 mux 1
> >Mutex error: mutex_vector_enter: locking against myself
> >lock address : 0x00000000018a03b0
What's a 18a03b0 when it's at home then? Can you get a backtrace?
> >current cpu : 0
> >current lwp : 0x0000000001818940
> >owner field : 0x00ff070000000000 wait/spin: 0/1
> >panic: lock error
> >cpu0: kdb breakpoint at 1429a40
> >Stopped in pid 0.1 (system) at netbsd:cpu_Debugger+0x4: nop
> I've seen that on my U1, a kernel without LOCKDEBUG should work. Un
> the other hand - someone should fix the locking bug.
The trace above indicates that lockdebug isn't enabled.