Re: netbsd-5 locking panic

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

At 19:17 Uhr +0000 26.4.2009, Andrew Doran wrote:
>On Sun, Apr 26, 2009 at 06:39:15PM +0200, Hauke Fath wrote:
>
>> 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
>
>In ddb:
>
>x/I 0x00000000c0126f2a
>x/I 0x00000000c0126fc2
>x/I 0x00000000c0292a4f
>
>... or use gdb/nm to figure out what the line and/or function is.
>
>(gdb) info line *0x12345678

Thanks for the hint. I'll do that tomorrow, unless I get a coredump earlier
- the console server is located behind the router, so breaking into ddb
does not do me any good while I am at home...

        hauke

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