Date: Wed, 18 Sep 2024 16:55:47 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 281560] gve (4) uma deadlock during high tcp throughput Message-ID: <bug-281560-7501-rkhPvdDuq8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281560-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-281560-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281560 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #1 from Konstantin Belousov <kib@FreeBSD.org> --- If you have the deadlock, there must be a resource acquisition loop, which you should be able to unwind by looking at threads waiting for a resource, then finding the owner of the resource, then seeing what it is doing etc. That said, do you run with INVARIANTS and WITNESS enabled? If not, you mus= t. For instance, only INVARIANTS-enabled kernel would detect an attempt to take a blockable lock inside smr section. Similarly, WITNESS might directly point to the resource loop for locks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281560-7501-rkhPvdDuq8>