Re: kern/60444: repeatable mutex "locking against myself" panic
"Jeff Rizzo via gnats" <[email protected]>
| Newsgroups | gmane.os.netbsd.bugs |
|---|---|
| Message-ID | <[email protected]> |
The following reply was made to PR kern/60444; it has been noted by GNATS. From: Jeff Rizzo <[email protected]> To: [email protected] Cc: Subject: Re: kern/60444: repeatable mutex "locking against myself" panic Date: Mon, 13 Jul 2026 12:26:26 -0700 I just did a test with a -current (11.99.6) kernel; the issue persists and looks similar crashwise: [ 166.4109013] Mutex error: mutex_vector_enter,551: locking against myself [ 166.4109013] lock address : ffff92de2ef0e940 [ 166.4209012] current cpu : 1 [ 166.4209012] current lwp : 0xffff92de0cdef800 [ 166.4309006] owner field : 0xffff92de0cdef800 wait/spin: 0/0 [ 166.4409006] panic: lock error: Mutex: mutex_vector_enter,551: locking against myself: lock 0xffff92de2ef0e940 cpu 1 lwp 0xffff92de0cdef800 [ 166.4509004] cpu1: Begin traceback... [ 166.4509004] vpanic() at netbsd:vpanic+0x189 [ 166.4609004] panic() at netbsd:panic+0x3c [ 166.4709007] lockdebug_abort() at netbsd:lockdebug_abort+0x115 [ 166.4709007] mutex_vector_enter() at netbsd:mutex_vector_enter+0x392 [ 166.4809004] bridge_input() at netbsd:bridge_input+0xcf5 [ 166.4909003] vlan_input() at netbsd:vlan_input+0xd8 [ 166.4909003] ether_input() at netbsd:ether_input+0x70f [ 166.5009003] bridge_input() at netbsd:bridge_input+0xd14 [ 166.5109003] lagg_input_ethernet() at netbsd:lagg_input_ethernet+0x1f6 [ 166.5209002] if_percpuq_softint() at netbsd:if_percpuq_softint+0x9e [ 166.5309003] softint_dispatch() at netbsd:softint_dispatch+0x112 [ 166.5309003] DDB lost frame for netbsd:Xsoftintr+0x4c, trying 0xffff9894ab55c0f0 [ 166.5409002] Xsoftintr() at netbsd:Xsoftintr+0x4c [ 166.5509001] --- interrupt --- [ 166.5509001] 0: [ 166.5509001] cpu1: End traceback... [ 166.5509001] dumping to dev 168,8 (offset=8, size=18872056): [ 166.5609002] dump failed: insufficient space (4194304 < 9454053) [ 172.1808839] rebooting...