netbsd-5 locking panic

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

Hi,

on a pf based router upgraded to NetBSD 5.0_RC4 built from Friday's
sources, I saw the following crash (ahh, conserver...):


login:  [-- hf@localhost detached -- Fri Apr 24 19:08:22 2009]
Mutex error: mutex_vector_enter: locking against myself

lock address : 0x00000000ca204f80
current cpu  :                  0
current lwp  : 0x00000000ca207a00
owner field  : 0x00000000ca207a00 wait/spin:                0/0

panic: lock error
Begin traceback...
_prop_array_pool(c02734c3,1,c028b924,c028b7d0,c028052e,c02732fb,2,0,2001,0)
at 0xca204f80
Bad frame pointer: 0xc03d1a33
End traceback...
rebooting...


The kernel was built without debug options. There is no core dump, and
pflog left behind a file "pflog.bad.7e9c5e91", which has


[...]
2009-04-24 21:36:28.048023 rule 2/0(match): block in on vlan10:
130.83.228.108.4244 > 221.214.11.10.11153: UDP, length 41
2009-04-24 21:36:28.048044 rule 2/0(match): block in on vlan10:
130.83.228.108.4244 > 119.119.233.119.16909: UDP, length 43
2009-04-24 21:36:29.999078 rule 2..4294967040/0(match): block in/out on
vlan10: IP0 bad-hlen 0
1970-01-01 02:00:00.000000 [|pflog]
1970-01-01 02:00:00.000000 [|pflog]
1970-01-01 02:00:00.000000 [|pflog]
[...]

until EOF.

Does that speak to anyone?

        hauke

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