Date: Thu, 26 Sep 2024 22:37:22 +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-D2MFwxDd1U@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 --- Comment #11 from shailend@google.com --- Just a more succinct view of iperf thread 100719's central role in this deadlock: ``` db> show lockchain 100413 thread 100413 (pid 0, gve0 rxq 0) is blocked on lock 0xfffffe00df57a3d0 (sl= eep mutex) "mbuf" thread 100719 (pid 857, iperf) is on a run queue db> show lockchain 100414 thread 100414 (pid 0, gve0 rxq 1) is blocked on lock 0xfffff800b86f8560 (rw) "tcpinp" thread 100706 (pid 857, iperf) is blocked on lock 0xfffffe00df57a3d0 (sleep mutex) "mbuf" thread 100719 (pid 857, iperf) is on a run queue db> show lockchain 100433 thread 100433 (pid 0, gve0 txq 2) is blocked on lock 0xfffffe00df57a3d0 (sl= eep mutex) "mbuf" thread 100719 (pid 857, iperf) is on a run queue db> show lockchain 100419 thread 100419 (pid 0, gve0 rxq 6) is blocked on lock 0xfffff800b8d53020 (rw) "tcpinp" thread 100703 (pid 857, iperf) is blocked on lock 0xfffffe00df57a3d0 (sleep mutex) "mbuf" thread 100719 (pid 857, iperf) is on a run queue ``` --=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-D2MFwxDd1U>