NetBSD-10.0 nfs_rcvlock: panic: lock error: Mutex: mutex_vector_enter,548: locking against myself

This happened when I ran a binary that was on an NFS mount (it happened
to be one I had built with "-sanitizer=address" -- I'm not sure what
sysctl call was being made).  It's not easily repeatable, so far.

Has this been reported before?  I didn't find any similar looking posts.

It happened on an ancient Dell PE2650 (Xeon i386) where I'm still
running stock 10.0 for testing.

NetBSD once 10.0_STABLE NetBSD 10.0_STABLE (GENERIC) #0: Thu Aug  8 07:34:54 UTC 2024  [email protected]:/usr/src/sys/arch/i386/compile/GENERIC i386

Mutex error: mutex_vector_enter,548: locking against myself

lock address : ccb12ac0
current cpu  :                  3
current lwp  : 0x00000000cfcad0c0
owner field  : 0x00000000cfcad0c0 wait/spin:                0/0

panic: lock error: Mutex: mutex_vector_enter,548: locking against myself: lock 0xccb12ac0 cpu 3 lwp 0xcfcad0c0
cpu3: Begin traceback...
vpanic(c126c944,eadef904,eadef9b4,c0cb620f,c126c944,c1269070,c116965c,224,c126903f,ccb12ac0) at netbsd:vpanic+0x196
panic(c126c944,c1269070,c116965c,224,c126903f,ccb12ac0,3,cfcad0c0,c116965c,31626363) at netbsd:panic+0x18
lockdebug_abort(c116965c,224,ccb12ac0,c14b2c44,c126903f,cfcad0c0,cfcad0c0,eadefa40,c0c7b622,c126903f) at netbsd:lockdebug_abort+0x11f
mutex_abort(c126903f,0,c0cf1bb1,0,c95f2b00,0,0,cfcad0c0,0,0) at netbsd:mutex_abort+0x2f
mutex_vector_enter(ccb12ac0,c69dbe00,0,c7844000,eadefa90,c0bb7148,cfcad0c0,eadefa74,0,1000000) at netbsd:mutex_vector_enter+0x33b
sigpending1(cfcad0c0,eadefa74,0,1000000,c7844004,0,0,cfcad0c0,c95f2b00,0) at netbsd:sigpending1+0x20
nfs_rcvlock(c7844000,c69dbe00,c95f2b00,c69dbe00,cfcad0c0,0,eadefb4c,0,c6d3d500,24) at netbsd:nfs_rcvlock+0xbb
nfs_request(c8cfb2b8,c6d3d500,4,cfcad0c0,c67e6340,eadefbf4,eadefbf8,eadefbec,0,c6d3d600) at netbsd:nfs_request+0x386
nfs_access(eadefc24,0,140,c116c9d0,c8fc5580,140,c67e6340,c8fc5580,eadefd54,c0d022e3) at netbsd:nfs_access+0x1e0
VOP_ACCESS(c8fc5580,140,c67e6340,c64cd068,0,40,0,1,0,0) at netbsd:VOP_ACCESS+0x63
getcwd_common(c7124c80,c6466740,eadefd80,c64cd068,ff,1,cfcad0c0,c64cd268,cf2af040,c64cd25a) at netbsd:getcwd_common+0x263
vnode_to_path(c64cd068,200,c9342580,cfcad0c0,cf2af040,0,c6516708,c64cd000,c6516704,6bb1) at netbsd:vnode_to_path+0xb5
sysctl_vmproc(eadeff04,3,bb0c1000,eadefef8,0,0,eadefefc,cfcad0c0,c5e84304,f000) at netbsd:sysctl_vmproc+0x625
sysctl_dispatch(eadefefc,5,bb0c1000,eadefef8,0,0,eadefefc,cfcad0c0,c5e84304,eb00) at netbsd:sysctl_dispatch+0x99
sys___sysctl(cfcad0c0,eadeff68,eadeff60,c79bb300,3,ca,eadeff60,eadeff68,0,0) at netbsd:sys___sysctl+0xda
syscall() at netbsd:syscall+0x1d6
--- syscall (number 202) ---
bb461857:
cpu3: End traceback...

Unfortunately I didn't have enough free space in /var/crash on that
machine so the dump was not saved.  I will probably reinstall it with
NetBSD-11 soon and if I do I'll try to remember to give /var more space,
but in the mean time I've set savecore_dir to point to another
filesystem with more free space.

--
					Greg A. Woods <[email protected]>

Kelowna, BC     +1 250 762-7675           RoboHack <[email protected]>
Planix, Inc. <[email protected]>     Avoncote Farms <[email protected]>

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCaNxg1QAKCRBmfXG3eL/0
f+cHAJ9ER2Irxqz4T51GSclLoFwxNhgHXACdFh3xBWj2/nQCHsHqBCJHaP7uEt0=
=bGMD
-----END PGP SIGNATURE-----