Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Feb 2026 00:56:22 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 293127] Kernel panic __mtx_lock_sleep due to nfsd?
Message-ID:  <bug-293127-227-BtLewCTJiq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-293127-227@https.bugs.freebsd.org/bugzilla/>

index | next in thread | previous in thread | raw e-mail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293127

--- Comment #11 from yuan.mei@gmail.com ---
(In reply to Mark Johnston from comment #9)
I ran GENERIC-DEBUG kernel for a few days.  The machine went into a deadlock
state (had to hard reset) and did not generate a dump.  However, in an old
dmesg save, there's the following message.  Not sure if this is relevant.

lock order reversal:
 1st 0xfffffe00c4489a00 tcphash (tcphash, sleep mutex) @
/usr/src/sys/netinet/tcp_usrreq.c:1529
 2nd 0xffffffff822e8ae0 in6_ifaddr_lock (in6_ifaddr_lock, rm) @
/usr/src/sys/netinet6/in6_src.c:293
lock order tcphash -> in6_ifaddr_lock attempted at:
#0 0xffffffff80c0eb21 at witness_checkorder+0xbe1
#1 0xffffffff80b8dc79 at _rm_rlock_debug+0x129
#2 0xffffffff80de61fd at in6_selectsrc+0x3fd
#3 0xffffffff80de5d9d at in6_selectsrc_socket+0x6d
#4 0xffffffff80de3861 at in6_pcbconnect+0x291
#5 0xffffffff80dc6877 at tcp6_connect+0xb7
#6 0xffffffff80dc41f5 at tcp6_usr_connect+0x2f5
#7 0xffffffff80c4f500 at soconnectat+0xc0
#8 0xffffffff80c577d1 at kern_connectat+0xe1
#9 0xffffffff80c576c1 at sys_connect+0x81
#10 0xffffffff810eb979 at amd64_syscall+0x169
#11 0xffffffff810bd36b at fast_syscall_common+0xf8
Limiting icmp ping response from 193 to 192 packets/sec


The machine has been rebooted and running the GENERIC-DEBUG kernel again.  Will
see what happens.

-- 
You are receiving this mail because:
You are the assignee for the bug.

home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293127-227-BtLewCTJiq>