Re: kern/60444: repeatable mutex "locking against myself" panic

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: Sun, 12 Jul 2026 20:36:00 -0700

 I verified that creating the bridges in the other order (vlan600 before 
 lagg0) yields a very similar crash:
 
 [ 9917.1289071] Mutex error: mutex_vector_enter,551: locking against myself
 
 [ 9917.1389070] lock address : ffff81232f282500
 [ 9917.1489066] current cpu  :                  1
 [ 9917.1489066] current lwp  : 0xffff81218516e000
 [ 9917.1589066] owner field  : 0xffff81218516e000 wait/spin:         0/0
 
 [ 9917.1589066] panic: lock error: Mutex: mutex_vector_enter,551: 
 locking against myself: lock 0xffff81232f282500 cpu 1 lwp 0xffff81218516e000
 [ 9917.1789065] cpu1: Begin traceback...
 [ 9917.1789065] vpanic() at netbsd:vpanic+0x171
 [ 9917.1889067] panic() at netbsd:panic+0x3c
 [ 9917.1989064] lockdebug_abort() at netbsd:lockdebug_abort+0x114
 [ 9917.1989064] mutex_vector_enter() at netbsd:mutex_vector_enter+0x397
 [ 9917.2089065] bridge_input() at netbsd:bridge_input+0xaaf
 [ 9917.2189064] vlan_input() at netbsd:vlan_input+0x165
 [ 9917.2189064] ether_input() at netbsd:ether_input+0x2d2
 [ 9917.2289067] bridge_input() at netbsd:bridge_input+0xace
 [ 9917.2389066] lagg_input_ethernet() at netbsd:lagg_input_ethernet+0x20c
 [ 9917.2489066] if_percpuq_softint() at netbsd:if_percpuq_softint+0x9e
 [ 9917.2489066] softint_dispatch() at netbsd:softint_dispatch+0x95
 [ 9917.2589066] DDB lost frame for netbsd:Xsoftintr+0x4c, trying 
 0xffff8914ab5640f0
 [ 9917.2689066] Xsoftintr() at netbsd:Xsoftintr+0x4c
 [ 9917.2789064] --- interrupt ---
 [ 9917.2789064] 0:
 [ 9917.2789064] cpu1: End traceback...
 
 [ 9917.2789064] dumping to dev 168,8 (offset=8, size=18872056):
 [ 9917.2889068] dump failed: insufficient space (4194304 < 10579091)
 
 
 [ 9922.8788941] rebooting...