I was doing some small background builds and tests of a project on my "nbday" machine that I had just upgraded with the 20260805095105Z daily build and I noticed the xload window for it had disappeared. I found this on the console: [ 6123.1695877] panic: lock error: Mutex: mutex_vector_enter,551: locking against myself: lock 0xffff8c800d63e280 cpu 0 lwp 0xffff8c800c922000 [ 6123.1695877] cpu0: Begin traceback... [ 6123.1695877] vpanic() at netbsd:vpanic+0x164 [ 6123.1695877] panic() at netbsd:panic+0x3c [ 6123.1695877] lockdebug_abort() at netbsd:lockdebug_abort+0x10f [ 6123.1695877] mutex_vector_enter() at netbsd:mutex_vector_enter+0x2f5 [ 6123.1695877] sigpending1() at netbsd:sigpending1+0x24 [ 6123.1695877] nfs_rcvlock() at netbsd:nfs_rcvlock+0xed [ 6123.1695877] nfs_request() at netbsd:nfs_request+0x48e [ 6123.1817135] nfs_access() at netbsd:nfs_access+0x30b [ 6123.1817135] VOP_ACCESS() at netbsd:VOP_ACCESS+0x55 [ 6123.1817135] getcwd_common() at netbsd:getcwd_common+0x2bd [ 6123.1817135] vnode_to_path() at netbsd:vnode_to_path+0xbb [ 6123.1817135] sysctl_vmproc() at netbsd:sysctl_vmproc+0x71c [ 6123.1817135] sysctl_dispatch() at netbsd:sysctl_dispatch+0xb3 [ 6123.1817135] sys___sysctl() at netbsd:sys___sysctl+0xca [ 6123.1817135] syscall() at netbsd:syscall+0x98 [ 6123.1817135] --- syscall (number 202) --- [ 6123.1817135] netbsd:syscall+0x98: [ 6123.1817135] cpu0: End traceback... I haven't found any obvious posts that seem to be related. Is this worth a send-pr, or is it already known? -- Greg A. Woods <gwoods%acm.org@localhost> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpctkSyJAFNA.pgp
Description: OpenPGP Digital Signature