Re: netbsd-5 locking panic

[Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>]

At 16:25 Uhr +0200 26.4.2009, Hauke Fath wrote:
>I got a second one of these (identical) two hours ago, and rebooted with a
>DEBUG/DIAGNOSTIC/LOCKDEBUG enabled kernel. Let's see what comes of it.

login:   Mutex error: lockdebug_wantlock: locking against myself

lock address : 0x00000000ca264f80 type     :     sleep/adaptive
initialized  : 0x00000000c0292a4f
shared holds :                  0 exclusive:                  1
shares wanted:                  0 exclusive:                  1
current cpu  :                  0 last held:                  0
current lwp  : 0x00000000ca267a00 last held: 0x00000000ca267a00
last locked  : 0x00000000c0126f2a unlocked : 0x00000000c0126fc2
owner field  : 0x00000000ca267a00 wait/spin:                0/0

Turnstile chain at 0xc04a0f40.
=> No active turnstile for this lock.

panic: LOCKDEBUG
Begin traceback...
copyright(cc478583,0,0,ca267c54,c04a6140,c04a60d8,ca264f80,c045e810,ca267a00,c01
26f2a) at netbsd:__kernassert+0x51d6d
_prop_array_pool(c04a6100,0,0,cc4759d0,cc475440,cc4753d8,ca264e80,c045e804,0c02a
5b60) at 0xcc473340
ld_prime(cc475400,0,0,ca275cf4,cc4770c0,cc477058,ca264e00,c045e810,0,c02fb322) a
t netbsd:__kernassert+0xdd220
_prop_array_pool(cc477080,0,0,cc475090,cc478580,cc478518,ca264dc0,c045e804,0,c02
a70ed) at 0xcc476380
End traceback...
rebooting...

That was quick... At least a proper stack trace. I've switched on
kern.dump_on_panic so there should be a nice coredump soon.  =8/

        hauke

--
"It's never straight up and down"     (DEVO)