Re: LOCKDEBUG panic when hitting the shutdown button

1 msg	Possible bug in 4.99.62 at the poweroff time
5 msg	crash in today's kernel: uvm_fault() in vfs_busy()
1 msg	new permission problem in full build
7 msg	i386 acpi panci
3 msg	MFS panic
2 msg	resize kills -current
3 msg	rpc.lockd
3 msg	locale LC_NUMERIC
4 msg	NetBSD on sd0 (memory) and CGD on wd0... succes...
2 msg	-current panics with mount_null(8)
3 msg	troubles with ipnat TCP entries
5 msg	Moving usr into cgd -- is it ok if i use 'cp -p...
4 msg	-current not building: prop_array.o
3 msg	file system problems

LOCKDEBUG panic when hitting the shutdown button
\ Sverre Froyen (6 May 2008)
. \ Juan RP (6 May 2008)
. . \ Sverre Froyen (6 May 2008)
. . . \ Juan RP (6 May 2008)
. . . . \ Juan RP (6 May 2008)
. \ Juan RP (6 May 2008)
. . \ Sverre Froyen (7 May 2008)

1 msg	build.sh ... release failed on amd64
7 msg	NetBSD in a camera
4 msg	'locking against myself' with sysmon_envsys/lib...
6 msg	network dysfunction
4 msg	By the way - was Re: Change from BSDL to GPL?

Subject:	Re: LOCKDEBUG panic when hitting the shutdown button
Group:	Netbsd-current-users
From:	Sverre Froyen
Date:	7 May 2008

On Tuesday 06 May 2008, Juan RP wrote:
> On Tue, 6 May 2008 13:43:01 -0600
>
> Sverre Froyen <sverre> wrote:
> > I'll be happy to test a patch.
>
> I fixed it once again, I missed prop_object_iterator_next() in my
> previous commit.
>
> Please make sure that you have these revisions:
>
> $NetBSD: prop_array.c,v 1.14 2008/05/06 22:57:26 xtraeme Exp $
> $NetBSD: prop_dictionary.c,v 1.26 2008/05/06 22:57:26 xtraeme Exp $

I did a cvs update in /usr/src/common/lib/libprop and received the following
new files:

-rw-r--r-- 1 root wheel 20305 May 6 19:42 prop_array.c
-rw-r--r-- 1 root wheel 11207 May 6 19:42 prop_dictionary.3
-rw-r--r-- 1 root wheel 33995 May 6 19:42 prop_dictionary.c
-rw-r--r-- 1 root wheel 13401 May 6 19:42 prop_object_impl.h

prop_array.c and prop_dictionary.c are the revisions specified above. I then
did a make in the kernel compile directory and tested the new kernel. The
panic is still there and it looks like the backtrace is identical (aside from
some address and line number changes):

#9 0xc0473ddd in panic (fmt=0xc09c2e93 "LOCKDEBUG")
at /usr/src/sys/kern/subr_prf.c:257
#10 0xc046d711 in lockdebug_abort1 (ld=0xce85f380, lk=0xc0ae0920,
func=0xc07c8ed6 "lockdebug_wantlock",
msg=0xc09c081d "locking against myself", dopanic=true)
at /usr/src/sys/kern/subr_lockdebug.c:799
#11 0xc0453133 in rw_vector_enter (rw=0xcc5cc128, op=RW_READER)
at /usr/src/sys/kern/kern_rwlock.c:297
#12 0xc079ce05 in prop_dictionary_iterator (pd=0xcc5cc120)
at /usr/src/sys/lib/libkern/../../../common/lib/libprop/prop_dictionary.c:774
#13 0xc079cec7 in _prop_dictionary_externalize (ctx=0xc329ba80, v=0xcc5cc120)
at /usr/src/sys/lib/libkern/../../../common/lib/libprop/prop_dictionary.c:413
#14 0xc079c017 in prop_dictionary_externalize (pd=0xcc5cc120)
at /usr/src/sys/lib/libkern/../../../common/lib/libprop/prop_dictionary.c:1135
#15 0xc0798c08 in _prop_object_copyout_ioctl (pref=0xce03bc60,
cmd=<value optimized out>, obj=0xcc5cc120)
at /usr/src/sys/lib/libkern/../../../common/lib/libprop/prop_kern.c:323
#16 0xc0119e03 in sysmonioctl_power (dev=17154, cmd=3221770241,
data=0xce03bc60, flag=5, l=0xce00a7e0)
at /usr/src/sys/dev/sysmon/sysmon_power.c:591
#17 0xc04bc5fa in spec_ioctl (v=0xce03bb50)
at /usr/src/sys/miscfs/specfs/spec_vnops.c:665
#18 0xc04b5ed2 in VOP_IOCTL (vp=0xce1aaf00, command=3221770241,
data=0xce03bc60, fflag=5, cred=0xcc5c5f00)
at /usr/src/sys/kern/vnode_if.c:562
#19 0xc04b3663 in vn_ioctl (fp=0xcdfa9b40, com=3221770241, data=0xce03bc60)
at /usr/src/sys/kern/vfs_vnops.c:624
#20 0xc047b27d in sys_ioctl (l=0xce00a7e0, uap=0xce03bd00, retval=0xce03bd28)
---Type <return> to continue, or q <return> to quit---
at /usr/src/sys/kern/sys_generic.c:616
#21 0xc051dbd0 in syscall (frame=0xce03bd48)
at /usr/src/sys/arch/i386/i386/syscall.c:102
#22 0xc0100514 in syscall1 ()